ASP.NET process identity does not have read permissions to the global assembly cache.

VS2005 RC1 - XP PRO Sp2 + - App is a webservice and default.aspx.

I'm seeing errors in the error log after a browser tries open the site. The browser sees an http 500.

The server log shows the following:

03:04:48 127.0.0.1 GET /default.aspx 500
03:05:33 192.168.0.100 GET /test.htm 304
03:05:51 192.168.0.100 GET /default.aspx 500
03:06:39 127.0.0.1 GET /default.aspx 500
03:06:41 127.0.0.1 GET /default.aspx 500

I have opened up all the permissions root directory and the ASP user account and internet user account which has been know to be the cause of this error. There is no usual way to set permissions in the GAC directory because when looking at its properties there is no security tab. I've taken a quick look at the .net v20 framework configuration manager and I've seen lots of viewers with readonly parameters but haven't found any way to set them.

This error seems to be environmental - at the nexus of IIS ASP and the v2.0 framework. Has anyone seen it before

Answer this question

ASP.NET process identity does not have read permissions to the global assembly cache.

gssundar

Well for reasons I now can't remeber, we decided to install the SDK on the server and now all is well!

So I don't actually know what fixed it, but we are working - sort of.

the outstanding problem is that we are getting errors when any .aspx page needs to access our SQL2000 database (not 2005). I guess it is security related but as yet we haven't solved that.

This is low-priority prelim. testing at the moment so it is often days between attempts.
Artur Magaljan

Before you do anything too drastic check your basic permission settings - I had this error and solved this by simply adding the ASP_NET machine account to the website root.
Franco22

I'm having this problem with .NET v2 also. Can you be a bit more specific when referring to applications directory. Is this the 'web application' directory, 'program files' directory or where

Sorry to be appearing stupid on this but clarification would help me enormously!

thanks
Michael Chan

I know what helped me with this and what the problem was for me. Unfortunately I couldn't find this post to close it.

I had had a power failure when this happened. I had problems in my router and in debugging that problem, i deliebrately unistalled IIS. What I found out is that if you instal IIS I believe some of the special accounts get corrupted in a way that it's really not fixable. The fix was actually to scrape the disk and do a fresh install. As soon as I did that, all the ASP problems were gone.
SMKurup
Hit the exact same problem today when installing a test directory on a restricted web app on my production server. The restricted web app is the key here, check out the following article

http://programcsharp.com/blog/archive/2005/10/04/7595.aspx

Seems that when I restricted it to Windows Authentication and then set the directory restriction to System and Admins, I forgot to allow localmachine\ASPNET have access as well. The moment I gave the account Read/Execute rights to the application directory, it worked.

Reading the blog above shows someone else ran into the same problem when they installed FPSE on their IIS machine, it set the directory rights for them and removed ASPNET. Another scenario is when the local IT folks decide it is in yours and their best interest to screw with the rights without telling you .

Anyways, just go to your application directory and give the ASPNET account the proper rights and you should be good to go.

HTH, Jim
ASP.NET process identity does not have read permissions to the global assembly cache.

Answer this question