.Net Framework and MOSS 2007

Posted on June 10th, 2009 in Technology, Work by Jim Prince

Yesterday I had a frustrating experience trying to install .Net Framework 3.5 SP1 in one of our dev environments. Due to some, frankly bizarre, dependency problems I found myself having to uninstall .Net 3.5, .Net 3.0 and .Net 2.0. I was then finally able to install .Net 3.5 SP1 which thankfully is cumulative.

Optimistically I thought that would be the end of the issue but SharePoint seemed to be very broken. For example if I tried to navigate to the root of a site collection I’d get a 404 error. If I navigated to the full URL using /pages/default.aspx the site would load but images called from a document library were missing. If I accessed pages under /_layouts such as settings.aspx then everything loaded just fine.

The Windows Event logs were empty and since SharePoint Central Administration was exhibiting the same behaviour I ran the SharePoint Config Wizard. Once this completed CA was fine but I still had problems with the other Webapps and Site Collections.

At this point I resorted to trawling Google and perhaps for the first time in my career found the solution on Experts Exchange.

Open IIS Manager and for each Webapp navigate to Properties -> Home Directory -> Configuration -> Wildcard Application Maps.




If you’re experiencing the same problem as I did you’ll see that this is box is empty. Click on insert and add C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll.

Ensure that the check box “Verify that the file exists” is unchecked and click on Ok. After running IISRESET everything was working again and the problem was resolved.

Post a comment