I was lazy and decided to uninstall my Beta SharePoint, delete all of the databases, then re-install SharePoint 2010 RTM on my server. Everything ran perfectly through the install until I ran the SharePoint Products Configuration Wizard and received the error shown below.
Task configdb has failed with an unknown exception 07/14/2010 10:39:47 8 ERR Exception: System.InvalidCastException: Unable to cast object of type ‘Microsoft.IdentityModel.Configuration.MicrosoftIdentityModelSection’ to type ‘Microsoft.IdentityModel.Configuration.MicrosoftIdentityModelSection’. at Microsoft.SharePoint.Administration.SPIisWebServiceSettings.ProvisionWebSiteSettings() at Microsoft.SharePoint.Administration.SPIisWebServiceInstance.Provision() at Microsoft.SharePoint.Administration.SPFarm.Join() at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb() at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run() at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
Open the web.config file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\Root and change the identityModel Version from 184.108.40.206 to 220.127.116.11
Delete your databases and then re-run the SharePoint products configuration wizard and it should now complete successfully.
Rating: 10.0/10 (3 votes cast)
Rating: +1 (from 1 vote)
Geneva Error – Exception: System.InvalidCastException: Unable to cast object of type ‘Microsoft.IdentityModel.Configuration.MicrosoftIdentityModelSection’ to type ‘Microsoft.IdentityModel.Configuration.MicrosoftIdentityModelSection’., 10.0 out of 10 based on 3 ratings
Ulysses Ludwig is a SharePoint architect with over 16 years in the IT and computer industry. Ulysses' primary focus is SharePoint but he dabbles in the latest web technologies and likes to develop software in his spare time.
Probably the most critical and overlooked portion of SharePoint installation is security. Without a well thought out security strategy and a plan of action, it is likely that SharePoint 2013 will not behave...
So I have noticed that Google refers lots of people to my blog for “Fly Out Menus”. I imagine many of you are disappointed when you find that the article is for enabling the fly out only on the top of the page...