Microsoft KB Archive/263913

= SMS: Delete Aged Discovery Task Always Reports Zero Items Deleted =

Article ID: 263913

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Systems Management Server 2.0 Standard Edition

-



This article was previously published under Q263913



SYMPTOMS
Systems Management Server status messages that are generated by SMS_SQL_MONITOR, reporting the deletion of Aged Discovery data, always report deletion of zero (0) items, regardless of the number of items that are actually deleted by the maintenance task.

An example of the status message text is:

SMS_SQL_MONITOR 2404 The database maintenance SQL task &quot;Delete Aged Discovery Data - System&quot; completed successfully. The task deleted 0 items from the SMS site database.



WORKAROUND
To determine the actual number of items deleted by the Delete Aged Discovery Data database maintenance task, the log for SMS_SQL_MONITOR must be examined directly.

As a prerequisite, logging must be enabled for the SMS_SQL_MONITOR component by doing the following steps:
 * 1) Open the Systems Management Server Administrator console.
 * 2) Navigate to the Tools node and expand it.
 * 3) Right-click SMS Service Manager, click All Tasks, and then click Start SMS Service Manager.
 * 4) In SMS Service Manager, expand .
 * 5) Click Components.
 * 6) In the right pane, highlight SMS_SQL_MONITOR.
 * 7) Right-click SMS_SQL_MONITOR and click Logging.
 * 8) Click Logging Enabled.
 * 9) Click OK and close SMS Service Manager.

NOTE: You should increase the size of the log file if you plan on using the above workaround on a periodic basis, because the log file may wrap frequently and lose the data you want to view. The default size of the log file is 1 megabyte (MB).

Once logging is enabled, verify the actual number of deleted Aged Discovery items:  After a scheduled Delete Aged Discovery Data task is finished, open the Systems Management Server Administrator console, and navigate to System Status. Navigate to Site Status, Your Site, and then Component Status. Locate SMS_SQL_MONITOR in the list. Right-click SMS_SQL_MONITOR, click Show Messages, and then click All. Locate status messages with an identification (ID) of 2404. Note the date and time of the status message. Using Notepad or a similar utility, open Smsdbmon.log from the Sms\Logs directory on the server where SMS_SQL_MONITOR resides.</li> Scan the log, locating an entry similar to the following that corresponds with the time of the status message:

STATMSG: ID=2404 SEV=I LEV=M SOURCE=&quot;SMS Server&quot; COMP=&quot;SMS_SQL_MONITOR&quot; SYS=SMSSERVERNC SITE=ABC PID=1108 TID=524 GMTDATE=Wed May 24 14:11:03.968 2000 ISTR0=&quot;Delete Aged Discovery Data - System&quot; ISTR1=&quot;0&quot; ISTR2=&quot;&quot; ISTR3=&quot;&quot; ISTR4=&quot;&quot; ISTR5=&quot;&quot; ISTR6=&quot;&quot; ISTR7=&quot;&quot; ISTR8=&quot;&quot; ISTR9=&quot;&quot; NUMATTRS=0

Above this entry you should see an entry similar to the following:

DeleteDiscoveryItems deleted 53 rows of architecture System.

This entry reflects the actual number of items deleted during the database maintenance task.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed this to be a problem in Systems Management Server version 2.0.

Additional query words: prodsms

Keywords: kbbug kbdatabase kbdiscovery kbprb kbstatsum KB263913

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.