Windows Server 2012 Essentials, An Error prevented the Dashboard from opening
April 29, 2013 37 Comments
This is an issue that has caught me out once or twice in my testing and general messing about with Essentials over the last age, and also someone in the forum just posted a question along these lines so i thought it worth a post. I have been struggling with a bit of ‘writers block’* recently and this seemed to be something easy to get back into blogging again with.
* I do not consider myself to be a writer, merely a lazy admin who had nothing interesting to say.
You have somehow deleted a certificate, and then the Dashboard fails to open. That could be through IIS from the server certificates area, or just through the Local Computer, Personal Certificate store.. but when attempting to open the Dashboard you see:
An error prevented the Dashboard from opening..
If you go to that link you get a TechNet wiki article about SBS 2011 Essentials, and it doesn’t answer this particular issue other than to give some guidance on general issues with certificates.
Thankfully the fix for this is simple.
Go to c:\Program Files\Windows Server\Bin and run the WSSPowerShell.exe file.
Then type in: Add-WssLocalMachineCert
This will reissue a Certificate to the local computer and also repair the registry settings tied to that certificate.
if you are interested to know, you can see a lot of settings related to Essentials in the registry here:
The entries relating to the dashboard error above, can be found under IDENTITY.
In this case the LocalMachineCert value is that of the thumbprint of the certificate the Dashboard expects to be part of the local machine store in order for it to start.
If that cert is missing or damaged the Dashboard will fail.
Running the above PowerShell cmdlet will request a new certificate and update this registry key with the new thumbprint ID.
You can see the thumbprint value here is updated.
When attempting to open the Dashboard for the first time after this, you may see a warning about Addins that may have caused the problem. You can click on Continue here to get to the Dashboard.