[SOLVED] [Server2012R2Essentials] Errors installing updates and Dot Net 4.7

[Sysnative Windows Update]

Yes, you can reboot after the script.

 

[phantom]

Done, Logs attached: https://wetransfer.com/downloads/3e8bb4b81898ebf6aaa9fea51147f60220190829144356/1cd5db7b290f81b647e30e3ce9d0703120190829144356/2b77b0

 

[phantom]

With regards to the Windows Server 2012 R2 Essentials dashboard problem I mentioned before. The Essentials Server services won't start because the "Windows Server Essentials Provider Registry Service" won't start "Error 1067: The process terminated unexpectedly". In the application event log I get the following event from the .NET Runtime relating to that service:

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: Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderException: Failed to configure the ServiceHost (see inner exception). ---> Microsoft.WindowsServerSolutions.Certificates.CertificatesException: Unable to find valid machine certificate on local store.
   at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProductConfiguratorBase._SetServiceCert(X509CertificateRecipientServiceCredential svcCertCred)
   at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProductConfiguratorBase._ConfigureServiceHost(ServiceHost serviceHost)
   at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProductConfiguratorBase.ConfigureServiceHost(ServiceHost serviceHost)
   --- End of inner exception stack trace ---
   at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProductConfiguratorBase.ConfigureServiceHost(ServiceHost serviceHost)
   at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderRegistry.Program.ConfigureEndpointsNormalMode(ServiceHost host)
   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()

Which mentions that its unable to find a valid machine certificate on the local store. The local machine certificate expired and thought I've renewed it and rebinded it to ISS as required, but apparently not. How do I fix this or where do I look for answers?

 

[Sysnative Windows Update]

This is likely related to the numerous .NET issues present on the system. I am fixing the errors as I come across them.

Can you please retry the update with ProcMon once again?

 

[phantom]

I hear you, but it was working before the certificate expired and I attempted to renew it. I think I caused this problem with the certificate I installed.

I've run the update. Here's the log: https://wetransfer.com/downloads/49f98a7e63bffb6dd82e5b7f010a975520190829155043/c70c59c0c1a204b7dfe9ecdd2af12f9520190829155043/6dcf66

 

[Sysnative Windows Update]

It's possible. Continue monitoring and we'll see what can be done.

Fix + updates with ProcMon.

 

[phantom]

Sorted my dashboard problem.

Ran fix and procmon (don't know what was running that made it so big this time): https://wetransfer.com/downloads/c5b5245c08ae9d210e02403f8743b45720190829170518/7bffd0145a616c8e0eb697a4c3ac288f20190829170518/a6b70d

 

[Sysnative Windows Update]

I see there was some network activity going on. Please run the fixes and then ProcMon.

 

[phantom]

Thank you for working so late to assist me.

Logs: https://wetransfer.com/downloads/fc05143f7fb35d3e2d584a9facc8554420190830071233/d4514d3948b09b20067fe62f634c653120190830071233/abe1a7

 

[Sysnative Windows Update]

No problem. Please do the following and then try updates.

 

[phantom]

Thanks

Here's the logs: https://wetransfer.com/downloads/a3bd5dd4739e78eeeb1483e07e17c62920190830135258/e0015c70e909a1d769d3a9f0137eb24120190830135258/696cae

 

[Sysnative Windows Update]

Here.

 

[phantom]

Done: https://wetransfer.com/downloads/5e532080b4350cf84b31257a69e2d28f20190830144612/f5c70a8cb56bf4bceeb4ce951603a68220190830144612/459ed7

 

[Sysnative Windows Update]

Here.

 

[phantom]

Done: https://wetransfer.com/downloads/c2b3afa9ae7c8001d6e96623638086ba20190831035945/faacc863f86e748774ce1960954db1d020190831035945/825e35

 

[Sysnative Windows Update]

Next.

 

[phantom]

Script ran without errors but Server crashed and rebooted during installation of the update

Rerunning update with ProcMon

 

[Sysnative Windows Update]

Crashed as in rebooted suddenly or reverted changes?

 

[phantom]

As in the Server suddenly rebooted.

I reran the update since the reboot and this time it was fine. Will post the logs now

Soon after completing the update the server rebooted again unexpectedly. I managed to get the logs though before the reboot.

 

[phantom]

Logs: Logfile.rar and 2 more files

EDIT: Sorry, the server didn't reboot the second time. Looks like there was a power failure and the internet went out for a few minutes because of the delay of swopping to backup power. When I reconnected to the server it was on the same screen i left it, so it hadnt rebooted