>I'd be surprised if the share was the problem. Bear in mind that WebResource.axd is not a physical file but created by an HTTP handler.
>
>This might help : http://blogs.msdn.com/b/carloc/archive/2008/12/04/webresource-axd-or-scriptresource-axd-not-working.aspx

Yes, that is correct. But, running the site locally does not cause such a problem It is only when running the site in share.

>Also some have reported a problem caused by time differences on the production server:
>http://stackoverflow.com/questions/1098548/axd-files-generate-a-404-error
>http://stackoverflow.com/questions/4797435/scriptresource-axd-404-error-in-asp-net-4-application-webresource-works-fine-t

Thanks, I will check those references.

BTW, I also found that aspnet_iisreg.exe is not able to reconfigure successfully the entire IIS registration. We have two failures and, guess what, they are related to the share drive. So, I am trying to have aspnet_iisreg.exe to work successfully at first. While they are failures in there, I doubt the Web site will function properly.