Monday, June 21, 2010

Error 500 after installing SharePoint 2010 and Visual Studio 2010

Hi all,

Just and update on some frustrating behaviour I recently had.
The solution is so simple it's annoying to let anyone else struggle with it...

Well, I went ahead and installed SharePoint 2010 on my Win7 64 bit laptop.
In stand alone mode, everything was going great!
here is a link to a great step by step guide for doing that:

OK, once I was done - SharePoint was working great and at lightning fast speed!

Next I wanted to install Visual Studio 2010 on that same machine, so I ran the installer and chose to install C#, Web developer and among other things the SQL express that comes with it.

Installation, again, was going smoothly.

After a reboot - I noticed that SharePoint had stopped working, and any page I tried to access gave me server error 500... even the central administration!

Naturally, I ran the SharePoint configuration wizard and hoped it will make everything better again... only to find out it reports that my configuration database is not available!

So, first step was to fix the DB not available thing... that was easy:
apparently installing VS with its SQL express had stopped the SharePoint SQL instance and all I had to do was to start it, using services or using the start menu -> "SQL Server Configuration Manager":

OK - that allowed me to complete the SharePoint configuration wizard, but did not resolve the server error 500 I keep getting hitting any SharePoint page.

SharePoint log files were useless, which means that the error came before SharePoint code was even called.

Windows log viewer was very helpful on this, reporting an ISAPI filter that could not be loaded and caused the site load to abort: "Could not load all ISAPI filters for site/service. Therefore startup aborted"
Followed by another message:
"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, see"

After a little trial and error, I have noticed that the ISAPI filter DLL file is being loaded from the 32 bit framework folder. Changing that manually to 64 bit in all my sites solved the problem!

So, while I am not sure of why this is happening, but at least here is how to fix it!


Dennis de Vries said...

Hi Shai!

Thanks alot for your explenation. I've had the same kind of error on my WSUS 3.0 SP2 configuration.

This error showed up after installing .NET 4.0. And after correcting the "\Framework64\" path my WSUS server worked again.

Kind regards,

Dennis de Vries
The Netherlands

Anonymous said...

wow thanks this worked! I installed windows updates(including .NET 4) to come back to the 500 page and 404 on other sites in the morning.

I went to IIS, clicked the site and replaced "framework" with "framework64" for the path. It's back up again!

Allan said...


Can someone tell me how to do this?
My "PageHandlerFactory-ISAPI-2.0-64" is using C:\Windows\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll but when I access the page, I get a 500 error with message Calling LoadLibraryEx on ISAPI filter "C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_filter.dll" failed.

I can't understand why it's using Framework as opposed to Framework64. Please help. Thanks


Anonymous said...

Hi Shai,
This works really well and even runs little fast. I also installed both SP and VS. Had a good time with your blog. I also refered one more blog related to this topic (which i will mention below)also solved my problem. Please check it out. You will find some useful info from that.

Scott said...


I was devastated after all the work I did to install a dev environment only to get a 500 error. Your fix WORKED!! Thank you for taking the time to post this. It is very appreciated!

Shai Petel said...

Please note that there are several versions of the framework.
You changed the v2 to use 64bit folder, but it reports on the v4 running off the 32 bit.
perhaps this is the reason?

Scott - I know what you mean. Glad I could help, I really didnt find anything posted on this anywhere else.

Anonymous said...

I installed MOSS 2007 on IIS 6.0. After SharePoint Configuration Wizard no web application worked. I get the error: Unavailable service.
In event viewer I get the next error:
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.

I solved it changing the path of ASP.NET._4.0.30319.0 to Framework64

Thenk you for this post

Taha Zubair said...

Thanks Shai,

I have changed the "ISAPI Filter" path from IIS and stand up the live server Central Admin

Taha Zubair