You are currently viewing 0x800703fa? Repair Immediately

0x800703fa? Repair Immediately

Updated

  • 1. Download ASR Pro
  • 2. Run the program
  • 3. Click "Scan Now" to find and remove any viruses on your computer
  • Speed up your computer today with this simple download.

    Last week, some of our readers told us they stumbled upon 0x800703fa.

    • 2 transformers for reading
    • Applies to:
      SharePoint Server 2013, SharePoint Server 2010

    Symptom

    Updated

    Are you tired of your computer running slow? Annoyed by frustrating error messages? ASR Pro is the solution for you! Our recommended tool will quickly diagnose and repair Windows issues while dramatically increasing system performance. So don't wait any longer, download ASR Pro today!


    A complete operation from Microsoft SharePoint 2013 or Microsoft SharePoint 2010 will fail and you will immediately see the following COMException error message logged in the ULS associated with the SharePoint LogViewer:

      [System.Runtime.InteropServices.COMException (0x800703FA): Failed to get the factory class org for a component with CLSID  due to the following error: 800703fa Attempting to perform an invalid registry key operation because it is marked should has been removed. 

    This error can occur under various circumstances. In this example, errors can occur in any scenario when you see log entries shortly after:

      03/11/2015 20: 09: 45.83 w3wp.exe (0x1A24) 0x46CC SharePoint Portal Server Microfeeds ada0j UnexpectedMicroBlogList.GetMicroBlogPostsForRePopulation http: // mysite / personal / 12345 bug fixedException:[System.Runtime.InteropServices.COMException (0x800703FA): Get COM class attachment for component with CLSID.Error BDEADF26-C265-11D0-BCED-00A0C90AB50F due to the following error: 800703faInvalid operation on a registry key that was also marked for deletion. (Exception from HRESULT: 0x800703FA).at Microsoft.SharePoint.Library.SPRequest..ctor ()at Microsoft.SharePoint.SPGlobal.CreateSPRequestAndSetIdentity (...)at Microsoft.SharePoint.SPRequestManager.GetContextRequest (SPRequestAuthenticationMode authenticationMode)at Microsoft.SharePoint.Administration.SPFarm.get_RequestAny ()at Microsoft.SharePoint.SPSecurity.GetCurrentUserTokenNoApplicationPrincipalDelegated (SPWebApplication Web Application, Uri siteUrl)at Microsoft.SharePoint.SPSecurity.GetCurrentUserToken ()at Microsoft.SharePoint.SPSecurity.EnsureOriginatingUserToken ()at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges (WaitCallback SecureCode Object Parameter)at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges (CodeToRunElevated secureCode)at Microsoft.Office.Server.UserProfiles.SPS2SAppContext.GetClientContext (...)at Microsoft.Office.Server.UserProfiles.SPS2SAppExecutionContextBase.get_ClientContext ()at Microsoft.Office.Server.Microfeed.SPMicrofeedStore.Query (...)at Microsoft.Office.Server.Microfeed.MicroBlogList.ExecuteRepopulationCamlQuery (...)in Microsoft.Office.Server.Microfeed.MicroBlogList.GetMicroBlogPostsForRePopulation ...)] 
      Handles an exception. Exception Details: System.Runtime.InteropServices. (0x800703FA): ComeException Restoring the COM class factory for the region with CLSID BDEADF26-C265-11D0-BCED-00A0C90AB50F failed due to the following error: 800703fa An illegal operation was attempted on a registry key, clean to delete. (Exception from HRESULT: 0x800703FA).at Microsoft.SharePoint.Library.SPRequest..ctor ()in Microsoft.SharePoint.SPGlobal.CreateSPRequestAndSetIdentity (...)at Microsoft.SharePoint.SPRequestManager.GetContextRequest (SPRequestAuthenticationMode authenticationMode)at Microsoft.SharePoint.Administration.SPFarm.get_RequestAuthAny ()at Microsoft.SharePoint.Administration.SPAcl`1.CalculatePermissions ()at Microsoft.SharePoint.Administration.SPIisWebServiceApplication.CheckAccess (SPIisWebServiceApplicationRights rights)at Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplication.DoesUserHavePermissions (...)at Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplication.GetChangedTermSets (...)at SyncInvokeGetChangedTermSets (Object, Object [], Object [])at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke (Object Instance, Object Inputs [], Object [] and Outputs)at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin (MessageRpc and rpc)at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5 (MessageRpc and rpc)at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31 (MessageRpc and rpc)at System.ServiceModel.Dispatcher.MessageRpc.Process (boolean problem isOperationContextSet) 

    Reason

    0x800703fa

    This usually happens after the supervisor logs into the server for online visit with a service account and then logs off. For example, an administrator can log into a front-end Web server (WFE) with someone else’s farm account and then log off. This action dumps the registry keys to this bank account profile. This state makes the keys unavailable.for future use.

    Resolution

    Method 1

    Do not log in to positively serve interactive sessions using a service account.

    Method 2

    Disable the Windows User Profile Service feature. To stick with this, follow these steps:

    1. Open the Group Policy Writer (Gpedit.msc) on the affected server.

    2. Open the UserProfiles folder in the following path:

      Computer Configuration> Administrative Templates >> System User Profiles

    3. 0x800703fa

      Find some settings. Do not force the user’s Windows registry to be unloaded when the user logs off.

    4. Return the parameter to On.

    Additional Information

    For more information, see the upcoming MSDN Distributed Services Support Team article:

    COM + blog application may stop working on Windows Server 2008 when logged on as an identity user

    Your web browser (Internet Explorer) is looking for something retro. Try Zoho Desk.

    Copy link

    @ TheTerence June 10, 2018

    My damaged shell was at first in an account without administrator rights. After reading these articles, I logged in as an administrator and started the Ubuntu shell. The post first talked about reformatting the file, which allowed the shell instance to function normally.
    However, I uninstalled Ubuntu from Applications / Services and then accepted my non-admin account again, combined with reopening Ubuntu. All perfectly.

    My damaged shell was associated with a non-admin account. After reading articles like this, I logged in as an administrator and also started the Ubuntu shell. The post was mainly related to a file reformat that allowed my shell instance to work fine.
    However, I still locked Ubuntu for apps / services and then logged in to my non-admin account and reopened Ubuntu. All perfectly.

    Speed up your computer today with this simple download.

    0x800703fa
    0x800703fa
    0x800703fa
    0x800703fa
    0x800703fa
    0x800703fa
    0x800703fa
    0x800703fa
    0x800703fa
    0x800703fa