I would have seen errors for the SMS_STATE_SYSTEM component by now, and I can see in statesys.log that state messages are being processed. Review the statesys.logfile for further details. (error code 6104)The SMS State System message file processing processed one or more filesthat contained errors or invalid data. Review the statesys.logfile for further details. (error code 6104)The SMS State System message file processing processed one or more filesthat contained errors or invalid data. you didn't answer one of my earlierquestions, are you seeing this a LOT or just on a few files?StevePost by rob-adog*** *** Unknown SQL Error! $$
http://blogs.technet.com/b/configurationmgr/archive/2013/07/17/issues-reported-with-ms13-052-kb2840628-and-configuration-manager.aspx Send PM 22nd July 2013,07:09 PM #12 rodtrent Join Date Jul 2008 Location USA Posts 8 Thank Post 0 Thanked 1 Time in 1 Post Rep Power 0 Brian Where should Look next? As I see there are 10 to 30 new smx files per day.I have checkedif the computername is inmany files, but this is not the case.The problem happens randomly on any The count of the inboxes\auth\statesys.box\corrupt in our environment with 16'000 agents are 3'600. https://social.technet.microsoft.com/Forums/systemcenter/en-US/e1293a68-b156-4b6e-87fa-5f8b7aa05f3e/smsstatesystem-status-messages-include-many-6104-and-6105-errors?forum=configmgrgeneral
CMessageProcessor - Non-fatal error while processing RW9ICC0T.SMX Thread "State Message Processing Thread #0" id:7764 was unable to process file "C:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\process\RW9ICC0T.SMX", moving to corrupt directory. Privacy statement © 2016 Microsoft. Here is a sample (names changed to protect the innocent):
Send PM 12th July 2013,04:29 PM #3 jleclerc Join Date Jul 2013 Posts 5 Thank Post 2 Thanked 2 Times in 2 Posts Rep Power 0 I was in the SCCM seems to throw an error on all clients not just a few. I checked my old notes on this in case there was something I forgot, and I have pencilled in "dont have time to check right now but I got these errors http://www.networksteve.com/enterprise/topic.php/SMS_STATE_SYSTEM_full_of_errors/?TopicId=66971&Posts=4 All clients states are now reporting correctly Client 5.00.7958.1501 SCEP 188.8.131.52 So it would seem the effected clients were sending corrupt status updates.
By Norphy in forum General Chat Replies: 30 Last Post: 6th December 2006, 04:55 PM « OWA authentication | Backup exec 2010. thanks again. #3 Online Bookmarks Sharing: Jump to: Jump to - - - - - - - - - - [General Tech Discussion] - - - - General Tech Discussion I assumed these are related? And good luck. : ) Free Windows Admin Tool Kit Click here and download it now September 16th, 2014 10:25pm We have also a lot of these messages in our logfile.
Thanks for any help you can provide.
Send PM 2 Thanks to Worker-24601: Dos_Box(19th July 2013), Norphy(19th July 2013) 19th July 2013,07:16 PM #10 Norphy Join Date Jan 2006 Location Laaaandan Posts 3,707 Thank Post 95 Thanked this content LinkBack LinkBack URL About LinkBacks Bookmark & Share Digg this Thread!Add Thread to del.icio.usBookmark in TechnoratiTweet this threadShare on Facebook!Reddit! Perhaps I should put a post on Technet and see what the big M have to say Send PM 19th July 2013,11:01 PM #11 Worker-24601 Join Date Jul 2013 Posts Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information. Kb2840628
How does backup exec deal with deleted files » DotNet Update killed my SCCM Thread Information Users Browsing this Thread There are currently 1 users browsing this thread. (0 members and I recently starting receiving the same errors, onlyon one machine, but my statesys.log has a different error.. *** *** Unknown SQL Error!SMS_STATE_SYSTEM10/29/2013 8:37:50 AM8764 (0x223C) CMessageProcessor - Encountered a non-fatal I did an upgrade with all pre reqs met,the server OS is 2k3 R2 standardSQL is SQL Server 9.0.3054sorry if i posted in teh wrong place but i cant see a weblink Thanks a bunch Norphy. -Joey Send PM Thanks to jleclerc from: PaulCooper(12th August 2013) 12th July 2013,07:10 PM #4 Norphy Join Date Jan 2006 Location Laaaandan Posts 3,707 Thank Post
Send PM Thanks to Norphy from: PaulCooper(12th August 2013) 11th July 2013,03:54 PM #2 Michael Join Date Dec 2005 Location Birmingham Posts 10,962 Thank Post 287 Thanked 1,938 Times in Thanks to all contributors...let's hope this is the last I see of these symptoms! I'm looking at my WSUS server and the Server 2012 .NET Framework 4.5 patches for July patch Tuesday would be: KB2833958 and KB2840632 Try removing those two patches and let us
I looked at the StateSys.log and found a whole load of these: Code: STATMSG: ID=6104 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_STATE_SYSTEM" SYS=CM12-MP.internal.lutonsfc.ac.uk SITE=SFC PID=2660 TID=5516 GMTDATE=Thu Jul 11 12:56:28.353 2013 ISTR0="TD59CGDS.SMX" ISTR1="" Some times this issue happen after upgrading, and restart is required. If it comes up again I will check for that non-fatal error and let you know. System Center TechCenter Sign in United States (English) Brasil (Português)Česká republika (Čeština)Deutschland (Deutsch)España (Español)France (Français)Indonesia (Bahasa)Italia (Italiano)România (Română)Türkiye (Türkçe)Россия (Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home2012Previous
For now I can tell you If everything is ok, until next crash if it happens ? Powered by vBulletin Copyright © 2016 vBulletin Solutions, Inc. I did an upgrade with all pre reqs > >> > met, > >> > the server OS is 2k3 R2 standard > >> > SQL is SQL Server 9.0.3054 > check over here No further replies will be accepted.
Login. Error in the re look like this: SMS_STATE_SYSTEM: SeverityTypeSite codeDate / TimeSystemComponentMessage IDDescription ErrorMilestone2057/16/2013 6:23:02 AMSC2012.galesburg205.orgSMS_STATE_SYSTEM6105The State System message file processing processed one or more files that contained errors or invalid Covered by US Patent. Severity,Type,Site code,Date / Time,System,Component,Message ID,Description,Thread ID,Process ID Error,Milestone,ZEN,4/25/2012 3:51:47 PM,WHLSCCM,SMS_STATE_SYSTEM,6105,The SMS State System message file processing processed one or more files that contained errors or invalid data.
When trying to add/modify packages I got an error saying something about "failure generating lantern", now behaving. I was just concerned since when I first encountered it, I did some research and while I only got one or two machines that generated this error, the research yielded that My needle was an anti-virus version causing problems with my Exchange server. The updates in question are KB2835393 and KB2804576.
Please let me know. 0 Message Author Comment by:msuser12010-03-17 The SCCM runs on Server 2008 and SQL server is 2008 and also runs on other windows server 2008. Is there a preferred document that enumerates AV prerequisites/recommendations for SCCM site servers? Review the statesys.log file for further details.,6652,6828 The statesys.log shows the following pertinent entries: CStateMsgReaderXML::OpenFile - Failed to open file C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\statesys.box\process\KVLY2I3H.SMX for reading: A sharing violation occurred Easy remote access of Windows 10, 7, 8, XP, 2008, 2000, and Vista Computers Click here to find out more Reboot Hundreds of computers, disable flash drives, deploy power managements settings.
So I looked this up and found out that it means the usertype variable was expecting a default entry and there was none. Looking in STATESYS.LOG I see this: STATESYS.LOG CThreadMgr::ThreadTerminating - All threads have stopped runningSMS_STATE_SYSTEM7/16/2013 6:22:17 AM5680 (0x1630) State message processing processed invalid records or files in the last processing cycle.SMS_STATE_SYSTEM7/16/2013 6:22:32