When you have hosting site server role on the Windows 2008 server you need to make sure that you have followed the following article http://technet.microsoft.com/en-us/library/cc431377.aspx. In some cases had found a issue when the Site System was Windows 2008 64 bit .The SMS_STATE_SYSTEM Will show you errors with 6104 and 6105 Status ID
When you check the statesys.log you will have the following
Statesys.log========Found new state messages to process, starting processing thread SMS_STATE_SYSTEM 08-12-2008 12:57:44 3300 (0x0CE4)Thread "State Message Processing Thread #0" id:11108 started SMS_STATE_SYSTEM 08-12-2008 12:57:44 11108 (0x2B64)SQL MESSAGE: spProcessStateReport - Error: Message processing encountered a SQL error 9802 at record 1 for TopicType 501: "The locale identifier (LCID) 16393 is not supported by SQL Server.", Line 0 in procedure "" SMS_STATE_SYSTEM 08-12-2008 12:57:44 11108 (0x2B64)CMessageProcessor - Non-fatal error while processing K460EB66.SMX SMS_STATE_SYSTEM 08-12-2008 12:57:44 11108 (0x2B64)STATMSG: ID=6104 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_STATE_SYSTEM" SYS=NDA-HCLC-SCCM01 SITE=N01 PID=6716 TID=11108 GMTDATE=Mon Dec 08 07:27:44.729 2008 ISTR0="K460EB66.SMX" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_STATE_SYSTEM 08-12-2008 12:57:44 11108 (0x2B64)Thread "State Message Processing Thread #0" id:11108 was unable to process file "D:\Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\statesys.box\process\K460EB66.SMX", moving to corrupt directory. SMS_STATE_SYSTEM 08-12-2008 12:57:44 11108 (0x2B64)SQL MESSAGE: spProcessStateReport - Error: Message processing encountered a SQL error 9802 at record 1 for TopicType 501: "The locale identifier (LCID) 16393 is not supported by SQL Server.", Line 0 in procedure "" SMS_STATE_SYSTEM 08-12-2008 12:57:44 11108 (0x2B64)===============Also you can see that there are lot of SMX which are corrupted in the inboxes\auth\statesys.box\corruptThis is because of the locale issue. Do the following to resolve the issue.=>Go to Regional and Language Options and set everything was US-English=>Clicked on the Administrative TAB=>Clicked Copy to Reserved Accounts=>Selected Check box System account (Local System, Local Service, and network service)=>Restart the Database Machine as well as the SCCM serverOnce the same was done the SMX got rocessed . Also copying the corrupted SMX back to the incoming also got processed
Hope this infromation will be useful
Sudheesh Narayanaswamy | Support Engineer