When I go to SCCM monitoring and look in system status / component status I get many error in the SMS_STATE_SYSTEM component. Many per minute. Error in the re look like this:

SMS_STATE_SYSTEM:
Severity Type Site code Date / Time System Component Message ID Description
Error Milestone 205 7/16/2013 6:23:02 AM SC2012.galesburg205.org SMS_STATE_SYSTEM 6105 The State System message file processing processed one or more files that contained errors or invalid data. Review the statesys.log file for further details.
Error Milestone 205 7/16/2013 6:22:47 AM SC2012.galesburg205.org SMS_STATE_SYSTEM 6104 The State System message file processing could not process file 'NZG4NGUO.SMX' and moved it to the corrupt directory. Review the statesys.log file for further details.
Error Milestone 205 7/16/2013 6:22:47 AM SC2012.galesburg205.org SMS_STATE_SYSTEM 620 Microsoft SQL Server reported SQL message 50000, severity 16: *** Unknown SQL Error!    Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information.
Error Milestone 205 7/16/2013 6:22:32 AM SC2012.galesburg205.org SMS_STATE_SYSTEM 6105 The State System message file processing processed one or more files that contained errors or invalid data. Review the statesys.log file for further details.
Error Milestone 205 7/16/2013 6:22:17 AM SC2012.galesburg205.org SMS_STATE_SYSTEM 6104 The State System message file processing could not process file 'z67z8u8r.SMX' and moved it to the corrupt directory. Review the statesys.log file for further details.
Error Milestone 205 7/16/2013 6:22:17 AM SC2012.galesburg205.org SMS_STATE_SYSTEM 620 Microsoft SQL Server reported SQL message 50000, severity 16: *** Unknown SQL Error!    Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information.

Looking in STATESYS.LOG I see this:

STATESYS.LOG
CThreadMgr::ThreadTerminating - All threads have stopped running SMS_STATE_SYSTEM 7/16/2013 6:22:17 AM 5680 (0x1630)
State message processing processed invalid records or files in the last processing cycle. SMS_STATE_SYSTEM 7/16/2013 6:22:32 AM 4924 (0x133C)
STATMSG: ID=6105 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_STATE_SYSTEM" SYS=SC2012.galesburg205.org SITE=205 PID=6068 TID=4924 GMTDATE=Tue Jul 16 11:22:32.553 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_STATE_SYSTEM 7/16/2013 6:22:32 AM 4924 (0x133C)
Found new state messages to process, starting processing thread SMS_STATE_SYSTEM 7/16/2013 6:22:47 AM 4924 (0x133C)
Thread "State Message Processing Thread #0" id:5996 started SMS_STATE_SYSTEM 7/16/2013 6:22:47 AM 5996 (0x176C)
total chucks loaded (1) SMS_STATE_SYSTEM 7/16/2013 6:22:47 AM 5996 (0x176C)
*** *** Unknown SQL Error! SMS_STATE_SYSTEM 7/16/2013 6:22:47 AM 5996 (0x176C)
CMessageProcessor - Encountered a non-fatal SQL error while processing SMS_STATE_SYSTEM 7/16/2013 6:22:47 AM 5996 (0x176C)
CMessageProcessor - Non-fatal error while processing NZG4NGUO.SMX SMS_STATE_SYSTEM 7/16/2013 6:22:47 AM 5996 (0x176C)
STATMSG: ID=6104 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_STATE_SYSTEM" SYS=SC2012.galesburg205.org SITE=205 PID=6068 TID=5996 GMTDATE=Tue Jul 16 11:22:47.563 2013 ISTR0="NZG4NGUO.SMX" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_STATE_SYSTEM 7/16/2013 6:22:47 AM 5996 (0x176C)
Thread "State Message Processing Thread #0" id:5996 was unable to process file "C:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\process\NZG4NGUO.SMX", moving to corrupt directory. SMS_STATE_SYSTEM 7/16/2013 6:22:47 AM 5996 (0x176C)
total chucks loaded (0) SMS_STATE_SYSTEM 7/16/2013 6:22:47 AM 5996 (0x176C)
Thread "State Message Processing Thread #0" id:5996 terminated normally SMS_STATE_SYSTEM 7/16/2013 6:22:47 AM 5996 (0x176C)
CThreadMgr::ThreadTerminating - All threads have stopped running SMS_STATE_SYSTEM 7/16/2013 6:22:47 AM 5996 (0x176C)
State message processing processed invalid records or files in the last processing cycle. SMS_STATE_SYSTEM 7/16/2013 6:23:02 AM 4924 (0x133C)
STATMSG: ID=6105 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_STATE_SYSTEM" SYS=SC2012.galesburg205.org SITE=205 PID=6068 TID=4924 GMTDATE=Tue Jul 16 11:23:02.564 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_STATE_SYSTEM 7/16/2013 6:23:02 AM 4924 (0x133C)
Will sleep until task 'Policy Deployments Summary' is due in 39 seconds. SMS_STATE_SYSTEM 7/16/2013 6:24:02 AM 4924 (0x133C)
Main thread waiting for file change notification or timeout after 39 seconds. SMS_STATE_SYSTEM 7/16/2013 6:24:02 AM 4924 (0x133C)
Inbox notification triggered, pause for 10 seconds.... SMS_STATE_SYSTEM 7/16/2013 6:24:41 AM 4924 (0x133C)
Started task 'Policy Deployments Summary' SMS_STATE_SYSTEM 7/16/2013 6:24:51 AM 4924 (0x133C)
Started task 'Calculate EP Health State' SMS_STATE_SYSTEM 7/16/2013 6:25:06 AM 4924 (0x133C)
Task 'Policy Deployments Summary' completed successfully after running for 15 seconds, with status 0. SMS_STATE_SYSTEM 7/16/2013 6:25:06 AM 4924 (0x133C)
Task 'Calculate EP Health State' completed successfully after running for 15 seconds, with status 1. SMS_STATE_SYSTEM 7/16/2013 6:25:21 AM 4924 (0x133C)
Will sleep until task 'Save State Message Statistics' is due in 71 seconds. SMS_STATE_SYSTEM 7/16/2013 6:25:21 AM 4924 (0x133C)
Main thread waiting for file change notification or timeout after 71 seconds. SMS_STATE_SYSTEM 7/16/2013 6:25:21 AM 4924 (0x133C)
Inbox notification triggered, pause for 10 seconds.... SMS_STATE_SYSTEM 7/16/2013 6:26:32 AM 4924 (0x133C)
Started task 'Save State Message Statistics' SMS_STATE_SYSTEM 7/16/2013 6:26:42 AM 4924 (0x133C)
Task 'Save State Message Statistics' completed successfully after running for 15 seconds, with status 0. SMS_STATE_SYSTEM 7/16/2013 6:26:57 AM 4924 (0x133C)
Will sleep until task 'Re-target restore operation to Infected clients' is due in 283 seconds. SMS_STATE_SYSTEM 7/16/2013 6:26:57 AM 4924 (0x133C)
Main thread waiting for file change notification or timeout after 283 seconds. SMS_STATE_SYSTEM 7/16/2013 6:26:57 AM 4924 (0x133C)
Inbox notification triggered, pause for 10 seconds.... SMS_STATE_SYSTEM 7/16/2013 6:31:40 AM 4924 (0x133C)

