Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Event message: An unhandled access exception has occurred (IIS 7.5, cannot load website)

I deployed the Nuget source code to my company's web server, but when navigate to the URL, I get the following error (pulled from Event Viewer on the server):

Event code: 4011 
Event message: An unhandled access exception has occurred. 
Event time: 11/6/2013 9:02:54 AM 
Event time (UTC): 11/6/2013 3:02:54 PM 
Event ID: 2f5d6f7e594e47259b6dc050f82fc57d 
Event sequence: 2 
Event occurrence: 1 
Event detail code: 0 

Application information: 
    Application domain: /LM/W3SVC/2/ROOT/Nuget-3-130282237713215393 
    Trust level: Full 
    Application Virtual Path: /Nuget 
    Application Path: E:\omitted\omitted\Nuget\ 
    Machine name: SERVERNAME

Process information: 
    Process ID: 1420 
    Process name: w3wp.exe 
    Account name: DOMAIN\serviceAccount 

Request information: 
    Request URL: http://subdomain.domain.net/nuget 
    Request path: /nuget 
    User host address: ***.**.***.** 
    User:  
    Is authenticated: False 
    Authentication Type:  
    Thread account name: DOMAIN\serviceAccount 

Custom event details: 

This will run just fine on my local machine, but not on the web server. Does anyone have any ideas as to what the problem might be? All I did was take the Nuget source code, modify the database details in the web.config to point to my database, and deploy it to the web server.

like image 838
Mike Marks Avatar asked Nov 06 '13 15:11

Mike Marks


3 Answers

I would just like to clarify for anyone else who comes to this question. The permissions need to be changed on the folder where the website resides in windows explorer.

like image 121
smithygreg Avatar answered Oct 04 '22 11:10

smithygreg


The local users group needed modify permissions to get past this error. Resolved.

like image 27
Mike Marks Avatar answered Oct 04 '22 11:10

Mike Marks


I had this exact error - the only solution that worked was setting the app pool's Enable 32-bit Applications advanced setting to True.

Update: As I continue to have issues with a particular solution, I've found that clearing the C:\WINDOWS\Microsoft.NET\Framework\v4.xxx.xx\Temporary ASP.NET Files\ resolves the issue in most cases.

like image 45
Adam K Avatar answered Oct 04 '22 11:10

Adam K