Access denied..........global.asax
-
I have been fighting this for several days now and it is REALLY beginning to
irritate the crap out of me. Configuration is as follows:
Win2k3 server SP1
SPS 2003 SP1
SQL server is remote
Using the Network Service account to run the Report Server service
Using windows integrated for DB access
Impersonate = true in the web.config file
Reporting Services has been successfully initialized per the documentation
Paths for Reports and Report Server have been excluded in SharePoint
I can access http://<servername>/ReportServer just fine.
When I try and access http://<servername>/reports I am prompted for a
username and password and although I am a member of the local administrators group I still can't access the Reports page. The username/password box comes up three times and then redirects to that oh so glorious error message we all know and hate.
I have tried granting my account, machine\aspnet, iusr_machinename
permissions to global.asax and still get the error message each and every
time.
It should not be this difficult to get an application to work. Any help is
appreciated more than you can possibly imagine.
TIA!!!!!!!
Access to the path "C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportManager\global.asax" is denied. 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.UnauthorizedAccessException: Access to the path
"C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportManager\global.asax" is denied.
ASP.NET is not authorized to access the requested resource. Consider
granting access rights to the resource to the ASP.NET request identity.
ASP.NET has a base process identity (typically {MACHINE}\ASPNET on IIS 5 or Network Service on IIS 6) that is used if the application is not
impersonating. If the application is impersonating via <identity
impersonate="true"/>, the identity will be the anonymous user (typically
IUSR_MACHINENAME) or the authenticated request user.
To grant ASP.NET write access to a file, right-click the file in Explorer,
choose "Properties" and select the Security tab. Click "Add" to add the
appropriate user or group. Highlight the ASP.NET account, and check the boxes for the desired access.
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:
[UnauthorizedAccessException: Access to the path "C:\Program Files\Microsoft
SQL Server\MSSQL\Reporting Services\ReportManager\global.asax" is denied.]
System.IO.__Error.WinIOError(Int32 errorCode, String str) +393
System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access,
FileShare share, Int32 bufferSize, Boolean useAsync, String msgPath, Boolean
bFromProxy) +888
System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access,
FileShare share, Int32 bufferSize) +44
System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean
detectEncodingFromByteOrderMarks, Int32 bufferSize) +79
System.Web.UI.Util.ReaderFromFile(String filename, HttpContext context,
String configPath) +443
System.Web.UI.TemplateParser.ParseFile(String filename, String
virtualPath) +62
System.Web.UI.TemplateParser.Parse() +200
System.Web.UI.TemplateParser.GetParserCacheItemThroughCompilation() +74
System.Web.UI.TemplateParser.GetParserCacheItemInternal(Boolean
fCreateIfNotFound) +219
System.Web.UI.TemplateParser.GetParserCacheItemWithNewConfigPath() +125
System.Web.UI.TemplateParser.GetParserCacheItem() +98
System.Web.UI.ApplicationFileParser.GetCompiledApplicationType(String
inputFile, HttpContext context, ApplicationFileParser& parser) +171
System.Web.HttpApplicationFactory.CompileApplication(HttpContext context)
+43
System.Web.HttpApplicationFactory.Init(HttpContext context) +485
System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext
context) +170
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +414
-
Excuse me if I misunderstand because I did not have time to read all of your information; but I have had a similar problem repeatedly over the past few months with using the network service account. The key to resolving was finding the 17 errors (repeatedly) in the application event log.
Okay, here is something pasted from my notes
The “NETWORK SERVICE” user was used by default for DCOM OBJECTS. There were 17 errors (10016) in the system event log for each failed access against “Reports”. Microsoft online help provided the technique to give this user the appropriate web service account privileges required. This was a rather convoluted modification; but was successfully completed and the error messages did go away.
But that is not complete enough to fix the problem. go to "Component Services" | Computers | My Computer | DCOM Config and look for the following item:
netman 27AF75ED-20D9-11D1-B1CE-00805FC1270E}
go to properties |security and edit the "launch and activation permissions"
add the network service account and give it remote launch and remote activation.
This should fix your problem. I'm counting on it
By the way, I said the Microsoft solution was convoluted. The described fix is NOT exactly what they recommended, and they never said "netman" but gave me the key (above, ending in 1270e) in a list that cannot be sorted... and it had me with multiple windows opened in component services and in the registry... none of which was necessary (in the registry, at least). I have fixed these errors at least a half a dozen times on various machines and OSes... and once they go away they only return when I re-image... something I have also done a lot of recently.
Good luck! Hope this helps.
-
Thanks David. I had seen that before and had tried it and while it stopped the error message in the Event Viewer it did not allow access to global.asax.
I did finally get it to stop throwing that error by giving the EVERYONE group full access to global.asax. Obviously that isn't going to fly in a production environment but right now I would like to just get the app to display something besides error messages.
Since I got rid of the access denied message I have gotten the following;
Unable to establish a connection to the database.
Invalid or unknown database.
User logon failure
I have tried rsconfig, rsactivate, install/uninstall and I am about ready to say the heck with it. I can't believe that any application should be this problematic to install and configure.
Thanks for the help David, despite the griping about the app I appreciate you taking the time to respond.
-
In the web.config file you need to have this entry. As the comment says, the run-time will now permit access to a non trusted server
<!-- Allows log in to database on non trusted server-->
<identity impersonate="true"/>
Hope this helps
Quis custodiet ipsos custodes.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply