Hi, The problem seems to be three fold and I am not sure if they are connected. My setup: Two Site Systems, Central (DP, RP) and child primary (DP, MP, SLP) Sites Servers, Central (FSP, SUP), Primary Child (WDS, WUS) Mode, Native OS, Windows 2008 SP1 Config Mgr, SCCM 2007 SP2 R2 I have recently started to see SMS_OFFER_STATUS_SUMMARIZER errors on the Child Primary site. MessageID: 3814 ProcessID: 7512 ThreadID: 3360 SMS Offer Status Summarizer cannot process a status message because it contains the invalid Advertisement ID "{B17E4736-79F7-472A-88BA-FBA8EB98FE7F}". As a result, the Advertisement Status summary data in the SMS Administrator console may be inaccurate. The message (ID 10008) was reported by component "Software Distribution" on computer "xxxxx" at site xxx on 03/07/2011 10:13:25. Please refer to the Microsoft Knowledge Base for more information. I have recently started to see SMS_STATE_SYSTEM messages on the Central site. MessageID: 6105 ProcessID: 16512 ThreadID: 15092 The SMS State System message file processing processed one or more files that contained errors or invalid data. Review the statesys.log file for further details. I have done a lot of research on this and can't get any further. I have not found anything that would point me in the direction of why this is happening. The only thing that I saw was the Inboxes\auth\statesys.box\currupt has 2375 .SMX files (Central site) and 742 (Child Primary). Inboxes\offermgr.box has 94 .ofn files (Central) and 70 (Child Primary)....Seems like a proccessing issues??? Any help at all guys would be really grateul.

statesys.log might be helpful. How old are those corrupt SMX files? You can also examine those files or query the database to get an idea how many different clients and AdvertisementID are affected.Torsten Meringer | http://www.mssccmfaq.de

Hi, Thanks for your quick response. The statesys.log only says... Found new state messages to process, starting processing thread Thread "State Message Processing Thread ~0" id: 13876 Started Thread "State Message Processing Thread ~0" id: 13876 terminated norrmally CThreadMgr::ThreadTerminating - All threads have stopped running The .ofn files go from 06/06/2011 to 16/06/2010, the .smx /smw files 06/07/2011 to 26/10/2010. I have opened the .smx files, but is there a specific thing I should be looking for? The .ofn files are 0kb with no data to view? Sorry if I sound like a newbie, but how would I go about querying the DB? Is this the easiest way or are the good old logs still the best route? Thanks again

HI, Even if someone can give me some process flow on why this would happen is much appreciated. I have 3000 clients not connecting. Once again, thanks

What does "client not connecting" mean? That's not a term of ConfigMgr. You can delete the files from the corrupt box. Just monitor how many will re-appear in the future. Keep in mind that the files in your corrupt box are up to an year old, so this is not necessarily an idication of a major problem.Torsten Meringer | http://www.mssccmfaq.de

When I use the term "Client not connecting", this is in reference to all the previous posts. Not wanting to repeat myself each time, I thought any comment would reflect the previous posts and not divert from the content of the post. The problem is still the same, and "Client not connecting" is used in the term that the clients are not getting there advertisements, using "Client not connecting" is used as a generic term to sum up the previous posts and not an exact description of the posts or terminology of System Centre Configuration Manager 2007. In summary and to clarify - I am receiving the errors noted in the above posts and would like some assistance in resolving an issue where clients are not retrieving "connecting" to their advertisements, which are designated to them.

Those state messages have absolutely nothing to do with receiving advertisements. State messages are sent from the client to the server (for example when sending software updates related states to the MP). "The message (ID 10008) was reported by component "Software Distribution" on computer "xxxxx" at site xxx on 03/07/2011 10:13:25". 10008 translates to "The program for advertisement "%1" completed successfully ("%4" - "%5"). User context: %9%12" if I am not mistaken, so this does indicate that the advertisements are working fine. 6105 = "The SMS State System message file processing processed one or more files that contained errors or invalid data. Review the statesys.log file for further details.%12". I already suggested troubleshooting tipps above. 3814 = "SMS Offer Status Summarizer cannot process a status message because it contains the invalid Advertisement ID "%6". As a result, the Advertisement Status summary data in the SMS Administrator console may be inaccurate." You would have to start troubleshooting with the AdvertisementID (%6). It would not worry too much if those errors are appearing only on a very rare basis, if all other things are working. What about the advertisement status messages (http://technet.microsoft.com/en-us/library/bb632740.aspx)? Are they basically working? I cannot see any errors in your postings that would indicate a problem that prevents ConfigMgr from working. Is the MP working at all (mplist / mpcert)? Torsten Meringer | http://www.mssccmfaq.de

Thank you for a quick and detailed response. I mentioned the state messages as this is the first time it has happened and within the same period of seeing the SMS Offer status summarizer messages. The latter was the first time these types of messages have appeared as well, if through luck or good initial configuration. I have been designing and troubleshooting SCCM 2007 in enterprises for over 3 years and still feel the troubleshooting aspect of SCCM 2007 is lacking. I can find documents and guides for everything else, so respectfully take you ides and opinions’ on board. I was more concerned with the first part of the message contained within 3814 -> SMS Offer Status Summarizer cannot process a status message because it contains the invalid Advertisement ID "{B17E4736-79F7-472A-88BA-FBA8EB98FE7F}". As a result, the Advertisement Status summary data in the SMS Administrator console may be inaccurate. and not the last part of the message -> "The message (ID 10008) was reported by component "Software Distribution" on computer "xxxxx" at site xxx on 03/07/2011 10:13:25". 10008 translates to "The program for advertisement "%1" completed successfully ("%4" - "%5"). User context: %9%12" if I am not mistaken, so this does indicate that the advertisements are working fine. If you could elaborate on why the ID 10008 indicates it is working OK if the first part of 3814 indicates an issue? In response to the troubleshooting to 6105, please see my response from above.. The statesys.log only says... Found new state messages to process, starting processing thread Thread "State Message Processing Thread ~0" id: 13876 Started Thread "State Message Processing Thread ~0" id: 13876 terminated norrmally CThreadMgr::ThreadTerminating - All threads have stopped running The .ofn files go from 06/06/2011 to 16/06/2010, the .smx /smw files 06/07/2011 to 26/10/2010. I have opened the .smx files, but is there a specific thing I should be looking for? The .ofn files are 0kb with no data to view? All seems OK in terms of the advertisements, but the workstations are not getting those advertisements assigned to them. The advertisements do not seem to have any other diverse effects to these messages. As soon as I shut down the primary child down a moment ago, all has come baxk, however, I did this the other day and they can back after 00.00 time period. I guess this is because of the 24 Hr+ sccm self healing process or whatever they want to call it.