Hey guys. After an unscheduled outage this morning I noticed SCCM didn't recover very well. We can't open the console, and we noticed the logfiles weren't updated with new information. We restarted both the primary site server and the DB server, and after a while (45min) we noticed the logfiles were updated with new information. However, the smsprov.log file wasn't updated, and we still can't open the console. I went through various check (dcom, wmimgmt, wbemtest etc.) and all the results are OK. I performed a site reset, but we still have the same results. The smsprov.log file isn't updated and we can't open the console. I ran wmidiag and it found a couple of errors, so I mofcomped smsprov.mof and it solved the errors, but I still have the same issue - can't open console, smsprov.log not being updated.

Most threads on the web regarding this problem are solved after a reboot, but that didn't work for me. Any ideas how I can solve this? Thanks!

By the way, we run SCCM 2012 SP2 on Server 2012 R2.

Hi,

Can you connect to SCCM database without a problem?(From Microsoft SQL Server Management S

Hi Joyce, I can connect to the database from SQL mgmt studio. I can browse the tables, I can perform a simple query (select top 1000 rows) - it seems to work fine.

This morning I decided to install the SMS provider role on another server using site maintenance. After I installed the SMS provider onto a new server, and removed the SMS provider from the old server, I was able to open the console. The site status and component status was OK, except for a couple of errors from the sms_executive regarding registry entries on the old SMS provider which it couldn't find.

However, when I tried to reinstall the SMS provider onto the old server, the console didn't open, it kept hanging on "connecting to site". When I open the adminUIlog, it shows the following errors:

{
 Operation = "ExecQuery";
 ParameterInfo = "SELECT * FROM SMS_Site WHERE SiteCode = 'ABC'";
 ProviderName = "WinMgmt";
};
Error Code:
ProviderLoadFailure
\r\nSystem.Management.ManagementException\r\nProvider load failure \r\n   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__0.MoveNext()\r\nManagementException details:
instance of __ExtendedStatus

I got the same error message before I moved the SMS provider, so somewhere there's something wrong on the old sms provider server... but I can't really figure out what and why.

Is your SMS provider on your site server or another box? Do you just have one SMS provider or multiple? If only the one, try installing a 2ed SMS provider on a different box to see if your first provider is jacked. If you can get into the console after installing the 2ed provider, you know you probably need to rebuild the first provider. Hope that helps.

Firewall rules can also be at play, try dropping the firewall on the box that has the provider\s and see if that gets you anywhere.

-Tony

Hey Tony. This SCCM environment is quite simple, we have a primary site without secondary sites or CAS. We have a DB server, a primary site server, a separate server for the web app catalog, and we have a bunch of DP's on several locations. The SMS provider used to be on the primary site server, and it was the only SMS provider we had. Yesterday I installed the SMS provider on another server, and removed the SMS provider role from the primary site server, and I was able to open the console - everything was back to normal.

I tried to reinstall the SMS provider on the primary site server, but when the installation was finished, I wasn't able to open the console anymore. Removed the SMS provider, and it was working again. It seems to me that some sort of dependency for the SMS provider on the primary site server isn't working correctly, because the smsprov.log logfile on the primary site server is not updated with new information after we had the outage. No new information is added - and that's quite unusual for ConfigMgr logfiles ;) it seems to me the SMS provider isn't working correcty, or does not even start.

I can't entirely drop the firewall on the primary site server because this is managed by another team, but if firewall rules were at play, I would suspect the smsprov.log file to contain some sort of indication about this.

How does the site and component status looking under monitoring? Wondering if anything is showing critical there that we can look at that might help. Also, do you have to have an SMSProv crash log? Their might be something useful in it, if you have one. Also, a shot in the dark, maybe reboot the environment again after to reinstall the SMS provider on the site server.

I have not seem an instance yet when the log just does not update. I did some SMS provider work in my production environment not to long ago. We added a second provider which was not working, and it a firewall issue. That is why I suggested the firewall, unfortunately I can't say for certain if the log file logged any details or not when fire was blocking traffic. 

-Tony

After I've placed the SMS provider onto another server, the site and component status looks just fine. We only have a couple of errors from the SMS_AD_SYSTEM_DISCOVERY_AGENT - (AD System Discovery Agent reported errors for 1 objects). When the SMS provider wasn't running, I wasn't able to connect to the CM Service Manager and query the status for the components or check for errors. We did a couple of reboots during the whole SMS Provider installation/deinstallation proces, but it didn't make any difference.

And check the image below - this is on the server which was the former SMS provider. We installed and removed the SMS provider role several times, but as you can see, the logfile just doesn't get updated anymore. We had the crash on 7/29 11:15. It looks like there's some sort of issue with a dependency of the SMS provider, which is why the SMS provider isn't starting or something.

• Edited by Tom_Floor 17 hours 42 minutes ago

I think I am out of idea's at this point regarding why the SMS Provider won't reinstall or work on the orginal site server. My only thought now, kind of a shotgun approach would be to possibly reinstall the site server.  I have not had to do that before, so if you choose to do so I would do some research... Also, you might wait and see if any of the more experienced MVP's are able to weigh in. You might have to end up opening a case.

-Tony