Erreur « L’accès au Registre demandé n’est pas autorisé » dans la création de flux de travail OOB SharePoint 2013

Symptômes

L’erreur suivante s’est produite lorsque vous tentez de créer un flux de travail OOB (out-of-the-box) dans SharePoint 2013 (Nov2017Cu) :

Une erreur inattendue est survenue.

Le service uls (Unified Logging Service) affiche également les détails suivants (mis en surbrillant) :

06/02/2019 10:33:12.14 w3wp.exe (Servername:0x0A18) 0x3118 SharePoint Foundation General 8nca Medium Application error when access /_layouts/15/CstWrkflIP.aspx, Error=Requested registry access is not allowed. at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable) at Microsoft.Win32.Registry.GetValue (String keyName, String valueName, Object defaultValue) at Microsoft.Office.InfoPath.Server.Util.UrlManager.<>c__DisplayClass1. b__0() at Microsoft.Office.Server.Security.SecurityContext.RunAsProcess(CodeToRunElevated secureCode) at Microsoft.Office.InfoPath.Server.Util.UrlManager.OpenFileNameMap() at Microsoft.Office.InfoPath.Server.Util.UrlManager..cctor() 4445bd9e-70b9-008f-6bc3-c842222bad98

Notes

Consultez la section Plus d’informations pour un affichage plus complet de l’erreur dans le uls.

Cause

Le compte du pool d’applications n’a pas l’autorisation requise pour créer le flux de travail.

Résolution

Pour résoudre ce problème, essayez les étapes suivantes :

  1. Ajoutez le compte de pool d’applications de l’application web aux groupes WSS_WPG et WSS_Admin_WPG.

  2. Appliquez l’accès en lecture aux clés de Registre suivantes :

    HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\Office Server\15.0
    HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\Secure
    
  3. Redémarrez le serveur.

Si le problème persiste, contactez le support technique et le service clientèle Microsoft.

Plus d’informations

Voici un affichage plus complet du uls :

06/02/2019 10:33:12.03 w3wp.exe (Servername: 0x0A18) 0x3118 SharePoint Foundation Workflow Services aighj Medium Can’t find WorkflowServiceProxy or its service application proxy type name is null 4445bd9e-70b9-008f-6bc3-c842222bad98

06/02/2019 10:33:12.14 w3wp.exe (Servername:0x0A18) 0x3118 SharePoint Foundation General 8nca Medium Application error when access /_layouts/15/CstWrkflIP.aspx, Error=Requested registry access is not allowed. at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable) at Microsoft.Win32.Registry.GetValue (String keyName, String valueName, Object defaultValue) at Microsoft.Office.InfoPath.Server.Util.UrlManager.<>c__DisplayClass1. b__0() at Microsoft.Office.Server.Security.SecurityContext.RunAsProcess(CodeToRunElevated secureCode) at Microsoft.Office.InfoPath.Server.Util.UrlManager.OpenFileNameMap() at Microsoft.Office.InfoPath.Server. Util.UrlManager.. cctor() 4445bd9e-70b9-008f-6bc3-c842222bad98

06/02/2019 10:33:12.14 w3wp.exe (Servername: 0x0A18) 0x3118 SharePoint Foundation Runtime 6616 Critical Requested registry access is not allowed. 4445bd9e-70b9-008f-6bc3-c842222bad98 02/06/2019 10:33:12.14 w3wp.exe (Servername: 0x0A18) 0x3118 SharePoint Foundation General ajlz0 High Getting Error Message for Exception System.TypeInitializationException: The type initializer for 'Microsoft.Office.InfoPath.Server.Util.UrlManager' threw an exception. ---> System.Security.SecurityException : l’accès demandé au Registre n’est pas autorisé. at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable) at Microsoft.Win32.Registry.GetValue(String keyName, String valueName, Object defaultValue) at Microsoft.Office.InfoPath.Server.Util.UrlManager.<>c__DisplayClass1. b__0() at Microsoft.Office.Server.Security.SecurityContext.RunAsProcess(CodeToRunElevated secureCode) at Microsoft.Office.InfoPath.Server.Util.UrlManager.OpenFileNameMap() at Microsoft.Office.InfoPath.Server.Util.UrlManager..cctor() --- End of inner exception stack trace --- at Microsoft.Office.InfoPath.Server.Util.UrlManager.GetConverterGeneratedFilePath(ConverterGeneratedFile file, Document document) at Microsoft.Office.InfoPath.Server.SolutionLifetime.ScriptIncludes.RenderCssLinksToHeader(Control ctrl, Document document, Boolean ribbonEnabled, Boolean isDisplayMode) at Microsoft.Office.InfoPath.Server.Controls.XmlFormView.TryToAddCssLinksToHeader() at Microsoft.Office.InfoPath.Server.Controls.XmlFormView.OnDataBindHelper() at Microsoft.Office.InfoPath.Server.Controls.XmlFormView.OnDataBinding(EventArgs e) at System.Web.UI.WebControls.WebParts.Part.DataBind() at System.Web.UI.Control.DataBindChildren() at System.Web.UI.Control.DataBind(Boolean raiseOnDataBinding) at System.Web.UI.Control.DataBindChildren() at System.Web.UI.Control.DataBind(Boolean raiseOnDataBinding) at System.Web.UI.Control.DataBindChildren() at System.Web.UI.Control.DataBind(Boolean raiseOnDataBinding) at System.Web.UI.Control.DataBindChildren() at System.Web.UI.Control.DataBind(Boolean raiseOnDataBinding) at System.Web.UI.Control.DataBindChildren() at System.Web.UI.Control.DataBind(Boolean raiseOnDataBinding) at System.Web.UI.Control.DataBindChildren() at System.Web.UI.Control.DataBind(Boolean raiseOnDataBinding) at Microsoft.Office.Workflow.CstWrkflIPPage.LoadFromWorkflowTemplate(EventArgs ea) at Microsoft.Office.Workflow.CstWrkflIPPage.OnLoad(EventArgs ea) at System.Web.UI.Control.LoadRecursive() 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 System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) 4445bd9e-70b9-008f-6bc3-c842222bad98

Encore besoin d’aide ? Go to SharePoint Community.