在管理中心创建web应用程序时提示：指定的路径无法在此时使用(异常来自 HRESULT:0x80070094)

详细错误信息：

指定的路径无法在此时使用。 (异常来自 HRESULT:0x80070094)   在 System.DirectoryServices.DirectoryEntry.CommitChanges() 
   在 Microsoft.SharePoint.Administration.SPMetabaseObject.Provision() 
   在 Microsoft.SharePoint.Administration.SPProvisioningAssistant.ProvisionApplicationPool(String applicationPoolId, Int32 identityType, String username, SecureString secStrPassword) 
   在 Microsoft.SharePoint.Administration.SPApplicationPool.ProvisionInternal(SecureString sstrPassword) 
   在 Microsoft.SharePoint.Administration.SPApplicationPool.Provision() 
   在 Microsoft.SharePoint.Administration.SPWebApplication.Provision() 
   在 Microsoft.SharePoint.ApplicationPages.ExtendVirtualServerPage.BtnSubmit_Click(Object sender, EventArgs e) 
   在 System.Web.UI.WebControls.Button.OnClick(EventArgs e) 
   在 System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) 
   在 System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) 
   在 System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) 
   在 System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) 
   在 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 

解决办法：

Windows SharePoint Services Timer Service Causes Provisioning Failure
Posted by Scot Hillier under Apress
 
Several times now, I have experienced site provisioning errors that are related to the Windows SharePoint Services Timer Service. The symptoms can be:

- You create a new Web Application, but it does not get provisioned to every web front end, or
- You create a new Site and it seems to take forever to complete.

Both of these problems were cured for me by restarting the timer service on all servers.

The timer service has a known memory leak. Most of the information I have found says it’s not an issue because the service will blow out and restart on its own. However, it definitely is affecting site provisioning. Therefore, the best practice is to schedule this service to restart based on memory growth. You can do this if you monitor the service with Microsoft Operations Manager (MOM). If you can’t monitor it, then you can create a simple batch file and schedule it to run every few hours. The batch file would just be…

NET STOP “Windows SharePoint Services Timer Service”
NET START “Windows SharePoint Services Timer Service”

Let me know how this approach works out. Hopefully, this issue gets fixed soon.