Previous Next

• 07-24-2008, 11:09 AM

  hassanayoub85 Joined on 09-20-2005, 9:02 AM Lebanon Posts 1 hassanayoub85

  ASP.Net 3.5 Deployment Failure. Reply Contact Dear, Each time I try to deploy my application using IIS 7 on vista 64bit, I got this error: HTTP Error 500.0 - Internal Server Error. Calling LoadLibraryEx on ISAPI filter "C:\Windows\Microsoft.NET\Framework\v2.0.50727\\aspnet_filter.dll" failed. Someone told me to fix this by Running this to enable 32bit apps. cscript.exe adsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 true. After trying this, the problems solved, but another error appears: Error Summary HTTP Error 500.19 - Internal Server Error The requested page cannot be accessed because the related configuration data for the page is invalid. Detailed Error Information Module IIS Web Core Notification BeginRequest Handler Not yet determined Error Code 0x80070005 Config Error Cannot read configuration file due to insufficient permissions Config File \\?\C:\Users\Mr. Hassan M Ayoub\Desktop\FileUpload\FileUpload\web.config Requested URL http://localhost:80/X Physical Path C:\Users\Mr. Hassan M Ayoub\Desktop\FileUpload\FileUpload Logon Method Not yet determined Logon User Not yet determined Config Source -1: 0: How can I solve this? Thx Nothing Is Impossible. The Only Impossible Is Saying Impossible. So, Don't Say It.

• 07-24-2008, 12:52 PM

  In reply to

  joelangley Joined on 07-20-2008, 2:37 PM Posts 82 joelangley	Re: ASP.Net 3.5 Deployment Failure. Reply Contact Sounds like an access/security issue. Please make sure that your permissions are correct IUSR, IIS_IURS ,IIS_WPG,NetworkService (ASPNET). Also, take a look at this article for general trouble-shooting: http://mvolo.com/blogs/serverside/archive/2007/07/26/Troubleshoot-IIS7-errors-like-a-pro.aspx

• 08-04-2008, 5:20 AM

  In reply to

  darrensandford Joined on 08-04-2008, 5:13 AM Posts 1 darrensandford

  Re: ASP.Net 3.5 Deployment Failure. Reply Contact I had exactly the same problem as this and found that it was caused by some kind of installation adding an extra line to my iis applicationHosts.config file. The offending line was in the file C:\Windows\System32\inetsrv\config\applicationHost.config. The "isapiFilters" section should look like: EDIT: Gah, the XML's close enough. <isapiFilters> <clear /> <filter name="ASP.Net_2.0.50727.0" path="%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_filter.dll" enabled="true" enableCache="true" preCondition="bitness32" /> <filter name="ASP.Net_2.0.50727-64" path="%windir%\Microsoft.NET\Framework64\v2.0.50727\aspnet_filter.dll" enabled="true" enableCache="true" preCondition="bitness64" /> </isapiFilters> My problem was that an extra line had been added before the first two, directly referencing the aspnet_filter.dll with a fixed path, the double-backslash you see in the error, but crucially without the "bitness" precondition, meaning that both 32 and 64 bit components were being run against the 32 bit aspnet_filter.dll. I deleted the offending line, and all has started working again. You may find that the command you tried above has changed one of your application pools to 32 bit from 64 bit. You may need to change it back if it wasn't actually the problem.