Spinning losding icon after moving upgraded site to production

colhouse.fdgweb.com is the url. I had this website running fine locally after upgrading it to version 4.50.2 but now that it is on a production server for testing it is just showing the spinning boxes. The template is the uptown theme from Nop-templates.  When it initially loaded it displayed the menu structure and everything but without any css or javascript loading it would seem. next time I tried to load it went to the spinning icon.
Anyway here's log file from it..

info: System.Net.Http.HttpClient.default.LogicalHandler[100]
      Start processing HTTP request POST http://colhouse.fdgweb.com/scheduletask/runtask
info: System.Net.Http.HttpClient.default.LogicalHandler[100]
      Start processing HTTP request POST http://colhouse.fdgweb.com/scheduletask/runtask
info: System.Net.Http.HttpClient.default.LogicalHandler[100]
      Start processing HTTP request POST http://colhouse.fdgweb.com/scheduletask/runtask
info: System.Net.Http.HttpClient.default.ClientHandler[100]
      Sending HTTP request POST http://colhouse.fdgweb.com/scheduletask/runtask
info: System.Net.Http.HttpClient.default.ClientHandler[100]
      Sending HTTP request POST http://colhouse.fdgweb.com/scheduletask/runtask
info: System.Net.Http.HttpClient.default.ClientHandler[100]
      Sending HTTP request POST http://colhouse.fdgweb.com/scheduletask/runtask
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
      Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
      Content root path: D:\WebData\colhouse.fdgweb.com\Colhouse-4.50.2\
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 GET http://colhouse.fdgweb.com/ - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 POST http://colhouse.fdgweb.com/scheduletask/runtask application/x-www-form-urlencoded 58
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 POST http://colhouse.fdgweb.com/scheduletask/runtask application/x-www-form-urlencoded 69
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 POST http://colhouse.fdgweb.com/scheduletask/runtask application/x-www-form-urlencoded 123
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]
      Executing endpoint 'Nop.Web.Controllers.ScheduleTaskController.RunTask (Nop.Web)'
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]
      Executing endpoint 'Nop.Web.Controllers.ScheduleTaskController.RunTask (Nop.Web)'
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]
      Executing endpoint 'Nop.Web.Controllers.ScheduleTaskController.RunTask (Nop.Web)'
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]
      Executing endpoint 'Nop.Web.Controllers.HomeController.Index (Nop.Web)'
info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[3]
      Route matched with {action = "RunTask", controller = "ScheduleTask", area = ""}. Executing controller action with signature System.Threading.Tasks.Task`1[Microsoft.AspNetCore.Mvc.IActionResult] RunTask(System.String) on controller Nop.Web.Controllers.ScheduleTaskController (Nop.Web).
info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[3]
      Route matched with {action = "RunTask", controller = "ScheduleTask", area = ""}. Executing controller action with signature System.Threading.Tasks.Task`1[Microsoft.AspNetCore.Mvc.IActionResult] RunTask(System.String) on controller Nop.Web.Controllers.ScheduleTaskController (Nop.Web).
