none
Component Status not updating since upgrade from SCCM2012 SP1 CU3 to SCCM2012 R2 RRS feed

  • Question

  • Since upgrading to SCCM2012 R2 three days ago, in the Configuration Manager console when we go to Monitoring > System Status > Component Status and view the status messages for any component, there are no entries since the time of our upgrade.  All components are this way.

    I've checked the logs and information is flowing through them and everything else seems to be running smoothly, but there are no updates to items in Component Status.  There was only one warning in the R2 prereq checker, the ConfigMgrPrereq.log shows:

    <11-08-2013 15:33:30> ERROR: Site server does not have create child permission on AD 'System Management'
    <11-08-2013 15:33:30> WARN: Site server does not have delete child permission on AD 'System Management'
    <11-08-2013 15:33:30> [primary site server];    Verify site server permissions to publish to Active Directory.;    Warning;    The site server might be unable to publish to Active Directory. The computer account for the site server must have Full Control permissions to the System Management container in its Active Directory domain. You can ignore this warning if you have manually verified these permissions. For more information about your options to configure required permissions, see http://go.microsoft.com/fwlink/p/?LinkId=233190.

    I have confirmed via ADUC and ADSIEdit that the primary site server computer account does have full control over the System Management container.

    We are running a single site server with separately hosted site database server and several remote distribution point site systems.  Any help would be greatly appreciated.



    • Edited by Chris H DCS Tuesday, November 12, 2013 5:39 AM
    Tuesday, November 12, 2013 5:34 AM

Answers

  • Problem solved!

    I was looking in the statmgr.log file and spotted an error about a bad SQL transaction.  Some searching on this lead me to this Microsoft KB article: http://support.microsoft.com/KB/884123.  Even though it is for SMS2003 it lead me to check the \inboxes\statmgr.box\retry\ folder and sure enough there were ~5100 .sql files waiting.  As per the instructions in the document, I stopped the SMS_EXECUTIVE service, deleted the oldest .sql file and then restarted the service.  The file count in the \Retry\ folder is dropping and status messages are flowing.  I now just have to wait for the 6 days of status messages to process.

    Thanks everyone for your assistance :)

    • Marked as answer by Chris H DCS Thursday, November 14, 2013 2:22 AM
    Thursday, November 14, 2013 2:22 AM

All replies

  • Can you try this :-

    Remove the site server account from System Management container. Add it back and provide the appropriate permissions as you had provided earlier. Reboot the SCCM server and check if this issue occurs again.


    Prajwal Desai

    http://prajwaldesai.com

    http://prajwaldesai.com/support

    http://prajwaldesai.com/forum

    Tuesday, November 12, 2013 6:36 AM
  • The AD publishing issue has nothing to do with missing component status. What does hman.log and sitecomp.log tell? What error code do you get when the server tries to publish to AD?
    Have you already tried running the 'all status messages' status message query? Does it return anything?

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, November 12, 2013 1:59 PM
    Moderator
  • Can you try this :-

    Remove the site server account from System Management container. Add it back and provide the appropriate permissions as you had provided earlier. Reboot the SCCM server and check if this issue occurs again.


    Prajwal Desai

    The site server account had permissions to the System Management container via a security group, I have added explicit full control access for the account and restarted the Primary Site Server, no change.

    Wednesday, November 13, 2013 1:23 AM
  • The AD publishing issue has nothing to do with missing component status. What does hman.log and sitecomp.log tell? What error code do you get when the server tries to publish to AD?
    Have you already tried running the 'all status messages' status message query? Does it return anything?

    Torsten Meringer

    I ran the 'All Status Message' query selecting the last week as the time period, it does not return any messages since the the R2 upgrade.

    The log files showed no error messages, below is a sample from the end of each file.

    hman.log:

    [hman.log removed]

    sitecomp.log

    [sitecomp.log removed]
    • Edited by Chris H DCS Monday, November 17, 2014 12:27 AM remove log files
    Wednesday, November 13, 2013 1:32 AM
  • Problem solved!

    I was looking in the statmgr.log file and spotted an error about a bad SQL transaction.  Some searching on this lead me to this Microsoft KB article: http://support.microsoft.com/KB/884123.  Even though it is for SMS2003 it lead me to check the \inboxes\statmgr.box\retry\ folder and sure enough there were ~5100 .sql files waiting.  As per the instructions in the document, I stopped the SMS_EXECUTIVE service, deleted the oldest .sql file and then restarted the service.  The file count in the \Retry\ folder is dropping and status messages are flowing.  I now just have to wait for the 6 days of status messages to process.

    Thanks everyone for your assistance :)

    • Marked as answer by Chris H DCS Thursday, November 14, 2013 2:22 AM
    Thursday, November 14, 2013 2:22 AM
  • Same problem; fresh install of SCCM 2012 R2 on Win2012R2, status messages stopped updating during/after a migration job from the old 2007-system. Resolved by removing oldest .sql-file in \inboxes\statmgr.box\retry as per the post above. 17 000 sql-files are now being processed at a rate of a couple per second. 

    Thanks, Chris H DCS!

    Thursday, April 24, 2014 12:52 PM
  • Also want to say thanks. Exact same problem as you after upgrading from 2012 SP1 CU3 to 2012 R2 CU1, but resolved it by following the same steps.

    -Russel

    Tuesday, August 5, 2014 4:14 PM
  • Just wanted to say I had this happen a few days ago--no entries being made to any of the component staus logs. I had not changed anything--not that I am aware of at least, the logs just stopped getting new entries. The fix of stopping SMS Exec service, deleting the oldest .sql file, and restarting the service worked for me too. My guess is that oldest .sql file was corrupted somehow.

    Ben JohnsonWY

    Monday, March 16, 2015 4:43 PM
  • Did you find a resolution? I tried the SMS 2003 article regarding deleting files in the inboxes. This worked for an hour or so, then logging stopped again
    Monday, April 27, 2015 12:43 AM
  • Problem solved!

    I was looking in the statmgr.log file and spotted an error about a bad SQL transaction.  Some searching on this lead me to this Microsoft KB article: http://support.microsoft.com/KB/884123.  Even though it is for SMS2003 it lead me to check the \inboxes\statmgr.box\retry\ folder and sure enough there were ~5100 .sql files waiting.  As per the instructions in the document, I stopped the SMS_EXECUTIVE service, deleted the oldest .sql file and then restarted the service.  The file count in the \Retry\ folder is dropping and status messages are flowing.  I now just have to wait for the 6 days of status messages to process.

    Thanks everyone for your assistance :)

    Works for me. Thanks!!!
    Tuesday, July 19, 2016 3:38 PM
  • This solution solved my problem too. Same scenario but after upgrading to 1606 from 1602.
    Saturday, August 13, 2016 1:34 PM
  • Thanks for this Chris! Had the same problem after moving the CM databases to another SQL server.
    Friday, December 23, 2016 5:45 PM
  • Had the same problem. This solution solved my problem too. Same scenario but after upgrading to 1610 from 1606
    Monday, February 6, 2017 1:38 PM