|
 |
 |
 |
|
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms
of Use |
Trademarks
Article ID: 925969 - Last Review: February 8, 2007 - Revision: 1.1 Discovery data records (DDRs) remain queued in the ddm.box on a Systems Management Server 2003 site serverYou may experience the following symptoms on a Microsoft Systems Management Server (SMS) 2003 site server: - The SMS database is not updated with newly created objects after a discovery interval has passed.
- Discovery data records (DDRs) remain queued in the ddm.box inbox folder.
By default, the ddm.box folder is located in one of following locations:
- C:\SMS\inboxes\
- C:\SMS\inboxes\auth\
Additionally, the ddm.log file that is located in the \SMS\Logs folder may contain error messages that resemble the following: ***[42000][50000][Microsoft][ODBC SQL Server Driver][SQL Server]The GUID cannot be
changed once set.
MachineIdGroupXRef_upd
CDiscoverySource_SQL::UpdateItem - could not execute sql- IF EXISTS (select GUID
from MachineIdGroupXRef where MachineID = 42193 and ArchitectureKey = 5 ~) update
MachineIdGroupXRef set MachineID = 42193, ArchitectureKey = 5, GroupKey = 1, GUID =
"GUID:5D8427EE-DF95-4C8E-A110-3F087347CFAC" where MachineID = 42193 and
ArchitectureKey = 5~ ELSE insert into MachineIdGroupXRef (MachineID,
ArchitectureKey, GroupKey, GUID) values (42193, 5, 1,
"GUID:5D8427EE-DF95-4C8E-A110-3F087347CFAC")~
CDiscoverDataManager::ProcessDDRs_PS - Unable to update data source
This issue typically occurs when the DDR contains a corrupted SMS unique identifier.
To resolve this issue, you must remove the corrupted DDR from the ddm.box on the SMS site server. To do this, use one of the following methods. Manually remove the corrupted DDR record- Use an account that has administrative credentials to log on to the SMS site server.
- Click Start, point to Administrative Tools, and then click Services.
- In the Services MMC snap-in, right-click SMS_Site_Component_Manager, and then click Stop.
- Click Start, point to All Programs, click Systems Management Server, and then click SMS Administrator Console.
- Expand Site Database (SiteCode-SiteName), and then expand Tools.
- Right-click SMS Service Manager, point to All Tasks, and then click Start SMS Service Manager.
- In SMS Service Manager, expand SiteCode, and then expand Components.
- Click SMS_DISCOVERY_DATA_MANAGER.
- In the right-pane, right-click SMS_DISCOVERY_DATA_MANAGER, and then click Query.
- After the query is complete, right-click SMS_DISCOVERY_DATA_MANAGER, and then click Stop.
- Locate the sms\inboxes\ddm.box folder or the sms\inboxes\auth\ddm.box folder that contains the corrupted DDR file by using Windows Explorer, and then delete the DDR file.
- Right-click SMS_DISCOVERY_DATA_MANAGER, and then click Start.
- In the Services MMC snap-in, right-click SMS_Site_Component_Manager, and then click Start.
Use SQL Query Analyzer to locate the corrupted DDR record- Click Start, point to All Programs, point to Microsoft SQL Server, and then click Query Analyzer.
- In the Connect to SQL Server dialog box, specify the instance of SQL Server to which you want to connect, specify the type of authentication that you want to use, and then click OK.
- In SQL Query Analyzer, select the SMS database from the list of databases.
- To obtain a list of computers that are creating corrupted DDR files, copy and paste the following query in the Editor pane of SQL Query Analyzer, and then click Execute Query:
select sys.Netbios_Name0 from System_DISC sys join MachineIdGroupXRef xref on
sys.ItemKey=xref.MachineID where IsNULL(SMS_Unique_Identifier0,'') != IsNULL(GUID,'')
Note If the SMS clients continue to send corrupted DDR files, the SMS clients may be adding incompatible information to the DDR file. For example, these SMS clients may use Windows Management Instrumentation (WMI) tables that are incompatible with tables in the SMS database. To resolve this issue, remove the SMS agent from the affected client computer, and then reinstall the SMS agent on the client computer.
For more information about how to remove an SMS 2003 client, click the following article number to view the article in the Microsoft Knowledge Base:
826842Â
(http://kbalertz.com/Feedback.aspx?kbNumber=826842/
)
How to remove a Systems Management Server 2003 client
918914Â
(http://kbalertz.com/Feedback.aspx?kbNumber=918914/
)
The ddm.box inbox folder is backlogged with many DDRs, and the SMS database is not updated with newly created objects in Systems Management Server 2003
923113Â
(http://kbalertz.com/Feedback.aspx?kbNumber=923113/
)
After you upgrade SMS 2003 sites to SMS 2003 Service Pack 1, performance may decrease significantly
816051Â
(http://kbalertz.com/Feedback.aspx?kbNumber=816051/
)
SMS Primary Site processes discovery and inventory data very slowly
871161Â
(http://kbalertz.com/Feedback.aspx?kbNumber=871161/
)
A description of inbox folders and how they are used in Systems Management Server
APPLIES TO- Microsoft Systems Management Server 2003
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
|
|
 |
|
 |
|
|
|
| |