info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[3]
      Route matched with {action = "RunTask", controller = "ScheduleTask", area = ""}. Executing controller action with signature System.Threading.Tasks.Task`1[Microsoft.AspNetCore.Mvc.IActionResult] RunTask(System.String) on controller Nop.Web.Controllers.ScheduleTaskController (Nop.Web).
info: System.Net.Http.HttpClient.StoreHttpClient.LogicalHandler[100]
      Start processing HTTP request GET http://colhouse.fdgweb.com/keepalive/index
info: System.Net.Http.HttpClient.StoreHttpClient.ClientHandler[100]
      Sending HTTP request GET http://colhouse.fdgweb.com/keepalive/index
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 GET http://colhouse.fdgweb.com/keepalive/index - -
info: System.Net.Http.HttpClient.StoreHttpClient.ClientHandler[101]
      Received HTTP response headers after 16.4734ms - 200
info: System.Net.Http.HttpClient.StoreHttpClient.LogicalHandler[101]
      End processing HTTP request after 22.5434ms - 200
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 GET http://colhouse.fdgweb.com/keepalive/index - - - 200 - - 16.7131ms
info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[3]
      Route matched with {action = "Index", controller = "Home", area = ""}. Executing controller action with signature Microsoft.AspNetCore.Mvc.IActionResult Index() on controller Nop.Web.Controllers.HomeController (Nop.Web).
info: Microsoft.AspNetCore.Mvc.StatusCodeResult[1]
      Executing StatusCodeResult, setting HTTP status code 204
info: Microsoft.AspNetCore.Mvc.StatusCodeResult[1]
      Executing StatusCodeResult, setting HTTP status code 204
info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[2]
      Executed action Nop.Web.Controllers.ScheduleTaskController.RunTask (Nop.Web) in 179.6278ms
info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[2]
      Executed action Nop.Web.Controllers.ScheduleTaskController.RunTask (Nop.Web) in 179.6053ms
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
      Executed endpoint 'Nop.Web.Controllers.ScheduleTaskController.RunTask (Nop.Web)'
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
      Executed endpoint 'Nop.Web.Controllers.ScheduleTaskController.RunTask (Nop.Web)'
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 POST http://colhouse.fdgweb.com/scheduletask/runtask application/x-www-form-urlencoded 123 - 204 - - 1799.7321ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 POST http://colhouse.fdgweb.com/scheduletask/runtask application/x-www-form-urlencoded 58 - 204 - - 1799.7311ms
info: System.Net.Http.HttpClient.default.ClientHandler[101]
      Received HTTP response headers after 2124.6772ms - 204
info: System.Net.Http.HttpClient.default.LogicalHandler[101]
      End processing HTTP request after 2138.343ms - 204
info: System.Net.Http.HttpClient.default.ClientHandler[101]
      Received HTTP response headers after 2124.7494ms - 204
info: System.Net.Http.HttpClient.default.LogicalHandler[101]
      End processing HTTP request after 2138.3846ms - 204
info: Microsoft.AspNetCore.Mvc.StatusCodeResult[1]
      Executing StatusCodeResult, setting HTTP status code 204
info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[2]
      Executed action Nop.Web.Controllers.ScheduleTaskController.RunTask (Nop.Web) in 367.5594ms
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
      Executed endpoint 'Nop.Web.Controllers.ScheduleTaskController.RunTask (Nop.Web)'
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 POST http://colhouse.fdgweb.com/scheduletask/runtask application/x-www-form-urlencoded 69 - 204 - - 1959.9490ms
info: System.Net.Http.HttpClient.default.ClientHandler[101]
      Received HTTP response headers after 2281.6189ms - 204
info: System.Net.Http.HttpClient.default.LogicalHandler[101]
      End processing HTTP request after 2295.2794ms - 204
info: Microsoft.AspNetCore.Mvc.ViewFeatures.ViewResultExecutor[1]
      Executing ViewResult, running view Index.
info: Microsoft.AspNetCore.Mvc.ViewFeatures.ViewResultExecutor[4]
      Executed ViewResult - view Index executed in 45815.7987ms.
info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[2]
      Executed action Nop.Web.Controllers.HomeController.Index (Nop.Web) in 45960.3667ms
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
      Executed endpoint 'Nop.Web.Controllers.HomeController.Index (Nop.Web)'
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 GET http://colhouse.fdgweb.com/ - - - 200 56206 text/html;+charset=utf-8 48583.9812ms
info: System.Net.Http.HttpClient.default.LogicalHandler[100]
      Start processing HTTP request POST http://colhouse.fdgweb.com/scheduletask/runtask
info: System.Net.Http.HttpClient.default.ClientHandler[100]
      Sending HTTP request POST http://colhouse.fdgweb.com/scheduletask/runtask
info: Microsoft.AspNetCore.Hosting.

Thanks! :)

Rob

skagitmedia wrote:
Check the settings in AppSettings
https://yourwebsite.com/Admin/Setting/AppSettings
Check
Enable disk cache is enabled
and the cache directory is set - mine says
C:\inetpub\wwwroot\nopCommerce4.50.1\wwwroot\bundles

Yidna wrote:

I checked the appsettings json file and it was set to my local folder so I reset that to the correct folder. Is there something in the db I need to set? It is still showing only the spinning box icon?

Thanks!
Rob

Maybe a different problem
What happens if you use the DefaultClean Theme ?

Yidna wrote:

I'm not able to access any pages I just see the spinning box.

Thanks!
Rob

Is the Uptown Theme for v4.50
- If so you have the install file and can reinstall it later
So you could try delete the Uptown Theme Directory and it should default to DefaultClean

Can you access the Database and check the log file for errors ?

Is the Uptown Theme for v4.50
- If so you have the install file and can reinstall it later
So you could try delete the Uptown Theme Directory and it should default to DefaultClean

Yidna wrote:
On a hunch i am going to remove the sitefiles and reload them from a current archive. I had to uninstall the ajax filter plugin in the theme then reload it after going fromn SQL Server 2019 to SQL server 2017. I think the sitefiles might be updated and I need to reload them if that does not work I will definitely try what your suggest. Appreciate all your help greatly. :)

Thanks!
Rob

I would start with a fresh clean version of v4.50.2 and get the site operating
Then install Themes and Plugins

Yidna wrote:
The site was a massive upgrade from 3.80. I painstakingly did every update fixing everything along the way progessively up to 4.50.2 locally here on my machine. It works great locally. I should be able to take the site files and take the db and load them on the server and it should work. I even installed the dotnet core 6.0 on the server. Why would that not work? :)

Rob