Looking inbox\auth\statesys.box\corrupt folder I see many files which contain stuff like this:

<?xml version="1.0" encoding="UTF-16"?>
<Report><ReportHeader><Identification><Machine><ClientInstalled>1</ClientInstalled><ClientType>1</ClientType><ClientID>GUID:A2F3264E-6E3D-4A40-B74E-37AFCA8A0E29</ClientID><ClientVersion>5.00.7804.1000</ClientVersion><NetBIOSName>000E137777DO002</NetBIOSName><CodePage>437</CodePage><SystemDefaultLCID>1033</SystemDefaultLCID><Priority>5</Priority></Machine></Identification><ReportDetails><ReportContent>State Message Data</ReportContent><ReportType>Full</ReportType><Date>20130716112234.644000+000</Date><Version>1.0</Version><Format>1.0</Format></ReportDetails></ReportHeader><ReportBody><StateMessage MessageTime="20130716112214.000000+000" SerialNumber="431"><Topic ID="ghs/jsmith_Auto" Type="1600" IDType="0" User="" UserSID=""/><State ID="2" Criticality="0"/><UserParameters Flags="0" Count="3"><Param>GHS\jsmith</Param><Param>Auto</Param><Param>0</Param></UserParameters></StateMessage></ReportBody></Report>

I don't know how to fix these errors. I have not moved the database. We have been trying to add OS and APP deployment to our server lately. SCCM seems to throw an error on all clients not just a few. Where should Look next?

What version of ConfigMgr (SP and CU level) are you using? What version of SQL? Are the remaining COnfigMgr components working fine?

SCCM 2012 sp1 cu2

SQL 2012 sp1

No recent messages show errors on the other components.

I don't know if this is relevant or not but in examining the disk I have found that the SQL ReportServer_log.LDF is 60 gig!

There is an issue with recent .net patch.  kb2840628

Saw the same in my logs.  Use workaround or uninstall.

http://blogs.technet.com/b/configurationmgr/archive/2013/07/17/issues-reported-with-ms13-052-kb2840628-and-configuration-manager.aspx