Help Desk and PC Inventory Software by Gritware   Gritware Support Forums
Gritware Support Forums
Sign up Latest Topics
 
 
 


Reply
  Author   Comment  
Canadianmade

Member
Registered:
Posts: 69
Reply with quote  #1 
Hello, out of no where we are now getting the following error when trying to load the website. (already tried restarting the whole server).

Server Error in '/' Application.


The file '/index.aspx' has not been pre-compiled, and cannot be requested.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: The file '/index.aspx' has not been pre-compiled, and cannot be requested.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[HttpException (0x80004005): The file '/index.aspx' has not been pre-compiled, and cannot be requested.]   System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) +9871022   System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) +103   System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean throwIfNotFound) +165   System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp) +43   System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) +31   System.Web.UI.PageHandlerFactory.GetHandler(HttpContext context, String requestType, String virtualPath, String path) +37   System.Web.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +339   System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) +48   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +159


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.3429.0
Canadianmade

Member
Registered:
Posts: 69
Reply with quote  #2 
Hello, we had to do a complete reisntall last time this happened and now it is happening again. Would like to know if there is something we can do to prevent this?

Funny enough, if we access the site using the servername (http://servername/webtracks) it works fine? But using the DNS name we have setup for servicdesk.domain.com does not work?
thoese

Moderator
Registered:
Posts: 491
Reply with quote  #3 
Hi,

Thanks for the detailed information.  It does seem odd that the error only happens using the customer DNS name.

Try deleting all files in the following folder where Web Tracks is installed..

C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root 

After doing this, reset iis.

Thank you,
Todd

__________________
Todd @ Gritware
Other resources
Gritware.com
Knowledge Base
Web Tracks Help
Canadianmade

Member
Registered:
Posts: 69
Reply with quote  #4 
Thanks for the reply, unfortunately I had to get this going so I installed it on another server and it seems to working fine there. If we run into an issue again we will try deleting those files.
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.