Azure devops Azure DevOps 2019 On Prem-创建集合时出错：“0”；步骤“创建框架安全命名空间”中的最小异常；

当我试图从管理控制台在Azure DevOps on premises上创建集合时，我遇到了一个错误

当DevOps管理

CreateCollection.Service.Analytics

部分时，似乎会发生这种情况。我在谷歌上找不到任何关于这个问题的参考资料

我在向导中选择继承过程模型，几分钟后启动安装时：

[15:15:32.793] Executing step: Enable analytics on-prem for new collections
[15:15:32.793]   Executing step: 'Enable analytics on-prem for new collections' AnalyticsCollection.EnableAnalyticsOnPrem (360 of 387)
[15:16:13.407]   [Warning] Impossible d'activer Analytics pour cette nouvelle collection. Vous pouvez y remédier en réactivant Analytics manuellement. Pour plus d'informations, consultez la documentation : https://go.microsoft.com/fwlink/?linkid=2093060.
[15:16:13.533]   [Warning] Analytics failed to enable for new collection due to: Le bail de AnalyticsStateService.SetFeatureState, dont le propriétaire est f24b9929-5d00-498c-9b4c-1e6d8c5f8f77, obtenu le 10/03/2020 14:15:33 par le processus abde3e12-0d37-4751-a1fe-23387f8c5268 a expiré le 10/03/2020 14:16:03
*** 
in english : 
Unable to enable Analytics for this new collection. You can fix it by reactivating Analytics manually (so later no ??? )
The lease for AnalyticsStateService.SetFeatureState, owned by f24b9929-5d00-498c-9b4c-1e6d8c5f8f77, obtained on 10/03/2020 14:15:33 by the process abde3e12-0d37-4751-a1fe-23387f8c5268 expired on 10 / 03/2020 14:16:03 
***
[15:16:13.540] Step passed (with warnings): Enable analytics on-prem for new collections. Execution time: 40 seconds.
[15:16:13.540]   [StepDuration] 40,7454734
[15:16:13.597]   [GroupDuration] 67,5660477
[15:16:13.597]   [OperationDuration] 67,56617
[15:16:13.597] +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[15:16:13.597] ++ Executing - Operation: CreateCollection.Service.Analytics.Sdk, Group: CreateCollection.Service.Analytics.Sdk
[15:16:13.597] +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[15:16:13.597] Step skipped: Queue Analytics Maintain Staging Schedules Job.
[15:16:13.600]   [GroupDuration] 0,0046515
[15:16:13.600]   [OperationDuration] 0,0046985
[15:16:13.600] +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[15:16:13.600] ++ Executing - Operation: CreateCollection.Service.Notifications, Group: CreateCollection.Service.Notifications
[15:16:13.600] +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[15:16:13.600] Executing step: Load service tokens
[15:16:13.600]   Executing step: 'Load service tokens' FrameworkTokens.ConfigureServiceTokens (362 of 387)
[15:16:13.603] Step passed: Load service tokens. Execution time: 3 milliseconds.
[15:16:13.603]   [StepDuration] 0,0002612
[15:16:13.603] +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Executing step: Create Framework Security Namespaces
[15:16:13.603]   Executing step: 'Create Framework Security Namespaces' Security.CreateSecurityNamespaces (363 of 387)
[15:16:13.603]   There are 1 security namespaces to create/update.
[15:16:13.603]   Validating 'EventSubscription' security namespace.
[15:16:13.603]   Creating/updating security namespace(s).
[15:16:13.603]   [Error] Le bail de AnalyticsStateService.SetFeatureState, dont le propriétaire est f24b9929-5d00-498c-9b4c-1e6d8c5f8f77, obtenu le 10/03/2020 14:15:33 par le processus abde3e12-0d37-4751-a1fe-23387f8c5268 a expiré le 10/03/2020 14:16:03
*** 
in english : 
Same error but with stack trace
The lease for AnalyticsStateService.SetFeatureState, owned by f24b9929-5d00-498c-9b4c-1e6d8c5f8f77, obtained on 10/03/2020 14:15:33 by the process abde3e12-0d37-4751-a1fe-23387f8c5268 expired on 10 / 03/2020 14:16:03 
***
[15:16:13.633]   Microsoft.TeamFoundation.Framework.Server.LeaseLostException: Le bail de AnalyticsStateService.SetFeatureState, dont le propriétaire est f24b9929-5d00-498c-9b4c-1e6d8c5f8f77, obtenu le 10/03/2020 14:15:33 par le processus abde3e12-0d37-4751-a1fe-23387f8c5268 a expiré le 10/03/2020 14:16:03
[15:16:13.633]      à Microsoft.TeamFoundation.Framework.Server.VssRequestContext.CheckCanceled(Boolean throwIfShutdown)
[15:16:13.633]      à Microsoft.TeamFoundation.Framework.Server.VssRequestContext.get_ServiceProvider()
[15:16:13.633]      à Microsoft.TeamFoundation.Framework.Server.VssRequestContextExtensions.GetService[TService](IVssRequestContext context)
[15:16:13.633]      à Microsoft.VisualStudio.Services.Framework.SecurityStepPerformer.CreateOrUpdateSecurityNamespaces(IVssRequestContext requestContext, ServicingContext servicingContext, LocalNamespaceDescriptionStepData[] securityNamespaceDescriptions)
[15:16:13.633]      à Microsoft.TeamFoundation.Framework.Server.TeamFoundationStepPerformerBase.PerformHostStep(String servicingOperation, ServicingOperationTarget target, IServicingStep servicingStep, String stepData, ServicingContext servicingContext)
[15:16:13.633]      à Microsoft.TeamFoundation.Framework.Server.TeamFoundationStepPerformerBase.PerformStep(String servicingOperation, ServicingOperationTarget target, String stepType, String stepData, ServicingContext servicingContext)
[15:16:13.633]      à Microsoft.TeamFoundation.Framework.Server.ServicingStepDriver.PerformServicingStep(ServicingStep step, ServicingContext servicingContext, ServicingStepGroup group, ServicingOperation servicingOperation, Int32 stepNumber, Int32 totalSteps)
[15:16:13.633] Step failed: Create Framework Security Namespaces. Execution time: 30 milliseconds.

这是我在Azure DevOps上从头开始创建的第一个集合，但我已经从tfs 2015迁移了一个集合，它运行得非常好。我不想在tfs2015上创建我的集合，只是为了将其迁移到devops：(

报告没有配置，我知道我可以在以后真正想使用它们时配置它们。我没有安装SSR，但如果有必要，我会这样做

分析服务功能安装在我的SQL Server实例上。SQL Server安装在同一台服务器上

集合的数据库已创建，但控制台中的状态为脱机，我无法重新执行创建工作。如果出现错误，我必须使用命令行将其删除

---

编辑：

我用xml流程模型测试了一个创建，它正在工作。在设置页面中，我看到分析被激活

编辑2：多亏了@PatrickLu MSFT，这就是工作。 在发布之前，我已经尝试重新启动服务器，但没有成功

这次我尝试从SQL Configuration Manager重新启动所有SQL服务并重新创建集合，但仍然失败，这是不够的

---

然后我使用服务重新启动了服务：SQL Server（MSSQLServer），我按照Patrick告诉我的重新启动了服务器。它成功了，我能够用继承模型创建我的集合！

根据您的描述，您的SQL服务可能出了问题

请尝试重新启动SQL Server服务，如果它在尝试停止该服务时挂断。然后您可以尝试重新启动服务器并尝试再次创建新集合

如果这不起作用，也请检查事件视图中是否有一些信息。这可能有助于查明问题