I set up a windows 7 BDP and it is accepting and deploying packages but the Status remains Critical, Free space is 0% and the State System status shows:
Severity,Type,Site code,Date / Time,System,Message ID,Component,Description,Thread ID,Process ID
Error,Milestone,BOS,6/3/2015 11:13:41 AM,SCCM01,6104,SMS_STATE_SYSTEM,The SMS State System message file processing could not process file '8HU3WZVN.SMX' and moved it to the corrupt directory. Review the statesys.log file for further details.,45532,60264
The statesys.log shows:
SQL MESSAGE: spProcessStateReport - Error: Message processing encountered a SQL error 232 at record 1 for TopicType 900: "Arithmetic overflow error for type int, value = 2441894912.000000.", Line 0 in procedure "" SMS_STATE_SYSTEM 6/3/2015
11:13:41 AM 45532 (0xB1DC)
SQL MESSAGE: spProcessStateReport - Error: Message processing encountered a SQL error 3621 at record 1 for TopicType 900: "The statement has been terminated.", Line 0 in procedure "" SMS_STATE_SYSTEM 6/3/2015 11:13:41 AM 45532
(0xB1DC)
CMessageProcessor - Non-fatal error while processing 8HU3WZVN.SMX SMS_STATE_SYSTEM 6/3/2015 11:13:41 AM 45532 (0xB1DC)
STATMSG: ID=6104 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_STATE_SYSTEM" SYS=SCCM01 SITE=BOS PID=60264 TID=45532 GMTDATE=Wed Jun 03 15:13:41.467 2015 ISTR0="8HU3WZVN.SMX" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_STATE_SYSTEM 6/3/2015 11:13:41 AM 45532 (0xB1DC)
Thread "State Message Processing Thread #0" id:45532 was unable to process file "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\statesys.box\process\8HU3WZVN.SMX", moving to corrupt directory. SMS_STATE_SYSTEM 6/3/2015
11:13:41 AM 45532 (0xB1DC)
The contents of the file are :
version="1.0" encoding="UTF-16"?>
<Report><ReportHeader><Identification><Machine><ClientInstalled>1</ClientInstalled><ClientType>1</ClientType><ClientID>GUID:6D8240BF-73C0-4EB0-A627-269B7D0E26E1</ClientID><ClientVersion>4.00.6487.2157</ClientVersion><NetBIOSName>04TECHDATA</NetBIOSName><CodePage>437</CodePage><SystemDefaultLCID>1033</SystemDefaultLCID><PublicKey
KeyType="Self Signed">0602000000240000525341310004000001000100553278B667E33E8F9252265EE4DE9255CA8218B884F0B6281DDFA56A2DFB851566E5EDD23CE3813D1DDEBAAB58EBEC00A6ECF40288D776BBB5252D358A67FCD7BCB56DCDD6E3CAD12CA02C1760695DDF817BD8C7C605C66E4589EBE627A99C3ED11A93A95120B960BCEC5C479A57F531B24C76198EEFEB3AF5DB48EEAFCF389A</PublicKey></Machine></Identification><ReportDetails><ReportContent>State
Message Data</ReportContent><ReportType>Full</ReportType><Date>20150603151332.255000+000</Date><Version>1.0</Version><Format>1.0</Format></ReportDetails></ReportHeader><ReportBody><StateMessage
MessageTime="20150603151331.927000+000" SerialNumber="12249"><Topic ID="Available Disk Space" Type="900" IDType="0"/><State ID="1" Criticality="0"/><StateDetails Type="1"><![CDATA[<BDPStatus><Availability>0</Availability><DiskSpace><Drive
Id="C" Free="358168" Total="476937"/><Drive Id="E" Free="1793652" Total="1907726"/></DiskSpace></BDPStatus>]]></StateDetails><UserParameters Flags="0" Count="0"/></StateMessage></ReportBody></Report>
Can anyone explain to me why this message is getting rejected as corrupt? It doesn't look large enough to be a overflow error but it obviously is processing the data incorrectly.