Error still reported to SCOM after clearing the origin
Hello, It was under "System Center TechCenter > System Center Configuration Manager" for awhile but no answer as it is related to SCOM also I am asking under tyhis forum. SCCM is clean and WSUS is working, it is why I am moving the thread here. I am receiving consistently the alerts about issues: CONFIGMGRSRV - ConfigMgr 2007 Status: WSUS Control Manager failed to configure proxy settings on WSUS Server. A new monitored SMS status message on machine CONFIGMGRSRV from component SMS_WSUS_CONTROL_MANAGER with message ID 7000 was found in the site SRV database. The status message contains message properties Machine Name: CONFIGMGRSRV Module Name: SMS Server Component: SMS_WSUS_CONTROL_MANAGER Message ID: 7000 Win32 Error: 0 Top Level Site Code: Database Record ID: 1316106 ---------------------------------------------------------------------------- CONFIGMGRSRV - ConfigMgr 2007 Status: WSUS Control Manager failed to configure proxy settings on WSUS Server. A new monitored SMS status message on machine CONFIGMGRSRV from component SMS_WSUS_CONTROL_MANAGER with message ID 7000 was found in the site SRV database. The status message contains message properties Machine Name: CONFIGMGRSRV Module Name: SMS Server Component: SMS_WSUS_CONTROL_MANAGER Message ID: 7000 Win32 Error: 0 Top Level Site Code: Database Record ID: 190816 ----------------------------------------------------------------------------CONFIGMGRDTS - ConfigMgr 2007 Status: WSUS Configuration Manager failed to configure upstream server settings on a WSUS Server. A new monitored SMS status message on machine CONFIGMGRDTS from component SMS_WSUS_CONFIGURATION_MANAGER with message ID 6600 was found in the site DTS database. The status message contains message properties Machine Name: CONFIGMGRDTS Module Name: SMS Server Component: SMS_WSUS_CONFIGURATION_MANAGER Message ID: 6600 Win32 Error: 0 Top Level Site Code: Database Record ID: 889151 ---------------------------------------------------------------------------- CONFIGMGRDTS - ConfigMgr 2007 Status: WSUS Synchronization failed. A new monitored SMS status message on machine CONFIGMGRDTS from component SMS_WSUS_SYNC_MANAGER with message ID 6703 was found in the site DTS database. The status message contains message properties Machine Name: CONFIGMGRDTS Module Name: SMS Server Component: SMS_WSUS_SYNC_MANAGER Message ID: 6703 Win32 Error: -2147467259 Top Level Site Code: Database Record ID: 889201 ---------------------------------------------------------------------------- CONFIGMGRMED - ConfigMgr 2007 Status: WSUS Synchronization failed. A new monitored SMS status message on machine CONFIGMGRMED from component SMS_WSUS_SYNC_MANAGER with message ID 6703 was found in the site MED database. The status message contains message properties Machine Name: CONFIGMGRMED Module Name: SMS Server Component: SMS_WSUS_SYNC_MANAGER Message ID: 6703 Win32 Error: -2146232832 Top Level Site Code: Database Record ID: 1341589 ---------------------------------------------------------------------------- CONFIGMGRMED - ConfigMgr 2007 Status: WSUS Configuration Manager failed to configure upstream server settings on a WSUS Server. A new monitored SMS status message on machine CONFIGMGRMED from component SMS_WSUS_CONFIGURATION_MANAGER with message ID 6600 was found in the site MED database. The status message contains message properties Machine Name: CONFIGMGRMED Module Name: SMS Server Component: SMS_WSUS_CONFIGURATION_MANAGER Message ID: 6600 Win32 Error: 0 Top Level Site Code: Database Record ID: 826188 ---------------------------------------------------------------------------- Any idea how to clear this? I have the same with SMS_SITE_BACKUP as well, the backups are doen but SCOM still reports failures... Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 Support
April 21st, 2010 2:20am

Hi Dom Is this alert from a rule or a monitor? It is an event collection rule so if it is from a monitor and the monitor has fired then it will most likely need you to reset it. Open the health explorer, go to the monitor in question and select "reset health" Paul Paul Keely
Free Windows Admin Tool Kit Click here and download it now
April 21st, 2010 9:54am

Hi Paul, These are "RULES" If I close the rule it reappears within an hour. Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 Support
April 21st, 2010 7:23pm

Have the same issue over here... Health ok .. sccm ok... I can remove the alerst but get the same ones back within a period of time
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2010 5:34pm

As a normal part of administering SCOM, one should consider turning off rules that don't seem useful to you. If you are not taking the actions to clear the problem (somewhere in WSUS configuration), then you can expect the rule to detect the problem whenever the event that drives it occurs. SCOM does not create the conditions that cause the alerts - it simply executes rule logic looking for the conditions. If no action is taken on the condition that causes the issue, and you find that you can safely go on living without ever taking the actdion that would clear the condition (these can be hard to figure out), then consider disabling the rule since you are not paying attention to it.Microsoft Corporation
July 14th, 2010 8:14pm

Dan, I can test every component and find no problem. The error is every time the same record in the database. If you google on this particular problem with the management pack you find many people reporting that there is possible an issue with the MP and that they hope Microsoft will fix it. Simply turning off rules and monitors because they are not working properly is not a solution. Please help us solve the issue. Arjan
Free Windows Admin Tool Kit Click here and download it now
July 15th, 2010 9:43am

Perhaps this helps to search for the root cause of the problem.. The status messages appear 24 hours and then don't come back. So there should be a parameter to override ... Health is ok... I removed the status messages from the ConfigMgr DB and still this message keep comming back. - ConfigMgr 2007 Status: Database Notification Monitor failed to execute a Site Maintenance task within the scheduled time. A new monitored SMS status message on machine <here was the server name> from component SMS_DATABASE_NOTIFICATION_MONITOR with message ID 2420 was found in the site VEL database. See this post comes to same conclusion but no answer http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/cd0518c5-1649-4f18-b184-9421ab1ea4a3
July 15th, 2010 1:31pm

These script continue to report until the record is out of the SCCM database? Messages keep comming even after 5 days? Is there really no other way then completely disable status message monitoring? SELECT [RecordID] ,[Time] FROM [SMS_VEL].[dbo].[v_StatusMessage] Where RecordID='1518626' Returns 1518626,2010-07-16 22:00:19.250
Free Windows Admin Tool Kit Click here and download it now
July 21st, 2010 1:43pm

There are no planned future updates to this management pack.Microsoft Corporation
July 23rd, 2010 6:25pm

There is taken the remark of Dan in considderation no other option than to disable this part of the MP because it is not working on a way that it adds something.. The status messages alerts cannot be resolved and come each hour. Some keep comming for days.. Cleaning the SCCM status messages is one thing... still if you have such an alert and you solved the issue you still have the message for days.. We still use the MP but configured an override for these status message alerts.
Free Windows Admin Tool Kit Click here and download it now
August 2nd, 2010 11:11am

No avtivity for a long time, will mark this thread as answer now. Feel free to re-open it.ThanksAnders Bengtsson | Microsoft PFE | blog at http://www.contoso.se
December 26th, 2010 9:22am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics