Table 26.22 SMS Discovery Data Manager (Message IDs 2600 to 2638)

Message ID	Severity	Message
2600	Error	SMS Discovery Data Manager failed to synchronize this site’s deletions with all secondary site databases. When discovery data is deleted, the deletion must be propagated to all secondary sites. In addition, any licenses associated with the deleted resources must be revoked. Because secondary site data is not synchronized, more licenses will be used than is necessary. Possible cause: SQL Server problem on this site or one or more secondary sites. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.
2601	Error	SMS Discovery Data Manager failed to connect to the discovery database. Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.
2602	Informational	SMS Discovery Data Manager is removing references from deleted site %1.
2603	Informational	SMS Discovery Data Manager is beginning the process of sending discovery data to the new parent site. (This happens whenever a site attaches to a new parent site.)
2604	Warning	SMS Discovery Data Manager failed to send discovery data to the new parent site. SMS Discovery Data Manager will retry, resuming where it left off.
2605	Error	SMS Discovery Data Manager failed to move the new parent site notification file to the Data Loader inbox. Possible cause: Low disk space on the disk drive of the Data Loader inbox. Solution: Make more space available on that drive.
2606	Error	SMS Discovery Data Manager has tried ten times to send the discovery database to the new parent site, and SMS Discovery Data Manager has been unsuccessful each time. SMS Discovery Data Manager is giving up. Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.
2607	Informational	SMS Discovery Data Manager has successfully sent the discovery database to the parent site.
2608	Error	SMS Discovery Data Manager failed to send file %1 to site %2. Possible cause: Low disk space on the disk drive of the destination site server. Solution: Make more space available on that drive.
2609	Error	SMS Discovery Data Manager failed to enumerate discovery architectures. Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.
2610	Error	SMS Discovery Data Manager failed to create the discovery data record (DDR) to send to the new parent site. Possible cause: Low memory. Solution: Stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.
2611	Informational	SMS Discovery Data Manager has detected a change in assignment rules. SMS Discovery Data Manager will not process discovery data records (DDRs) until it completes the rule refresh operation.
2612	Error	SMS Discovery Data Manager failed to complete the rule refresh process. Possible cause: Refer to the previous SMS Discovery Data Manager message.
2613	Error	SMS Discovery Data Manager failed to read the serial number from the parsed discovery data record (DDR) %1. Possible cause: The file %1 is corrupt. Solution: Delete file %1. Possible cause: Low memory. Solution: Stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.
2614	Error	SMS Discovery Data Manager failed to read the new discovery item from the parsed discovery data record (DDR) %1. Possible cause: The file %1 is corrupt. Solution: Delete file %1. Possible cause: Low memory. Solution: Stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.
2615	Error	SMS Discovery Data Manager failed to parse the new discovery item data from the parsed discovery data record (DDR) %1. Possible cause: The file %1 is corrupt. Solution: Delete file %1. Possible cause: Low memory. Solution: Stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.
2616	Error	SMS Discovery Data Manager failed to insert the new item from file %1 into the data source. Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.
2617	Error	SMS Discovery Data Manager failed to write the serial number record to file %1. Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs. Possible cause: Low disk space on the disk drive of the destination site server. Solution: Make more space available on that drive.
2618	Error	SMS Discovery Data Manager failed to write the item key record to file %1. Possible cause: Low disk space on the disk drive of the destination site server. Solution: Make more space available on that drive.
2619	Error	SMS Discovery Data Manager failed to write item buffer to file %1. SMS Discovery Data Manager is attempting to send a discovery data record (DDR) to another site or registered consumer, but is unable to write the data for the new item. Possible cause: Low disk space on the disk drive of the destination site server. Solution: Make more space available on that drive.
2620	Error	SMS Discovery Data Manager failed to format discovery data into file %1. Possible cause: Low memory. Solution: Stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.
2621	Error	SMS Discovery Data Manager failed to enumerate properties for architecture %1. Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.
2622	Error	SMS Discovery Data Manager failed to process file %1 because it cannot detect any Name properties. SMS Discovery Data Manager requires that all discovery data records (DDRs) report at least one field that is defined as a Name candidate. The three default architectures — User, User Group, and System — all have one or more defined Name fields. Either this DDR is not of one of those three architectures, or it is an invalid DDR. Possible cause: An SMS Discovery Data Manager bug. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. Possible cause: Something other than SMS created the DDR, and no value was specified as the Name. Solution: Every discovery item needs to have some value that can be identified as the name of the resource. In System DDRs, for example, one of the following values is used as the Name: NetBIOS Name, Resource Names, IP Addresses, IPX Addresses, or MAC Addresses. If none of these are available, or if you have created a DDR of a new architecture, then pick a property and flag it as the Name by ORing decimal 64 in the property’s Flags column.
2623	Error	SMS Discovery Data Manager failed to insert discovery data because SMS is out of client access licenses. Solution: Increase the number of client access licenses. You can purchase more from your Microsoft sales representative.
2624	Error	SMS Discovery Data Manager failed to read the current site’s .ncf (assignment rule) file. Possible cause: The file is corrupt. Solution: See if an .ncf file exists in the directory Inboxes\Ddm.box\Data.col. If so, delete it. The site control file will re-create it. If there is no .ncf file in that directory, stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.
2625	Error	SMS Discovery Data Manager failed to read the .ncf (assignment rule) file for site %1. Possible cause: The file is corrupt. Solution: See if an .ncf file exists in the directory Inboxes\Ddm.box\Data.col. If so, delete it. The site control file will re-create it. If there is no .ncf file in that directory, stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.
2626	Error	SMS Discovery Data Manager failed to open the .ncf (assignment rule) file for site %1. Possible cause: The file is corrupt. Solution: See if an .ncf file exists in the directory Inboxes\Ddm.box\Data.col. If so, delete it. The site control file will re-create it. If there is no .ncf file in that directory, stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.
2627	Error	SMS Discovery Data Manager failed to read the site control file for site %1. Because the SMS site database maintains the site control files for this site and all sites beneath it, SMS Discovery Data Manager reads site control files only from the SMS site database. Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.
2628	Warning	SMS Discovery Data Manager failed to write the .ncf (assignment rule) file %1. SMS Discovery Data Manager will retry writing this file during its next processing cycle. Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive.
2629	Warning	SMS Discovery Data Manager failed to copy the .ncf (assignment rule) file %1 to Asstdata.box, the point of replication to client access points (CAPs). SMS Discovery Data Manager will retry copying this file during its next processing cycle. Possible cause: Low disk space on the disk drive containing Asstdata.box. Solution: Make more space available on that drive.
2630	Informational	During a refresh, SMS Discovery Data Manager detected that assignment rules had changed. Therefore, SMS Discovery Data Manager is stopping the refresh now, but will perform it later.
2631	Error	SMS Discovery Data Manager failed to create a full refresh file to send to the secondary site. Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive.
2632	Error	SMS Discovery Data Manager failed to notify all consumers that a full refresh has occurred and that users need to refresh their data store. Possible cause: Because these notifications are done by a file, there is probably low disk space on one or more destination disk drives. Solution: Make more space available on those disks.
2633	Error	SMS Discovery Data Manager failed to send file %1 to site %2. Possible cause: Low disk space on site %2. Solution: Make more space available on the disk drive containing \Sms\Inboxes on site %2.
2634	Informational	SMS Discovery Data Manager will resume processing because it has successfully completed assignment-rule processing.
2635	Error	While parsing discovery data record (DDR) %1, SMS Discovery Data Manager found a blank Architecture field, which makes %1 a bad DDR. Possible cause: Something other than SMS created the DDR, and no value was specified as the Architecture. Solution: Re-create the DDR, specifying an architecture as part of the discovery item format. Possible cause: an SMS Discovery Data Manager bug. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
2636	Error	SMS Discovery Data Manager failed to process the discovery data record (DDR) %1, because it cannot update the data source. Possible cause: On a Primary site, it is probably a SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs. Possible cause: On a secondary site, SMS Discovery Data Manager probably cannot write to a file on the site server, so check for low disk space on the site server. Solution: Make more space available on the site server.
2637	Informational	SMS Discovery Data Manager is updating statistics in all tables in the SMS site database, which helps ensure optimal performance of SQL Server 6.5.
2638	Informational	SMS Discovery Data Manager has interpreted discovery data record (DDR) %1 as a delete request. Therefore, SMS Discovery Data Manager is deleting item %2 of architecture %3. DDR %1 contains an old item, but not a new item.