Painel do Windows SBS 2011 + Windows Server * Os serviços não serão iniciados devido ao serviço Windows Server Service Provider Registry

Question

Eu tenho uma caixa do Windows Server SBS 2011 que está tendo alguns problemas estranhos relacionados ao Registro de Provedor de Serviço do Windows Server . Um número de serviços do servidor do Windows estava sendo executado em problemas de início e eu segui-lo de volta para este serviço. Suas dependências são iniciadas e executadas sem erros que eu possa ver.

Este é o erro que recebo quando tento iniciar o serviço:

Error 1067: The process terminated unexpectedly.

Os erros do visualizador de eventos estão listados abaixo (2)

link

E um erro no .net:

Source: .Net Runtime
Event ID: 1025

Application: ProviderRegistryService.exe
Framework Version: v4.0.30319
Description: The application requested process termination through System.Environment.FailFast(string message).
Message: Unhandled exception in OnStart: System.InvalidOperationException: Service ServiceRegistryProvider was not found on computer '.'. ---> System.ComponentModel.Win32Exception: The specified service does not exist as an installed service
   --- End of inner exception stack trace ---
   at System.ServiceProcess.ServiceController.GenerateNames()
   at System.ServiceProcess.ServiceController.get_DisplayName()
   at Microsoft.WindowsServerSolutions.Common.ServiceUtility.GetDisplayName(String serviceName)
   at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProductConfigurator.LogServiceStartFailure(String serviceName, String info)
   at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderRegistry.ServiceShell.OpenHost()
   at Microsoft.WindowsServerSolutions.Common.Services.WssgServiceBase.OnStart(String[] args)
Stack:
   at System.Environment.FailFast(System.String, System.Exception)
   at Microsoft.WindowsServerSolutions.Common.Services.WssgServiceBase.OnStart(System.String[])
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

Depois de algumas pesquisa , encontrei alguns casos semelhantes, 1 lidou com o porta usada pelo serviço que não consigo encontrar listado em qualquer lugar, incluindo o arquivo de configuração para o serviço.

Eu executei recentemente um SFC Scan no arquivo e em todo o servidor que não retornou nenhum erro. O que eu estou procurando é se eu preciso trabalhar na tentativa de reinstalar o serviço ou se poderia ser um erro .net etc. Qualquer ajuda seria apreciada.

    

Answer 1

Eu também tive esse problema, no entanto, eu encontrei um Tópico de TechNet que realmente me ajudou a dar uma pista sobre isso. Basicamente, o problema era que, de alguma forma, o certificado de identidade dos servidores era excluído do armazenamento de certificados e precisava ser regenerado. Quando o certificado está ausente, o serviço "Windows Server Service Provider Registry" falha, o que faz com que vários outros serviços dependentes também falhem.

Vou postar novamente a mesma coisa que coloquei no tópico do TechNet abaixo. Espero que isso ajude alguém!

I had this exact same problem! Thank you so much Robert for posting a link to that script! That is truly an amazing Powershell script.

I had all the same errors that AK772 mentioned, but I chose to zoom in on a different issue that the script pointed out. When I ran the "Test CA Infrastructure" step it found several errors. When I looked at what the script was doing there it was comparing the server certificate thumbprint in the registry (HKLM:\Software\Microsoft\Windows Server\Identity) with the personal certificates (Personal Certificates in the Certificate snap-in using MMC). When I looked through them individually, sure enough the thumbprint in the registry didn't exist in my certificate store. I have NO idea how this could have happened!

However, from there, I changed my Google search criteria and found the following excellent article: http://titlerequired.com/2013/04/29/windows-server-2012-essentials-an-error-prevented-the-dashboard-from-opening/

This told more about that error and showed how to regenerate the certificate identity in the registry. This totally saved me! Once I ran through the steps that he outlines, even though I got a timeout error towards the end, I could see that the certificate thumbprint had changed in the registry and now existed in my personal certificate store.

Once I saw this, I tried going into services and manually starting the stopped "Windows Server Service Provider Registry" service. Sure enough it started right up, no error this time. Finally, I restarted the server so that all of the other dependent services would come back up and re-ran the linked script above and everything was perfect.