Hi, We have a Commerce site and for about 2 years all has worked well. Suddenly after doing a new DLL update to our bespoke code the OrdersPage (Your Orders) under the shop section has stopped working. This is what the Event Log says:
2016-07-08 16:44:32,465  ERROR EPiServer.Global: 1.2.5 Unhandled exception in ASP.NET System.Web.HttpException (0x80004005): The file '/link/fc0f337d87a0475d8163a641055d5cfc.aspx' does not exist. at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean throwIfNotFound) at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp) at System.Web.Routing.PageRouteHandler.GetHttpHandler(RequestContext requestContext) at System.Web.Routing.UrlRoutingModule.PostResolveRequestCache(HttpContextBase context) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
When we try and view the page in the CMS it says that the page cannot be previewed.
Do you know why this has happened?
That's an internal url that episerver fails to resolve. Why is a good question though. Removed any media files lately or updated appData folder when you released that accidently removed a file?
Turn on logging on info level and see if that gives anything. Check on order page if you have linked to some asset that doesn't exist.
Would Info level give a different log message to the one it supplied above?
Nothing apart from an update to the bespoke dll has chaged.
If I was to give the pageType a new GUID do you think this would create a new instance of the pageType in the DB - Im thinking there is a discrepency in the DB somewhere.
What do you mean "a new DLL update"
and what is your "bespoke code"?
I guess, Log is misleading here, It is better to turn on Logging at Info level as it will give you more details.When you open the page in cms, Please see the browsers console also, is there any error? that can also provide some clue.
(I assume database is still same and there are no changes in connection string)