Quick Solution 5 : Requested registry access is not allowed


Error Message

The timer job completed, but failed on one or more machines in the farm

SharePoint ULS:
<date time> OWSTIMER.EXE (0x06C0) 0x07E4 SharePoint Foundation Timer 6398 Critical The Execute method of job definition Microsoft.SharePoint.Administration.SPServiceApplicationInstanceProvisioningJobDefinition (ID 94bba7da-a1d1-4416-8b29-90097d834a3b) threw an exception. More information is included below.  Requested registry access is not allowed. d76d33cf-1737-48b9-b880-6d4561081fa2

Exception stack trace:  
 at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable)   
 at Microsoft.Office.Server.Utilities.SetupUtility.get_InstallLocation()   
 at Microsoft.Office.Server.Administration.UserProfileApplication.get_InstallPath()   
 at Microsoft.SharePoint.Administration.SPIisWebServiceApplication.ProvisionApplicationInstance()   
 at Microsoft.SharePoint.Administration.SPIisWebServiceApplication.ProvisionLocal(SPServiceInstance serviceInstance) 

System Log:
Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          <date time>
Event ID:      6398
Task Category: Timer
Level:         Critical
Keywords:     
User:          <user alias>
Computer:      <computer name>
Description:
The Execute method of job definition Microsoft.SharePoint.Administration.SPServiceApplicationInstanceProvisioningJobDefinition (ID 94bba7da-a1d1-4416-8b29-90097d834a3b) threw an exception. More information is included below.

Requested registry access is not allowed.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-SharePoint Products-SharePoint Foundation" Guid="{6FB7E0CD-52E7-47DD-997A-241563931FC2}" />
    <EventID>6398</EventID>
    <Version>14</Version>
    <Level>1</Level>
    <Task>12</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2011-03-08T03:16:46.198079000Z" />
    <EventRecordID>26617</EventRecordID>
    <Correlation ActivityID="{D76D33CF-1737-48B9-B880-6D4561081FA2}" />
    <Execution ProcessID="1728" ThreadID="2020" />
    <Channel>Application</Channel>
    <Computer>SPS2010-01.contoso.com</Computer>
    <Security UserID="S-1-5-21-3468372412-3115835394-1960983456-1105" />
  </System>
  <EventData>
    <Data Name="string0">Microsoft.SharePoint.Administration.SPServiceApplicationInstanceProvisioningJobDefinition</Data>
    <Data Name="string1">94bba7da-a1d1-4416-8b29-90097d834a3b</Data>
    <Data Name="string2">Requested registry access is not allowed.</Data>
  </EventData>
</Event>

 

Causes

The issue is caused by the insufficient permission on registry key: 

at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable)   

Solutions 

To solve the issue, please follow these steps:

  1. Use the Process Monitor to monitor the registry, once you get the following ACCESS DENIED message(You can filter the result with “Result contains Access Denied”):  

    Date & Time:      <date time>

    Event Class:        Registry

    Operation: RegOpenKey

    Result:  ACCESS DENIED

    Path:     HKLM\SOFTWARE\Microsoft\Office Server\14.0

    TID:        2020

    Duration:             0.0000297

    Desired Access:                Read

  2. Open Registry Editor (Start > Run, type regedit)
  3. Open key: HKLM\SOFTWARE\Microsoft\Office Server\14.0(got from Process Monitor from step 1)
  4. Assign the SharePoint Timer Service account the Read permission to this key
Comments (7)
  1. Ben says:

    This fixed it! Thanks

  2. GabbyGibson says:

    +1 for a life saver. You’re my hero, buddy!

  3. jim says:

    Cheers, Life saving post!

  4. Suzanne says:

    Thanks for posting this solution. Worked flawlessly!

  5. sam says:

    worked great on SharePoint 2013. thanks..

  6. Kenneth says:

    FIxed it for me aswell. Tried so many other "fixes" for this problem.
    The main issue in my case was that My Site didn’t list my tasks, it said "Sorry, we’re having trouble refreshing your tasks" and none of the other fixes on Google worked.

    Found the error above in my ULS log and voilá 🙂

    Thanks!

  7. jackadision says:

    You can also fix this type of sharepoint error by the help of Repair tool, for more information visit:
    http://sharepoint.filerepairtool.net/blog

Comments are closed.

Skip to main content