At least from the log message itself - looks like you are missing login page at all.
When am going from CMS site its redirecting to login page thats fine.
But when am going from front end site then am getting this error.
Do you have installation on front-end server with no EPiServer editing UI (like turned off via config or any other method)?
For instance, on frontend - if you go to "/cms" or "/episerver" or any other url where EPiServer Admin UI is added. Do you receive the same error? It just looks like EPiServer is trying to give you login page to access expired page (in order for editors to be able to edit that) but EPiServer Admin UI is not configured on front-end servers.
What is desired outcome? you should see 404?
Yeah from front end we do not have access to Episerver UI.
From CMS site am not getting this error. Its as expected gng to login page.
outcome is 500 error when accessing from front end.
What is desired outcome when visitor will go to expired page in front-end server? Should epi return 404 error instead?
Hi All
When browsing expired pages i am getting 500 error instead of login page. When i checked the log i get below exception.
Can you please help here.
2016-06-01 06:55:27,693 [60] ERROR EPiServer.Global: 1.2.5 Unhandled exception in ASP.NET
System.Web.HttpException (0x80004005): The file '/Util/login.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.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
at System.Web.HttpApplication.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)