none
...this is caused by removing an SPFeatureDefinition without writing upgrade code to remove references to the feature from each

    Question

  • I'm getting this error logged in the ULS when I try to remove a User Profile Service I created via Central Admin. The full error is:

    The configuration database was queried for a non-existent object with the id 86a000a5-2498-4b78-b007-4540faad15b5. Most commonly, this is caused by removing an SPFeatureDefinition without writing upgrade code to remove references to the feature from each site.

    Any ideas on how to un provision this?


    Kevin W. Gagel
    Thursday, August 19, 2010 10:59 PM

Answers

  • I solved it. Pretty simple actually. I had to login with the account that created the service. Then I could delete it.
    Kevin W. Gagel
    Friday, August 20, 2010 6:22 PM

All replies

  • Looks like a feature was not removed cleanly. Try uninstalling the feature from the farm. You can do this by using powershell or stsadm:

    stsadm -o uninstallfeature -id 86a000a5-2498-4b78-b007-4540faad15b5 -force

    Uninstall-SPFeature -id 86a000a5-2498-4b78-b007-4540faad15b5 -force

    Friday, August 20, 2010 1:19 PM
  • I tried it but it still cannot be removed. It looks like the GUID changes with each attempt and it actually is the timer job that is supposed to un-provision the service...

    Here is a full log of the activity while trying to un-provision the "My Sites Application":

    Medium	Name=Request (POST:http://XXX.XXX.XXX.XXX:YYYY/_admin/ServiceApplicationDelete.aspx?id=be51aebfbe054118812dffb8526c9677&IsDlg=1)	b4caa5c1-0db9-4523-9735-f03999084e0c
    Medium	Site=/	b4caa5c1-0db9-4523-9735-f03999084e0c
    High	Leaving Monitored Scope (PostAuthenticateRequestHandler). Execution Time=3.27946708310693	b4caa5c1-0db9-4523-9735-f03999084e0c
    Medium	Updating SPPersistedObject UserProfileApplication Name=My Sites Application. Version: 258894 Ensure: False, HashCode: 5785443, Id: be51aebf-be05-4118-812d-ffb8526c9677, Stack: at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()  at Microsoft.SharePoint.Administration.SPIisWebServiceApplication.Update()  at Microsoft.Office.Server.Administration.UserProfileApplication.Update()  at Microsoft.Office.Server.Administration.UserProfileApplication.ResetILMFlags()  at Microsoft.Office.Server.Administration.UserProfileApplication.Unprovision(Boolean deleteData)  at Microsoft.SharePoint.ApplicationPages.ServiceApplicationDeletePage.OkButton_Click(Object sender, EventArgs e)  at System.EventHandler.Invoke(Object sender, EventArgs e)  at System.Web.UI.WebControls.Button.OnClick(EventArgs e)  at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)  at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)  at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)  at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)  at System.Web.UI.Page.ProcessRequest()  at System.Web.UI.Page.ProcessRequest(HttpContext context)  at ASP._admin_serviceapplicationdelete_aspx.ProcessRequest(HttpContext context)  at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()  at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)  at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)  at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)  at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)  at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)  at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)  at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)  at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)	b4caa5c1-0db9-4523-9735-f03999084e0c
    High	Scheduling service application instance unprovisioning job for service application with name 'My Sites Application' and type 'Microsoft.Office.Server.Administration.UserProfileApplication'.	b4caa5c1-0db9-4523-9735-f03999084e0c
    Medium	Updating SPPersistedObject SPServiceApplicationInstanceProvisioningJobDefinition Name=My Sites Application. Version: -1 Ensure: True, HashCode: 61334830, Id: a4523dd5-0fb6-411f-b032-bf83dee3d0e3, Stack: at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()  at Microsoft.SharePoint.Administration.SPJobDefinition.Update()  at Microsoft.SharePoint.Administration.SPServiceApplication.ScheduleOneTimeJob(SPJobDefinition jobDefinition)  at Microsoft.SharePoint.Administration.SPServiceApplication.UnprovisionInstances()  at Microsoft.SharePoint.Administration.SPIisWebServiceApplication.Unprovision(Boolean deleteData)  at Microsoft.Office.Server.Administration.UserProfileApplication.Unprovision(Boolean deleteData)  at Microsoft.SharePoint.ApplicationPages.ServiceApplicationDeletePage.OkButton_Click(Object sender, EventArgs e)  at System.EventHandler.Invoke(Object sender, EventArgs e)  at System.Web.UI.WebControls.Button.OnClick(EventArgs e)  at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)  at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)  at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)  at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)  at System.Web.UI.Page.ProcessRequest()  at System.Web.UI.Page.ProcessRequest(HttpContext context)  at ASP._admin_serviceapplicationdelete_aspx.ProcessRequest(HttpContext context)  at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()  at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)  at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)  at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)  at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)  at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)  at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)  at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)  at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)	b4caa5c1-0db9-4523-9735-f03999084e0c
    Medium	Updating SPPersistedObject SPServiceApplicationInstanceProvisioningJobDefinition Name=My Sites Application. Version: 258922 Ensure: False, HashCode: 61334830, Id: a4523dd5-0fb6-411f-b032-bf83dee3d0e3, Stack: at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()  at Microsoft.SharePoint.Administration.SPJobDefinition.Update()  at Microsoft.SharePoint.Administration.SPServiceApplication.ScheduleOneTimeJob(SPJobDefinition jobDefinition)  at Microsoft.SharePoint.Administration.SPServiceApplication.UnprovisionInstances()  at Microsoft.SharePoint.Administration.SPIisWebServiceApplication.Unprovision(Boolean deleteData)  at Microsoft.Office.Server.Administration.UserProfileApplication.Unprovision(Boolean deleteData)  at Microsoft.SharePoint.ApplicationPages.ServiceApplicationDeletePage.OkButton_Click(Object sender, EventArgs e)  at System.EventHandler.Invoke(Object sender, EventArgs e)  at System.Web.UI.WebControls.Button.OnClick(EventArgs e)  at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)  at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)  at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)  at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)  at System.Web.UI.Page.ProcessRequest()  at System.Web.UI.Page.ProcessRequest(HttpContext context)  at ASP._admin_serviceapplicationdelete_aspx.ProcessRequest(HttpContext context)  at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()  at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)  at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)  at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)  at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)  at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)  at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)  at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)  at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)	b4caa5c1-0db9-4523-9735-f03999084e0c
    High	SPTimerJobAsyncResult 'a4523dd5-0fb6-411f-b032-bf83dee3d0e3': Created SPTimerJobAsyncResult.	b4caa5c1-0db9-4523-9735-f03999084e0c
    High	Waiting for service application instance unprovisioning job to complete for service application with name 'My Sites Application' and type 'Microsoft.Office.Server.Administration.UserProfileApplication'.	b4caa5c1-0db9-4523-9735-f03999084e0c
    High	SPTimerJobAsyncResult 'a4523dd5-0fb6-411f-b032-bf83dee3d0e3': SPTimerJobAsyncResult.End() invoked.	b4caa5c1-0db9-4523-9735-f03999084e0c
    High	SPTimerJobAsyncResult 'a4523dd5-0fb6-411f-b032-bf83dee3d0e3': Timer job has not completed. Blocking until job completes.	b4caa5c1-0db9-4523-9735-f03999084e0c
    High	Blocking until timer job 'a4523dd5-0fb6-411f-b032-bf83dee3d0e3' has completed.	b4caa5c1-0db9-4523-9735-f03999084e0c
    Medium	The configuration database was queried for a non-existent object with the id a4523dd5-0fb6-411f-b032-bf83dee3d0e3. Most commonly, this is caused by removing an SPFeatureDefinition without writing upgrade code to remove references to the feature from each site.	b4caa5c1-0db9-4523-9735-f03999084e0c
    High	Job 'My Sites Application' failed while running on server SHAREPOINTSERVER. Error: Access to the path 'Global\Microsoft.SharePoint.SPIisProvisioningLock' is denied.	b4caa5c1-0db9-4523-9735-f03999084e0c
    High	SPTimerJobAsyncResult 'a4523dd5-0fb6-411f-b032-bf83dee3d0e3': An error occurred while waiting for completion: Microsoft.SharePoint.SPException: The timer job completed, but failed on one or more machines in the farm.  at Microsoft.SharePoint.Administration.SPJobDefinition.WaitForCompletion(TimeSpan timeout)  at Microsoft.SharePoint.Administration.SPTimerJobAsyncResult.WaitForCompletion(Object state)	b4caa5c1-0db9-4523-9735-f03999084e0c
    Unexpected	Microsoft.SharePoint.SPException: The timer job completed, but failed on one or more machines in the farm. at Microsoft.SharePoint.Administration.SPTimerJobAsyncResult.End()  at Microsoft.SharePoint.Administration.SPServiceApplication.UnprovisionInstances()  at Microsoft.SharePoint.Administration.SPIisWebServiceApplication.Unprovision(Boolean deleteData)  at Microsoft.Office.Server.Administration.UserProfileApplication.Unprovision(Boolean deleteData)  at Microsoft.SharePoint.ApplicationPages.ServiceApplicationDeletePage.OkButton_Click(Object sender, EventArgs e)  at System.EventHandler.Invoke(Object sender, EventArgs e)  at System.Web.UI.WebControls.Button.OnClick(EventArgs e)  at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)  at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)  at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)	b4caa5c1-0db9-4523-9735-f03999084e0c
    Medium	Leaving Monitored Scope (Request (POST:http://XXX.XXX.XXX.XXX:YYYY/_admin/ServiceApplicationDelete.aspx?id=be51aebfbe054118812dffb8526c9677&IsDlg=1)). Execution Time=7390.02247492349	b4caa5c1-0db9-4523-9735-f03999084e0c
    

     

    The access denied is pretty telling but a search on Goolge returned 0 results...


    Kevin W. Gagel

    Friday, August 20, 2010 5:20 PM
  • What account is the timer service running under ? If possible, change the service account for the timer service and see if it makes any difference.
    Friday, August 20, 2010 5:50 PM
  • I solved it. Pretty simple actually. I had to login with the account that created the service. Then I could delete it.
    Kevin W. Gagel
    Friday, August 20, 2010 6:22 PM
  • I'm getting the same error:  

    The service instance "" could not be provisioned because of the following error: 
    Access to the path 'Global\Microsoft.SharePoint.SPIisProvisioningLock' is denied."

    ...but in this case it's when creating new service applications.

    I had problems unprovisioning the old broken service apps, even when logged in with the account that created them.

    An attempt to start/stop instance of service Microsoft.Office.Server.Search.Administration.SearchQueryAndSiteSettingsService on server WEBSERVER did not succeed. 
    Re-run the action via UI or command line on the specified server. Additional information is below.
    
    Access to the path 'Global\Microsoft.SharePoint.SPIisProvisioningLock' is denied.
    

    The solution was to stop the services under 'Manage services on server ' before deleting the service apps.

    I'm assuming then, as mentioned below, that the features havn't been removed and are now causing problems for the re-creation process.


     

    Friday, January 21, 2011 10:35 AM
  • I get this error while creating the top level site from a custom Template.
    Anshuman Dash
    Friday, August 26, 2011 7:58 AM
  • I got the same Error with another webpart. But login with the account that created did not help :<
    Wednesday, October 19, 2011 6:23 AM
  • Hi Rodin3D,

    Were you able to figure the solution for that error. I'm also getting the same error when accessing the visual webpart


    Anusha

    Monday, February 27, 2012 2:41 PM
  • Hi All 

    Error: "'Global\Microsoft.SharePoint.SPIisProvisioningLock' is denied."

    I also had same issue. In my environment which has two SharePoint Application Servers. I could able to solve this changing SP Timer Service account to  "Farm admin" account in both servers. 

    Thanks

    Damith.

    • Proposed as answer by Nick Buhaets Wednesday, December 21, 2016 8:33 PM
    Thursday, May 31, 2012 9:18 AM