Re: Failed to map the path '/sanction/App_GlobalResources/'

Thanks Gery. I ran the site in Netscape 7.1 and it seems to have given me some
more info like : 


Failed to access IIS metabase.The process account used to run ASP.NET must have
read access to the IIS metabase (e.g. IIS://servername/W3SVC).For information on
modifying metabase permissions, please see
http://support.microsoft.com/?kbid=267904.

I did a (.Net Framework Ver. 2.0) aspnet_regiis -ga machinename/ASPNET 

Then I re-ran the page. It gave exactly the same error message as above. BTW, I
have .NET Framework 1.0,1.1 and 2.0 installed in my machine. I do not have any
critical apps developed using 1.0 and 1.1. Can I uninstall these versions of the
framework? Is there any possibility that they might be the reason for the page
not being able to run?

Mark

Hi Mark,

This is an interesting situation. It may be that MapPath still fails for you
because of the same permissions failure that you are seeing in the process
account not being able to have access to the IIS metabase...eg some sort of I/O
restrictions. In your original post you mentioned that you are running IIS 5.
Are you still running IIS 5 or have you moved to IIS 6?

Changing to IIS 6 changes the account that ASP.NET runs under. In IIS 5 it was
running under the System account but now in IIS 6 it runs the Network Service
account which is slightly more restricted. But I don't think that should give
you the metabase permission problem...

In any case try this: (I am using Windows 2003 Server so some of this may be
different than what you see depending on your OS) Change the account that
ASP.NET runs under. To do this go to IIS Manager and look at the properties of
the web site you are working on. Go to the Home Directory tab and look near the
bottom and determine what the Application pool name is. Once you have that,
close the properties window. Then look under Application pools in the left pane
and find that application pool that is being used for your web site. Look at its
properties. Under the Identity tab it will show you the application pool
identity being used. This is a 'predefined' setting on my machine. If you are
using IIS 5 it is most likely 'Local System' but if it is IIS 6 it should be
'Network Service'. In any case make a note of it. Then change it to 'Local
System'. Then do an IIS reset (iisreset) and try testing the page again. If
things work then the problem is that account that was being used. If it had been
changed in it's security access it could have caused your problem OR if it
wasn't either of the two accounts mentioned then it is most likely a security
for that account.

Best regards,

Gery

On IIS 5, make sure the local ASPNET account has at least NTFS read permissions
on the content files and folders.