As I mentioned in my previous posts few days back I’ve decided to take Windows 8 Developer Preview for a spin by running it in a VHD boot configuration. As most of my time I’m involved in working with SharePoint 2010 Server it was more than obvious that I would be installing it.
But it was not that straightforward, here are my findings and the ways I’ve fixed it.
1. Install pre-requisites manually (W8 Developer Preview is still a workstation) as you cannot benefit from Prerequisites installer as you would do while installing it on server. As a quick fixer, the Windows Identity Foundation 3.5 even if already installed it must be activated in “Turn Features ON/OFF” in manually.
2. I still used SQL 2008 R2 Express Edition, which handles the SQL dependencies already.
3. Install SharePoint 2010 Server and start the Configuration Wizard. It will all go smoothly up to the point when the Central Administration must be provisioned when it will fail with the following exception (see below):
Failed to provision the SharePoint Central Administration Web Application.
An exception of type System.Runtime.InteropServices.COMException was thrown. Additional exception information: Filename: \\?\C:\inetpub\wwwroot\wss\VirtualDirectories\23516\web.config
Line number: 25
Error: There is a duplicate ‘system.web.extensions/scripting/scriptResourceHandler’ section defined
Basically this could mean either that indeed there is already a section or it might mean that while “parenting” occurs, same declaration must be already existent somewhere else, such as a machine.config
But in this case it means something else: .NET 4.0 being installed already, by default in IIS all Application pools will use it by default. So to fix it, one must be changing those back to using .NET 2.0 as you must know it already, but SharePoint 2010 doesn’t support .NET 4.0 (see bellow), and do it so for every of the SharePoint Web sites, as visible below.
Once all are changed, except for the SharePoint Web Services Root, start other Application pools and Sites that we’re created during wizard execution.
Now you could launch the Central Administration and it should work normally. Obviously as the “Start Menu” has been replaced by the Tile-based menu, you can easily find it as quickly as you can type SharePoint.
So, until next time happy SharePoint-ting fingers otherwise