SMS_PROVIDERS in Configuration Manager Service Manager

[Kevin79]

The service SMS_PRODIVERS in Configuration Manager Service Manager is showing as unknown. When I try to query the service I get "Error communicating with component". I upgraded from 2012 R2 SP1 to Configuration Manager Current Branch. How do I fix this? Will it cause any issues?

[ZeZe]

Give it some time. ConfigMgr is a little bit slow sometimes!

[Kevin79]

It still says the same thing.

[ZeZe]

Check the monitoring for more troubleshooting. Is the firewall ON in the server that is running that componente?

[Kevin79]

The firewall is not on. In monitoring, it says the availability is Unknown.

[ZeZe]

Ok, but did you check the messages?

 

Select the componente, right click, show messages, show all messages, select date and time 1 day ago... What does it say?!

 

opssy... wrong topic! but still works for you !

[Kevin79]

There isn't anything when I click Show Messages. Here are some screenshots. Whenever I try to query the status, CompMgrProv.log gets updated.

[ZeZe]

hmm... strange!

 

https://technet.microsoft.com/en-us/library/hh427336.aspx#BKMK_ManageSMSprovider

 

If there was a problem during the installation you can always remove and re-install or you could also install the componente in another server (for what I have been reading so far, you can have multiple SMS providers). But I would consider to test this before you run this procedure on your production environment.

[Kevin79]

I tried this and the result it the same.

[binarymime]

According to this guy Microsoft told him that this is now done by design. So apparently its nothing to wory about. If its any consolation i see the same thing in my environemnt as well.

 

http://www.networksteve.com/enterprise/topic.php/Upgraded_from_SCCM_2012_R2_to_SP1,_%22SMS_Providers%22_component_sho/?TopicId=103143&Posts=4

​

I think the thing that puzzles me though is that the component log is supposed to be here:

 

.\%ConfigMgrInstallDirectory%\logs\certificate.log

 

I cant find the log anywhere....which raises the question of whether or not Microsoft is entirely correct on this. Sounds like a misbehaving component to me

 

Thanks