SMS_STATE_SYSTEM 11/07/2013 13:56:43 5832 (0x16C8) CMessageProcessor - Encountered a non-fatal SQL error while processing SMS_STATE_SYSTEM 11/07/2013 13:56:43 5832 (0x16C8) CMessageProcessor - Non-fatal error while processing 3BNBYR4C.SMX SMS_STATE_SYSTEM 11/07/2013 13:56:43 5832 (0x16C8) I will also ensure all necessary AV exclusions are configured by the security team before re-installing the AV client on these servers. Back to top #7 CraigSCCM CraigSCCM Advanced Member Established Members 47 posts Gender:Male Posted 05 November 2015 - 12:13 PM Yeah we have the intune connector set up too, so we Review the statesys.log file for further details. 0 LVL 23 Overall: Level 23 MS Server OS 9 Message Expert Comment by:Nagendra Pratap Singh2013-04-12 Please attach statesys.log here. his comment is here
How does backup exec deal with deleted files » DotNet Update killed my SCCM Thread Information Users Browsing this Thread There are currently 2 users browsing this thread. (0 members and and Code: The State System message file processing could not process file 'r9c06kn1.SMX' and moved it to the corrupt directory. any clues in the'statesys.log' file?StevePost by rob-adoghi,i am using the local system account so didnt think this would be an issue?Post by Steve ThompsonIt's possibly an SPN issue...http://technet.microsoft.com/en-us/library/bb735885.aspxPost by rob-adogAfter upgrading Use workaround or uninstall. 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
https://support.micr...n-us/kb/3106034 Attached Images Back to top #10 Bumbi85 Bumbi85 Advanced Member Established Members 48 posts Posted 05 November 2015 - 02:16 PM Im thinking more in the line that the mobile SEO by vBSEO ©2011, Crawlability, Inc. 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
Promoted by Recorded Future Are you wondering if you actually need threat intelligence? All rights reserved. So I scratched my head, swore a bit checked the health of the server components. Get 1:1 Help Now Advertise Here Enjoyed your answer?
Are the remaining COnfigMgr components working fine? Statesys.log Location The State System message file processing could not process file 'N_hn1meweb.SMX' and moved it to the corrupt directory. Thread Tools Search Thread Advanced Search 11th July 2013,03:38 PM #1 Norphy Join Date Jan 2006 Location Laaaandan Posts 3,707 Thank Post 95 Thanked 778 Times in 570 Posts Blog pop over to these guys These are .NET Framework 4.0 patches and Windows 2012 comes with .NET Framework 4.5.
Uninstalled KB2835393, KB2804576 and KB2840628 - rebooted the server, and now both the SQL errors in the statesys.log and the package issues are fixed. this content thanks again. #3 Online Bookmarks Sharing: Jump to: Jump to - - - - - - - - - - [General Tech Discussion] - - - - General Tech Discussion The error I get in the statesys.log actually points to a problem with the database. Covered by US Patent. Kb2840628
I uninstalled all of the OS updates first. Login. OK SMS_STATE_SYSTEM Critical, loads of errors :( Started by CraigSCCM , Nov 04 2015 09:36 AM SMS_STATE_SYSTEM Errors Page 1 of 4 1 2 3 Next » Please log in to weblink Customer Impact:Analysis of incident scope is underway.Some customers may be impacted by this event.
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. ErrorMilestone2057/16/2013 6:22:17 AMSC2012.galesburg205.orgSMS_STATE_SYSTEM6104The 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.
kb2840628 Saw the same in my logs. Tweeted MS Intune over the weekend and ticket was escalated (how much good that'll do I don't know!). No further replies will be accepted. Review the statesys.log file for further details.
Thursday, April 26, 2012 5:44 PM Reply | Quote 0 Sign in to vote Here's one from the ConfigMgr support team: http://blogs.technet.com/b/configurationmgr/archive/2010/11/30/configmgr-2007-antivirus-scan-and-exclusion-recommendations.aspx. 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 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 check over here Suggested Solutions Title # Comments Views Activity Exchange Management Console Error - Initialization falied 18 88 76d Group Policy Questions 2 38 52d Microsoft AD for Secure LDAP 3 31 36d
July 16th, 2013 7:51am What version of ConfigMgr (SP and CU level) are you using? I do see some errors like these SMS internal error occurred for the update af7dc638-2b83-4e09-8334-a0280452ffbb.