SharePoint 2010 configuration wizard TypeLoadException


If you are installing SharePoint 2010 rejoice only after the configuration wizard is through with its process. I recently ran into an issue on Step 5: Configuring SharePoint services. The configuration wizard failed with an InvalidOperationException with the following entry in the eventlog

Log Name: Application Source: SharePoint 2010 Products Configuration Wizard Date: 5/18/2010 10:20:15 AM Event ID: 104 Task Category: None Level: Error Keywords: Classic User: N/A Computer: MARA.dev.credera.local Description: Failed to register SharePoint services. An exception of type System.InvalidOperationException was thrown. Additional exception information: Failed to load or format string Id ManagementUI_ExcelCalculationService_FriendlyName for culture en-US: System.TypeInitializationException: The type initializer for ‘Microsoft.Office.Excel.Server.Host.ExcelServerHost’ threw an exception. —> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.TypeLoadException: Could not load type ‘Microsoft.Office.Excel.Server.Extensions.IHostExtension’ from assembly ‘Microsoft.Office.Excel.Server.MossHost, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’. at System.Reflection.Assembly._GetType(String name, Boolean throwOnError, Boolean ignoreCase) at System.Reflection.Assembly.CreateInstance(String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes) at Microsoft.Office.Excel.Server.MossHost.MossHost.CreateHostExtension(String className, IHostExtension& extension) at Microsoft.Office.Excel.Server.MossHost.MossHost.LoadHostExtensions() — End of inner exception stack trace — at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck) at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache) at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache) at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes) at Microsoft.Office.Excel.Server.Host.ExcelServerHost.CreateHost(String assemblyName, String className) at Microsoft.Office.Excel.Server.Host.ExcelServerHost.CreateHost() at Microsoft.Office.Excel.Server.Host.ExcelServerHost..cctor() — End of inner exception stack trace — at Microsoft.Office.Excel.Server.Host.ExcelServerHost.get_Host() at Microsoft.Office.Excel.Server.StringManager.get_BrandStrings() at Microsoft.Office.Excel.Server.StringManager.GetString(StringId id, EncodingType encodingType, Boolean syncCultures, Object[] args) System.InvalidOperationException: Failed to load or format string Id ManagementUI_ExcelCalculationService_FriendlyName for culture en-US: System.TypeInitializationException: The type initializer for ‘Microsoft.Office.Excel.Server.Host.ExcelServerHost’ threw an exception. —> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.TypeLoadException: Could not load type ‘Microsoft.Office.Excel.Server.Extensions.IHostExtension’ from assembly ‘Microsoft.Office.Excel.Server.MossHost, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’. at System.Reflection.Assembly._GetType(String name, Boolean throwOnError, Boolean ignoreCase) at System.Reflection.Assembly.CreateInstance(String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder

If you encounter this issue or a similar issue with the configuration wizard, try deleting the registry keys for the service and re-run the configuration. The keys to delete are under HKLM\SOFTWARE\MICROSOFT\Shared Tools\Web Server Extensions\14.0\WSS\Services Delete the key for the service causing the error and re-run the configuration. After the delete the coniguration wizard ran successfully to completion

WARNING: Please see the comments. There are some issues with this fix. your mileage may vary

Advertisements

7 Responses to SharePoint 2010 configuration wizard TypeLoadException

  1. piou says:

    Hi!
    thanks. this is the only stuff I get on this issue.
    Do you know more about the consequences of removing this key from the registry ? My Excel Services was Online before installing the OfficeWebApps, any impacts ??
    thanks

  2. techdhaan says:

    I do not know of the consequences. After deletion I re-ran the config wizard and everything worked fine for me. YMMV

  3. Skhumbuzo says:

    The consequence is that after the deletion of this key. you won’t be able to view/create the Excel service application. you also won’t be able to access the “Services on the server” page. throws error(when going to the “Services on Server”: Could not load type ‘Microsoft.Office.Excel.Server.MossHost.IHostExtension’ from assembly ‘Microsoft.Office.Excel.Server.MossHost, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’

  4. Skhumbuzo says:

    is there any solution for that one? the work-around would be to use powershell or stsadm to access and view the services, but when the requirement for the Excel SA comes, i’m gonna be facing a serious problem. i tried a repair but it fails at the wizard with the same above mentioned error cuasing me to delete the key again. is there another work-around?

  5. How can I get the name of the service causing the error ??

  6. rajeswari says:

    Please suggest a work around urgently because of this my services on server is throwing exceptions as well as other things like deploying a feature in visual studio is not happening…..

    • skhumbuzo mjoji says:

      @rajeswari – I had to go through the agonizing pain of doing a repair then connecting to the existing farm. Basically i had installed a beta version of office web apps which caused the problem with the service application (Excel Service application). i then deleted the registry key, uninstalled the beta version of office web apps, then performed a repair of the whole SharePoint installation, installed the latest version of office web apps, then re-running the wizard. this fixed everything including the services on server page (which i could not access because of the deleted registry key). this is not a recommended solution but i was desperate at the time and we hadn’t gone live yet, so think about it carefully if you gonna take this route… Hope this helps.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: