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’affiche 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 de journalisation unifiée (ULS) affiche également les détails suivants (mis en surbrillance) :
02/06/2019 10:33:12.14 w3wp.exe (Servername:0x0A18) 0x3118 SharePoint Foundation General 8nca Medium Application error when access /_layouts/15/CstWrkflIP.aspx, <mark>Error=Requested registry access is not allowed. at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable) at Microsoft.Win32.Registry.GetValue</mark> (String keyName, String valueName, Object defaultValue) at Microsoft.Office.InfoPath.Server.Util.UrlManager.<>c__DisplayClass1.<OpenFileNameMap>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
Remarque
Consultez la section Plus d’informations pour obtenir un affichage plus complet de l’erreur dans l’ULS.
Cause
Le compte du pool d’applications ne dispose pas de l’autorisation requise pour créer le workflow.
Résolution
Pour résoudre ce problème, essayez les étapes suivantes :
Ajoutez le compte de pool d’applications de l’application web aux groupes WSS_WPG et WSS_Admin_WPG.
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
Redémarrez le serveur.
Si le problème persiste, contactez le service clientèle et le support microsoft.
Informations supplémentaires
Voici un affichage plus complet de l’ULS :
02/06/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
02/06/2019 10:33:12.14 w3wp.exe (Servername:0x0A18) 0x3118 SharePoint Foundation General 8nca Medium Application error when access /_layouts/15/CstWrkflIP.aspx, <mark>Error=Requested registry access is not allowed. at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable) at Microsoft.Win32.Registry.GetValue</mark> (String keyName, String valueName, Object defaultValue) at Microsoft.Office.InfoPath.Server.Util.UrlManager.<>c__DisplayClass1.<OpenFileNameMap>b__0() at Microsoft.Office.Server.Security.SecurityContext.RunAsProcess(CodeToRunElevated secureCode) at Microsoft.Office.InfoPath.Server.Util.UrlManager.OpenFileNameMap() at <mark>Microsoft.Office.InfoPath.Server</mark>.Util.UrlManager..cctor() 4445bd9e-70b9-008f-6bc3-c842222bad98
02/06/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: 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.<OpenFileNameMap>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 <mark>Microsoft.Office.Workflow.CstWrkflIPPage.LoadFromWorkflowTemplate(EventArgs ea)</mark> 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 ? Accédez au site de la Communauté SharePoint.
Commentaires
https://aka.ms/ContentUserFeedback.
Bientôt disponible : Tout au long de 2024, nous allons supprimer progressivement GitHub Issues comme mécanisme de commentaires pour le contenu et le remplacer par un nouveau système de commentaires. Pour plus d’informations, consultezEnvoyer et afficher des commentaires pour