Configuration Manager console won’t connect after an upgrade

I recently upgraded my Configuration Manager lab and as is the norm nowadays I ran the prereq checker – no isssues, then kicked off the install and went about my evening as the upgrade process in Configuration Manager is slick as you like. When I came back to it however, the console wouldn’t connect when I started it. I did some initial checking and the upgrade seemed to have ran through OK, the services were running and CMUpdate.log looked pretty good on the whole.

Tip – If you find yourself here, make a check with WBEMTEST to see if you can connect to the WMI namespace for Configuration Manager.

Simply run WBEMTEST from a command line etc

image

Now hit connect and try to connect to your site at ROOT\SMS\site_<site code>

image

More info here – https://docs.microsoft.com/en-us/sccm/develop/core/understand/introduction-to-wbemtest

In my case, this wouldn’t connect it simply went to not responding. I happen to mention this to a colleague and he said he had seen the same on the last two upgrades and pointed me to the logical next step which was checking WMI was running – it wasn’t.

image

The upgrade had issues stopping WMI by the looks of it.

Now you have two choices here, force the services to stop or kill the server and restart the OS. I would recommend trying the nice option first as killing server can be a little dicey at this point and can lead to BSOD or worse.

So try this first.

sc queryex winmgmt

Now take the PID (Process ID) and try and force a kill on it.

taskkill /PID <PID> /F

image

At this stage you can cross fingers and wait to see if it works. I was due to travel so I decided to leave it running and checked back a day later but it was still stopping. I did however notice that I could then make a connection with WBEMTEST but the service was still stuck. So I decided to try and fire up the console and it did work. Although the command prompt process shown above was still running, once I refreshed the services windows I could see the service had returned to a running state.

Job done.

/Peter

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.