Thursday, April 30, 2015

System.Runtime.InteropServices.COMException (0x800703FA)

Hello all,

today I faced another very interesting SharePoint 2013 issue :-) At least interesting for me.

Application log was filled out every hour with the following message:

Log Name: Application
Source: Microsoft-SharePoint Products-PerformancePoint Service
Date: 24.04.2015 10:41:34
Event ID: 1176
Task Category: PerformancePoint Services
Level: Error
User: contoso\test
Computer: mycomputer.local
An error occurred during maintenance cleanup.

Exception details:
System.Runtime.InteropServices.COMException (0x800703FA): Retrieving the COM class factory for component with CLSID {BDEADF26-C265-11D0-BCED-00A0C90AB50F} failed due to the following error: 800703fa Illegal operation attempted on a registry key that has been marked for deletion. (Exception from HRESULT: 0x800703FA).
   at Microsoft.SharePoint.Library.SPRequest..ctor()
   at Microsoft.SharePoint.SPGlobal.CreateSPRequestAndSetIdentity(SPSite site, String name, Boolean bNotGlobalAdminCode, String strUrl, Boolean bNotAddToContext, Byte[] UserToken, SPAppPrincipalToken appPrincipalToken, String userName, Boolean bIgnoreTokenTimeout, Boolean bAsAnonymous)
   at Microsoft.SharePoint.SPRequestManager.GetContextRequest(SPRequestAuthenticationMode authenticationMode)
   at Microsoft.SharePoint.Administration.SPFarm.get_RequestAny()
   at Microsoft.SharePoint.Utilities.SPUtility.GetLocalizedString(String source, String defaultResourceFile, UInt32 language)
   at Microsoft.PerformancePoint.Scorecards.ServerGlobalResources.SPGetString(String classKey, String resourceKey, CultureInfo uiCulture)
   at Microsoft.PerformancePoint.Scorecards.Server.Utilities.TempFCOTimedCleanup.Clean(DateTime expirationDateTime)

Suggestions like "Restart Performance Point service" or "Reboot the server" are not working in my case.

Fortunately I found that a solution working for me:

I changed the Load User Profile to true for Security TokenServiceApplicationPool inside IIS.

Hope this could help you too in resolving similar issues.

Share this post if you think it is helpful!

No comments:

Post a Comment