I am in the process of migrating from SCCM 2007 to 2012 R2.  My site was up and running great.  I installed SP1 and now my SMS_Providers shows type and availability as unknown for Component Staus.  In Configuration Manager Service Manager when I query the component I get "error communicating with component."  

I have reinstalled the Provider with no success.  I have tried to move the provider to my SQL box.

I am not seeing any errors in sitecomp.log

In my SMSProv.log I see the below errors

I am not sure how to proceed and any help would be great.

Site Component Manager failed to reinstall this component on this site system.    Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the reinstallation in 60 minutes. To force Site Component Manager to immediately retry the reinstallation, stop and restart Site Component Manager using the Configuration Manager Service Manager.
Site Component Manager could not stop the winmgmt service on site system "\\SCCM12..domain.com".    Possible cause: Site Component Manager does not have sufficient access rights to administer the site system.  Solution: Verify that the Site System Connection accounts are properly configured to allow the site to administer the site system.    If this problem persists, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information.
Site Component Manager is reinstalling this component on this site system.
Component Status Summarizer set the status of component "SMS_PROVIDERS" running on computer "SCCM12..domain.com" to Warning.    Possible cause: The component is experiencing a problem.  Solution: Diagnose and fix the problem by:  1. Examine the status messages that the component reports.  2. Correcting the problem.  3. Instructing Component Status Summarizer to reset the counts of Error, Warning, and/or Informational status messages reported by the component. To reset the counts, right-click Reset Counts on the component in the Component Status summary in the Configuration Manager Console. When the counts are reset, Component Status Summarizer will change the status of the component to OK. This might take some time if site "EHC" is a child site.  4. Deleting any unwanted status messages from the site database, if necessary.  5. Monitor the component occasionally to verify the problem does not reoccur.    Possible cause: The component is OK and you were unnecessarily alerted because the Component Status Thresholds are set too low for the component.  Solution: Increase the Component Status Thresholds for the component using the Thresholds tab of the Component Status Summarizer Properties dialog box in the Configuration Manager Console.    Possible cause: The component is "flooding" the status system by rapidly reporting the same message repeatedly.  Solution: Diagnose and control the flood of status messages by:  1. Verifying that the component is actually flooding the status system. View the status messages reported by the component, and verify that the same message is continually reported every several minutes or seconds.  2. Noting the Message ID of the flooded status message.  3. Creating a Status Filter Rule for site "EHC" that instructs Status Manager to discard the flooded status message when component "SMS_PROVIDERS" on computer "SCCM12..domain.com" reports it.   4. Verifying that your sites' databases were not filled up by the flooded status message.  Delete any
Component Status Summarizer detected that component "SMS_PROVIDERS", running on computer "SCCM12..domain.com", has reported 1 or more Error status messages during the Component Status Threshold Period.    Possible cause: The count equals or exceeds the Component Status Warning Threshold (1 status messages) for Error status messages for the component.  Solution: If the component's status is not already set to Warning, Component Status Summarizer will set the component's status to Warning in the Component Status summary in the Configuration Manager Console.
Site Component Manager is reinstalling this component on this site system.
Site Component Manager could not stop the winmgmt service on site system "\\SCCM12..domain.com".    Possible cause: Site Component Manager does not have sufficient access rights to administer the site system.  Solution: Verify that the Site System Connection accounts are properly configured to allow the site to administer the site system.    If this problem persists, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information.
Site Component Manager failed to reinstall this component on this site system.    Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the reinstallation in 60 minutes. To force Site Component Manager to immediately retry the reinstallation, stop and restart Site Component Manager using the Configuration Manager Service Manager.
Site Component Manager is reinstalling this component on this site system.
Site Component Manager could not stop the winmgmt service on site system "\\SCCM12..domain.com".    Possible cause: Site Component Manager does not have sufficient access rights to administer the site system.  Solution: Verify that the Site System Connection accounts are properly configured to allow the site to administer the site system.    If this problem persists, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information.
Site Component Manager failed to reinstall this component on this site system.    Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the reinstallation in 60 minutes. To force Site Component Manager to immediately retry the reinstallation, stop and restart Site Component Manager using the Configuration Manager Service Manager.

Did you see the the following in the log: "Site Component Manager could not stop the winmgmt service on site system "\\SCCM12..domain.com". " This is fatal -- there's not much setup can do if it can't stop a dependent service.

Have you tried stopping the service manually on that system?

Do you happen to have TrandMicro Anti-virus installed on that system?

Yes and does not make a difference.  

I do not have TrendMicro 

The only error I see in configMgrSetup.log  

