Windows Server 2019 Installation

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
4 years ago
Hey everyone!

I deployed the latest NopCommerce version to my win 2019 server. When I go to the resource I get the following error as shown here https://imgur.com/ODQFmzu

I gave the application pool access to the folders and that didn't work.
4 years ago
Do you have logs enabled?  If not, edit your web.config so stdoutLogEnabled="true"

    <aspNetCore requestTimeout="23:00:00" processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" forwardWindowsAuthToken="false" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" startupTimeLimit="3600">


then you can read the logs from that directory if you have direct access to the server, or select the latest log entries from the Log table in the database:


SELECT TOP 10 *
FROM [Log]
ORDER BY Id DESC;


Or you can configure IIS to send errors to the browser (don't do this in production).

something was probably recorded in your server's Event Viewer too, but nopCommerce's logs will probably be more helpful
4 years ago
99Systems wrote:
Hey everyone!

I deployed the latest NopCommerce version to my win 2019 server. When I go to the resource I get the following error as shown here https://imgur.com/ODQFmzu

I gave the application pool access to the folders and that didn't work.


I had the same issue and it was because .NET Core wasn't installed. nopCommerce requires .NET Core 2.2 installed, try installing that particular version, not the 3.2.1 which doesn't appear to work with nopCommerce, at least for me it's coming up with an error
4 years ago
Did installing of the .NET Core 2.2 run time solve the error ?

99Systems wrote:
Hey everyone!

I deployed the latest NopCommerce version to my win 2019 server. When I go to the resource I get the following error as shown here https://imgur.com/ODQFmzu

I gave the application pool access to the folders and that didn't work.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.