ISAPI Filter ‘C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_filter.dll’ could not be loaded due to a configuration problem. The current configuration only supports loading images built for a AMD64 processor architecture. The data field contains the error number. To learn more about this issue, including how to troubleshooting this kind of processor architecture mismatch error, … [reference to a meaningless web address]
– or –
Could not load all ISAPI filters for site ‘SHAREPOINT – 80’. Therefore site startup aborted
I did a bunch of searching around on the internet and found a bunch of BAD advice. So, here are some things that WILL NOT HELP:
- Don’t bother setting the IIS app pool for SharePoint to allow 32-bit apps
- Uninstalling dotnet 4.0 is stupid. Doy! You are going to need it sooner or later.
- Registry changes to allow IIS 6 and 7 (at the same time) won’t help.
- Running aspnet_regiis.exe -i doesn’t seem to help
When I tried to change the Application Pool for “SharePoint – 80” to allow 32-bit apps. I did get another error, that pointed me in the right direction. The error said this:
The Module DLL ‘C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\isapi\owssvr.dll’ could not be loaded due to a configuration problem. The current configuration only supports loading images built for a x86 processor architecture. The data field contains the error number. To learn more about this issue, including how to troubleshooting this kind of processor architecture mismatch error, see [some pointless/unhelpful web address].
So, here are the two things that DID help:
- This article on Stack Overflow had half of the magic sauce. However, it left-out some important next steps, so I added a post/solution that fills-in the rest of the details. In the article, the author says that you need to edit the applicationHost.config file (no hint where to find that file) and change the entry for “SharePoint14Module” set the preCondition to force 64-bit processing with the term “bitness64”. Totally bananas! How did this guy know something so obscure?
- The article didn’t mention that IIS may still try to load the darn ISAPI DLLs via the 32-bit version of dotnet. Doh! So, you have to go under “IIS Manager”, Sites, “SharePoint – 80”, IIS, “ISAPI Filters”, and make sure all of the “Executable” paths point to the %windir%\Microsoft.NET\Framework64\* path instead of the %windir%\Microsoft.NET\Framework\* (was not 64)
In case I was unclear:
“\Framework\” = Bad
“\Framework64\” = Good
Then I restarted the WWW service and SharePoint 2010 worked on my Dell/Intel with Windows 7 x64.