ERROR: Setup has detected that a SMS Provider is installed on the specified server. We will reinstall the SMS Provider on sccm12.domain.com.

INFO: Added site server machine account to security group SMS Admins on SCCM12.domain.com. Configuration Manager Setup 7/21/2015 12:07:10 PM 2596 (0x0A24)
INFO: Checking Windows Cluster. Configuration Manager Setup 7/21/2015 12:07:10 PM 2596 (0x0A24)
CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e Configuration Manager Setup 7/21/2015 12:07:10 PM 2596 (0x0A24)
INFO: WMI namespace root\MSCluster not exists on sccm12.domain.com. Configuration Manager Setup 7/21/2015 12:07:10 PM 2596 (0x0A24)

But I am not in Cluster mode so I am thinking I can ignore this error

In CompMPProv.log after reinstalling the provider I am getting

### CompMgrProv [07-21-15 10:06:32] *** ERROR *** CCompMgrProv::QueryService: serviceManager.QueryServiceStatus failed. Return code: 0x00000001
### CompMgrProv [07-21-15 10:06:36] *** ERROR *** CCompMgrProv::QueryService: serviceManager.QueryServiceStatus failed. Return code: 0x00000001
### CompMgrProv [07-21-15 10:14:49] **** **** **** CCompMgrProv::CCompMgrProv
### CompMgrProv [07-21-15 10:15:08] *** ERROR *** CCompMgrProv::QueryService: serviceManager.QueryServiceStatus failed. Return code: 0x00000001
### CompMgrProv [07-21-15 10:16:33] *** ERROR *** CCompMgrProv::QueryService: serviceManager.QueryServiceStatus failed. Return code: 0x00000001
### CompMgrProv [07-21-15 10:20:30] **** **** **** CCompMgrProv::CCompMgrProv
### CompMgrProv [07-21-15 10:20:30] *** ERROR *** CCompMgrProv::QueryService: serviceManager.QueryServiceStatus failed. Return code: 0x00000001
### CompMgrProv [07-21-15 11:15:10] **** **** **** CCompMgrProv::CCompMgrProv
### CompMgrProv [07-21-15 11:15:15] *** ERROR *** CCompMgrProv::GetServiceControlsAccepted: serviceManager.QueryServiceStatus failed. Return code: 0x00000001
### CompMgrProv [07-21-15 11:15:15] *** ERROR *** CCompMgrProv::GetServiceControlsAccepted: serviceManager.QueryServiceStatus failed. Return code: 0x00000001
### CompMgrProv [07-21-15 11:15:15] *** ERROR *** CCompMgrProv::GetServiceControlsAccepted: serviceManager.QueryServiceStatus failed. Return code: 0x00000001
### CompMgrProv [07-21-15 11:15:29] *** ERROR *** CCompMgrProv::QueryService: serviceManager.QueryServiceStatus failed. Return code: 0x00000001
### CompMgrProv [07-21-15 11:15:45] *** ERROR *** CCompMgrProv::QueryService: serviceManager.QueryServiceStatus failed. Return code: 0x00000001
### CompMgrProv [07-21-15 11:17:15] **** **** **** CCompMgrProv::CCompMgrProv
### CompMgrProv [07-21-15 11:17:15] *** ERROR *** CCompMgrProv::GetServiceControlsAccepted: serviceManager.QueryServiceStatus failed. Return code: 0x00000001
### CompMgrProv [07-21-15 11:17:15] *** ERROR *** CCompMgrProv::GetServiceControlsAccepted: serviceManager.QueryServiceStatus failed. Return code: 0x00000001
### CompMgrProv [07-21-15 11:17:15] *** ERROR *** CCompMgrProv::GetServiceControlsAccepted: serviceManager.QueryServiceStatus failed. Return code: 0x00000001
### CompMgrProv [07-21-15 11:17:23] *** ERROR *** CCompMgrProv::QueryService: serviceManager.QueryServiceStatus failed. Return code: 0x00000001
### CompMgrProv [07-21-15 11:48:29] **** **** **** CCompMgrProv::CCompMgrProv
### CompMgrProv [07-21-15 11:48:30] *** ERROR *** CCompMgrProv::GetServiceControlsAccepted: serviceManager.QueryServiceStatus failed. Return code: 0x00000001
### CompMgrProv [07-21-15 11:48:30] *** ERROR *** CCompMgrProv::GetServiceControlsAccepted: serviceManager.QueryServiceStatus failed. Return code: 0x00000001
### CompMgrProv [07-21-15 11:48:30] *** ERROR *** CCompMgrProv::GetServiceControlsAccepted: serviceManager.QueryServiceStatus failed. Return code: 0x00000001

"Yes and does not make a difference.  "

