'SMS 2003 Status: Message Monitoring' encountered a runtime error.
Goto the MOM 2005 Home Page
 
After importing the SMS 2003 MP to MOM 2005, the follow alerts had been issued every hours.(sd-sms-01 is SMS 2003 Server)

Description:
SD-SMS-01 - SMS 2003 Status: Script error.
The script 'SMS 2003 Monitor SMS Status Messages' running under processing rule 'SMS 2003 Status: Message Monitoring' encountered a runtime error.
Failed to process SMS status messages.
The error returned was: '' -2147467259 (0x80004005)

Contributed By: Peter Lamanna [MSFT]
If you installed MOM 2005 SP1, on the CD you will find the RTW version of the SMS 2003 Management Pack. Did you import that version?

If you did, turn on MOM Agent logging on one of your SMS Site Database Servers, typically also your Primary Site Server. This can be done by setting the EnableActiveDebugging registry value to 1 and then restarting the MOM Service.

[HKEY_LOCAL_MACHINE\SOFTWARE\Mission Critical Software\OnePoint]
"EnableActiveDebugging"=dword:00000001

The AgentResponse-"your config group name".log file can be found under the Windows\Temp\Microsoft Operations Manager folder. All scripts log to this one and only file. Search for the section that corresponds to the SMS 2003 Monitor SMS Status Messages script. When the script successfully executes its logging should look something like

--- RESPONSE: 'script: SMS 2003 Monitor SMS Status Messages' succeeded.
STARTTIME: 08/29/2005 20:02:00 ENDTIME: 08/29/2005 20:02:01
--- Output ---
[Trace]:SMS 2003 Monitor SMS Status Messages script starting at local time:
8:02:00 PM
[Trace]:'master' is not an SMS site database.
[Trace]:'model' is not an SMS site database.
[Trace]:'msdb' is not an SMS site database.
[Trace]:'Northwind' is not an SMS site database.
[Trace]:'pubs' is not an SMS site database.
[Trace]:'SMS_FLA' is an SMS site database.
[Trace]:Checking if this database is active in site 'FLA' for site server 'COMPUTER1'.
[Trace]:Connecting to WMI Registry :
winmgmts:\\COMPUTER1.DOMAIN1.com\root\default:StdRegProv
[Trace]:Value of Registry Key: SOFTWARE\Microsoft\SMS\Operations Management\SMS Server Role\SMS SQL Server\Site Code = FLA [Trace]:The database is active.
[Trace]:Processing status messages in the database.
[Trace]:The record ID of the previous last status message processed was '866159'.
[Trace]:Set DATEFORMAT query: set DATEFORMAT mdy [Trace]:Executing query at local time: 8:02:01 PM [Trace]:Query completed at local time: 8:02:01 PM [Trace]:SMS Status Message query: select System.Netbios_Name0, System.Resource_Domain_OR_Workgr0, StatusMessage.Component, StatusMessage.MessageID, StatusMessage.ModuleName, StatusMessage.RecordID, StatusMessage.Severity, StatusMessage.SiteCode, StatusMessage.TopLevelSiteCode, StatusMessage.Win32Error from vStatusMessages AS StatusMessage join System_DISC as System on StatusMessage.MachineName=System.Netbios_Name0 join Sites as Site on StatusMessage.SiteCode=Site.SiteCode where Site.Version like '2.5%' and RecordID > 866159 and StatusMessage.MessageID in (505, 600, 672, 1016, 1020, 1025, 1028, 1035, 1037, 1048, 1049, 1055, 1056, 1062, 1069, 1097, 1098, 1104, 2401, 2500, 2514, 2601, 2701, 2809, 3303, 3307, 3400, 3500, 3501, 3530, 3604, 4903, 4908, 4909, 4912, 4913, 4916, 4917, 4951, 5000, 5002, 5004, 5006, 5008, 5025, 5026, 5027, 5032, 5033, 5035, 5043, 5400, 5410, 5420, 5430, 5431, 5432, 5433, 5434, 5436, 5700, 5701, 5702, 11450, 11451, 11452, 11453, 11454, 11455, 11456, 11458) and StatusMessage.Component in ('SMS_AD_SYSTEM_DISCOVERY_AGENT', 'SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT',
'SMS_AD_USER_DISCOVERY_AGENT', 'SMS_CLIENT_CONFIG_MANAGERENT', 'SMS_CLIENT_INSTALL_DATA_MGR', 'SMS_COLLECTION_EVALUATOR', 'SMS_COMPONENT_STATUS_SUMMARIZER', 'SMS_COURIER_SENDER_CONFIRMATION',
'SMS_DESPOOLER', 'SMS_DISCOVERY_DATA_MANAGER', 'SMS_DISTRIBUTION_MANAGER', 'SMS_EXECUTIVE', 'SMS_HIERARCHY_MANAGER', 'SMS_INBOX_MANAGER', 'SMS_INBOX_MANAGER_ASSISTANT', 'SMS_INVENTORY_DATA_LOADER', 'SMS_INVENTORY_PROCESSOR', 'SMS_LAN_SENDER', 'SMS_MP_CONTROL_MANAGER', 'SMS_MP_DEVICE_MANAGER', 'SMS_MP_FILE_DISPATCH_MANAGER', 'SMS_NETWORK_DISCOVERY', 'SMS_OFFER_MANAGER', 'SMS_OFFER_STATUS_SUMMARIZER', 'SMS_POLICY_PROVIDER', 'SMS_REPLICATION_MANAGER', 'SMS_REPORTING_POINT', 'SMS_SCHEDULER', 'SMS_SITE_BACKUP', 'SMS_SITE_COMPONENT_MANAGER', 'SMS_SITE_CONTROL_MANAGER', 'SMS_SITE_SYSTEM_STATUS_SUMMARIZER',
'SMS_SOFTWARE_INVENTORY_PROCESSOR', 'SMS_SOFTWARE_METERING_PROCESSOR',
'SMS_SQL_MONITOR', 'SMS_STATUS_MANAGER', 'SMS_WINNT_SERVER_DISCOVERY_AGENT',
'Software Updates Sync Tool') and StatusMessage.Time > '8/27/2005 3:02:01 AM' order by RecordID asc [Trace]:Executing query at local time: 8:02:01 PM [Trace]:Query completed at local time: 8:02:01 PM [Trace]:The total number of status messages processed was '1'.
[Trace]:The record ID of the last status message processed was '866162'.
[Trace]:'tempdb' is not an SMS site database.
[Trace]:SMS 2003 Monitor SMS Status Messages script completed at local time:
8:02:01 PM
--- /Output ---
 

© FAQShop.com 2003 - 2008

Goto the MOM 2005 Home Page

Email the Author