Enjoy Sharing

Cannot View Software Update Compliance Status

Here’s one problem I’ve been wrestling with for a bit and I think this is good information to share.

You view under the Update Repository of the SCCM console and find under any update classes that the number of computers requires/installed/not required are all showing up as 0. Viewing the Software Update compliance report for a specific computer shows no information. Further investigation reveals that all the clients ran the scan successfully and reported back to the MP. Now, what could be the problem? That led me to investigate further on the server side which brought me to this error in the statmgr.log.

Thread "State Message Processing Thread #0" id:12708 was unable to process file "D:Program FilesMicrosoft Configuration Managerinboxesauthstatesys.boxprocessNEJWADWJ.SMX", moving to corrupt directory.                SMS_STATE_SYSTEM     1/1/1601 12:00:00 AM    12708 (0x31A4)

SQL MESSAGE: spProcessStateReport – Error: Message processing encountered a SQL error 9802 at record 1 for TopicType 501: "The locale identifier (LCID) 17417 is not supported by SQL Server.", Line 0 in procedure ""                SMS_STATE_SYSTEM     1/1/1601 12:00:00 AM    12708 (0x31A4)

Browsing to the path above showed me thousands of files in the corrupt folder. Now that’s why I’m not getting any compliance scan results showing up on the console. The solution I am gonna take may seem outrageous to folks in different parts of the world. The way to do it is to change the Regional Settings on the server. Here are the steps taken:-

  1. Go to Regional and Language Options in control panel and set everything to US-English.
  2. Click in the Administrative tab.
  3. Click Copy settings to Reserved Accounts…
  4. Selected Check box System account (Local System, Local Service, and network service)
  5. Restart the Database Machine as well as the SCCM server.

Apparently, if you are using other Regional Settings, SQL has a problem writing in that format. Many thanks to Winds and Chris that helped me look into this together though this is extremely rare. Who knew something so small made something seem so big.




2 responses

  1. DK

    I hit with this issue also, but previously I do receive this statsys.log message, but the client still able to obtain update, but right now, the client totally can’t.
    So I had try the method as mention, with change all the Regional Setting to Eng(US).
    Does my client PC also need to be the same?

    My environment are SCCM 2007 R2 SP1 with windows 2008 Server 32bits and remote SQL 2005 SP2 with Windows 2008 64bits.
    Can advice what other thing I need to look into?

    Kindly advice, many thanks!

    April 11, 2011 at 5:58 pm

    • Is your server doing the sync correctly?

      April 14, 2011 at 11:47 am

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