What does not make a difference? Did you manually stop the service and then restart the Component manager to kick off the install again?

sorry, Yes I have tried to stop the service, which I am able to so is SCCM server.  But it makes no difference.  

I am just starting over

So after you stopped the service on SCCM12.domain.com, did you restart the component manager also?

And watch the log?

Yes I would restart the component manager and I would see the errors above in my original comment.  No other errors except in CompMPProv.log which are also above.

Does the site server's account have local admin permissions on the system?

Have you reviewed the event viewer for any related e

Yes the server is admin.  I have looked at event viewer and there is nothing related to the error that I can see.  I just did a reinstall of SCCM 2012 and applied SP1.  I am getting the same thing.

Site Component Manager successfully reinstalled this component on this site system.
Site Component Manager is reinstalling this component on this site system.
Site Component Manager could not stop the winmgmt service on site system "\\SCCM12.domain.COM". The operating system reported error 1115: A system shutdown is in progress.     Possible cause: Site Component Manager does not have sufficient access rights to administer the site system.  Solution: Verify that the Site System Connection accounts are properly configured to allow the site to administer the site system.    If this problem persists, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information.
Site Component Manager failed to reinstall this component on this site system.    Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the reinstallation in 60 minutes. To force Site Component Manager to immediately retry the reinstallation, stop and restart Site Component Manager using the Configuration Manager Service Manager.
Site Component Manager is reinstalling this component on this site system.
Site Component Manager is reinstalling this component on this site system.
Site Component Manager detected that this component should be reinstalled on this site system. Site Component Manager will attempt to install the component every 60 minutes until the installation succeeds.

• Edited by freebird_ 11 hours 6 minutes ago

Well, this is a different issue: "A system shutdown is in progress"

The date on the errors is from yesterday 07/21/2012.  The last message says that it installed successfully.  The SMS_Providers is still showing as unknown.  When I use "CFG MGR Service Manager" the component is saying error "communicating with component"

SQL is on another server and SCCM server is in the local admin group on the server.

Yes the server is admin.  I have looked at event viewer and there is nothing related to the error that I can see.  I just did a reinstall of SCCM 2012 and applied SP1.  I am getting the same thing.

Site Component Manager successfully reinstalled this component on this site system.
Site Component Manager is reinstalling this component on this site system.
Site Component Manager could not stop the winmgmt service on site system "\\SCCM12.domain.COM". The operating system reported error 1115: A system shutdown is in progress.     Possible cause: Site Component Manager does not have sufficient access rights to administer the site system.  Solution: Verify that the Site System Connection accounts are properly configured to allow the site to administer the site system.    If this problem persists, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information.
Site Component Manager failed to reinstall this component on this site system.    Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the reinstallation in 60 minutes. To force Site Component Manager to immediately retry the reinstallation, stop and restart Site Component Manager using the Configuration Manager Service Manager.
Site Component Manager is reinstalling this component on this site system.
Site Component Manager is reinstalling this component on this site system.
Site Component Manager detected that this component should be reinstalled on this site system. Site Component Manager will attempt to install the component every 60 minutes until the installation succeeds.

• Edited by freebird_ Wednesday, July 22, 2015 8:43 PM

It's time to open a case with Microsoft support on this as it's often difficult to piece all the information together and troubleshoot in forum thread.

SMS_SITE_SQL_back...was in the same unknown state. I did some more diggin and found my SPN's were not created. I created two SPN for FQDN and NETBIOS and running setspn -L <domain\account> shows them there. Both components still show unknown.  

This is my exact problem "the cause" except my server and sql are 2012.  

https://support.microsoft.com/en-us/kb/957879

"

CAUSE

When SQL Server is not installed on the site server, the computer name of the site server is appended to the name of the SQL Server backup service. Therefore, the actual service name is "SMS_SITE_SQL_BACKUP_<var class="sbody-var" style="box-sizing:border-box;font-family:'Segoe UI', 'Segoe UI Web', 'Segoe UI Symbol', 'Helvetica Neue', 'BBAlpha Sans', 'S60 Sans', Arial, sans-serif;font-size:15px;line-height:18.1818180084229px;">The-name-of-the-Site-Server</var>" instead of "SMS_SITE_SQL_BACKUP."

Hi,

This is an expected issue.

This SMS_Providers is a newly added component of sitecomp in R2SP1/SP2 and its not a NT service, so its status is unknown, its hosted by WMI service host as other WMI Providers, this is servicing as a channel to update local & remote providers.

I ended up opening a case with Microsoft. Microsoft does not why the provider is showing unknown.  On Microsoft's advise I am reinstalling SCCM 2012