Microsoft KB Archive/886114

= Discovery Data Records that contain a five-digit year value may cause the Discovery Data Manager to stop responding in Systems Management Server 2003 =

Article ID: 886114

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Systems Management Server 2003

-





SYMPTOMS
When the Microsoft Systems Management Server (SMS) 2003 Discovery Data Manager receives a discovery data record (DDR), it may continuously process the DDR. When this behavior occurs, the SMS Discovery Data Manager eventually stops responding (hangs).

In this scenario, the DDM.log file that is contained in the SMS\Logs folder on the SMS site server computer contains an error message that is similar to the following:

Processing file .DDR Processing  #14... ==>Name = < > Update base table: System_DISC : execute sql update System_DISC set ItemKey = 14, DiscArchKey = 5, SMS_UUID_Change_Date0 = &quot;02/14/22004 01:47:32&quot; where ItemKey = 14


 * update System_DISC set ItemKey = 14, DiscArchKey = 5, SMS_UUID_Change_Date0 = &quot;02/14/22004 01:47:32&quot; where ItemKey = 14


 * [22007][241][Microsoft][ODBC SQL Server Driver][SQL Server]Syntax error converting datetime from character string. CDiscoverySource_SQL::UpdateItem - could not execute sql- update System_DISC set ItemKey = 14, DiscArchKey = 5,

SMS_UUID_Change_Date0 = &quot;02/14/22004 01:47:32&quot; where ItemKey = 14 CDiscoverDataManager::ProcessDDRs_PS - Unable to update data source STATMSG: ID=2636 SEV=E LEV=M SOURCE=&quot;SMS Server&quot; COMP=&quot;SMS_DISCOVERY_DATA_MANAGER&quot; SYS= SITE=  PID=1496 TID=1832 GMTDATE=Wed Feb 25 20:00:48.663 2004 ISTR0=&quot;C:\SMS\inboxes\ddm.box\ .DDR&quot; ISTR1=&quot;&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 CDiscoverDataManager::ProcessDDRs_PS - SQL problem detected. Will retry later.

Additionally, the SMSCfg.ini file in the SMS\Logs folder contains a five-digit year value, as in the following example:

SMS_UUID_Change_Date0 = &quot;02/14/22004 01:47:32

Note The SMS\Logs folder is located on the SMS client computer.



CAUSE
This problem occurs because SQL cannot convert the five-digit year that is contained in the DDR record in question. For example, the date stamp in the DDR record is &quot;02/14/22004&quot; instead of &quot;02/14/2004.&quot; In this scenario, SQL reports a syntax error in the DDM.log file on the SMS site server computer.



RESOLUTION
To resolve this issue, you must fix the problem in the system clock on the SMS client computer. You must also delete the bad DDR and then change the SMScfg.ini file on the SMS client computer. To do this, use the following methods.

Delete the DDRs that contain the five-digit year

 * 1) Log on to the SMS site server computer by using an account that has administrative permissions.
 * 2) Use Windows Explorer to locate the SMS\inboxes\ddm.box folder on the SMS site server. Right-click the DDR file that contains the five-digit year, and then click Delete.

Note The DDR file name is listed in the DDM.log file.

Change the SMScfg.ini file

 * 1) Log on to the SMS client computer by using an account that has administrative permissions.
 * 2) Use Windows Explorer to locate the SMSCfg.ini file in the WINNT or Windows folder on the SMS client computer. Right-click the SMSCfg.ini file that contains the five-digit year, point to Open With, click Notepad, and then click OK.
 * 3) In Notepad, locate the Last SMSUID Change Date property, and then change the date value to the correct date.
 * 4) On the Notepad File menu, click Save.



STATUS
This behavior is by design.

Keywords: kbtshoot kbprb KB886114

-

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

© Microsoft Corporation. All rights reserved.