Table 26.21 SMS Collection Evaluator (Message IDs 2500 to 2541)

2500

Error

SMS Collection Evaluator failed to enumerate collections.

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.

2501

Informational

SMS Collection Evaluator created an .adc (create collection) file for collection %1. If this occurs at startup, it is not a problem and this message can be ignored.

Possible cause: The SMS SQL Monitor service is not running.

Solution: Restart SMS SQL Monitor. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.

Possible cause: The collection was created before SMS SQL Monitor had time to install the trigger.

Solution: Look in the registry for HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Triggers\<site_code>\
Coll_Add. If that key exists, the trigger was installed (make sure Active is set to 0x1). If not, SMS Collection Evaluator was unable to write to the registry. In that case, check for low disk space on the site server, or an SMS Service account that lacks privileges to write to the registry.

2502

Informational

SMS Collection Evaluator created an .udc (update collection) file for collection %1. If this occurs at startup, it is not a problem and this message can be ignored.

Possible cause: The SMS SQL Monitor service is not running.

Solution: Restart SMS SQL Monitor. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.

Possible cause: The collection was created before SMS SQL Monitor had time to install the trigger.

Solution: Look in the registry for HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Triggers\<site_code>\
Coll_Upd. If that key exists, the trigger was installed (make sure Active is set to 0x1). If not, SMS Collection Evaluator was unable to write to the registry. In that case, check for low disk space on the site server, or an SMS Service account that lacks privileges to write to the registry.

2503

Informational

SMS Collection Evaluator replicated full collection details for collection %1 to all subsites.

2504

Warning

SMS Collection Evaluator failed to find collection %1. SMS Collection Evaluator received a .udc (update collection) or .adc (create collection) file for a collection that does not exist.

Possible cause: The collection was deleted shortly after being created or updated, but SMS SQL Monitor and SMS Collection Evaluator processed the create or update file out of sequence.

Solution: None needed. The create or update file will simply not be processed for the nonexistent collection.

2505

Warning

A SQL Server operation successfully updated collection %1, but the operation could not set the collection’s Update flag to 0, meaning the collection will be updated again next time whether it needs to be or not.

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.

2506

Informational

This site has changed its parent site. SMS Collection Evaluator is deleting all collections from the previous parent site.

2507

Error

SMS Collection Evaluator failed to delete collection %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.

2508

Informational

Site %1 has been created. SMS Collection Evaluator is preparing to replicate all collections to the new child site.

2509

Warning

Collection %1 has no update schedule. SMS Collection Evaluator will not automatically update this collection’s membership.

Solution: Update the collection manually using the SMS Administrator console. Right-click the collection, point to All Tasks, then choose Update Collection Membership. Alternatively, you can specify an update schedule for the collection using the SMS Administrator console.

2510

Informational

SMS Collection Evaluator is beginning to update the membership of collection %1.

2511

Error

SMS Collection Evaluator failed to update the membership of collection %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.

2512

Error

SMS Collection Evaluator failed to replicate collection %1 to child sites.

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.

2513

Informational

SMS Collection Evaluator received an .adc (add collection) file for collection %1, is creating a result table in the SMS site database, and is updating the collection’s membership.

2514

Error

SMS Collection Evaluator received an .adc (add collection) file for collection %1, but failed to create a result table in 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.

2516

Informational

SMS Collection Evaluator received an .adc (add collection) file for collection %1, created a result table in the SMS site database, and updated the collection’s membership.

2517

Error

SMS Collection Evaluator failed to replicate file %1 to child sites.

Possible cause: Low disk space on the disk drive containing \Sms\Inboxes\Colleval.box.

Solution: Make more space available on that drive.

Otherwise, look for other status messages before this one; they will give you clues about what is happening.

2518

Error

SMS Collection Evaluator failed to enumerate the member site list for a resource with SMS identifier (GUID or SMSID): %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. 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.

2519

Error

SMS Collection Evaluator failed to enumerate members of collection %1 at site %2.

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.

2520

Error

SMS Collection Evaluator failed to write to file %1.

Possible cause: Low disk space on the drive containing the file %1.

Solution: Make more space available on that drive.

Possible cause: The file %1 is read-only.

Solution: Clear the Read-only attribute from the file’s Properties dialog box.

Possible cause: Another process has the file %1 locked.

Solution: Wait for the other process to finish, then retry the operation.

Possible cause: The file %1 is corrupt.

Solution: Delete the file, and then stop and restart SMS Collection Evaluator. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.

2521

Error

SMS Collection Evaluator failed to retrieve collection %1 from the collection source. (On primary sites, the collection source is the SMS site database. On secondary sites, it is \Sms\inboxes\colleval.box.)

Possible cause on primary sites: 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 secondary sites: The file in \Sms\inboxes\colleval.box is corrupt.

Solution: Delete the file, and then stop and restart SMS Collection Evaluator. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.

2522

Error

SMS Collection Evaluator failed to write to file %1.

Possible cause: Low disk space on the drive containing the file %1.

Solution: Make more space available on that drive.

Possible cause: The file %1 is read-only.

Solution: Clear the Read-only attribute from the file’s Properties dialog box.

Possible cause: Another process has the file %1 locked.

Solution: Wait for the other process to finish, then retry the operation.

Possible cause: The file %1 is corrupt.

Solution: Delete the file, and then stop and restart SMS Collection Evaluator. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.

2523

Error

SMS Collection Evaluator failed to enumerate membership rules for collection %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.

2524

Error

SMS Collection Evaluator failed to write to file %1.

Possible cause: Low disk space on the drive containing the file %1.

Solution: Make more space available on that drive.

Possible cause: The file %1 is read-only.

Solution: Clear the Read-only attribute from the file’s Properties dialog box.

Possible cause: Another process has the file %1 locked.

Solution: Wait for the other process to finish, then retry the operation.

Possible cause: The file %1 is corrupt.

Solution: Delete the file, and then stop and restart SMS Collection Evaluator. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.

2525

Error

SMS Collection Evaluator failed to enumerate subcollections for collection %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.

2526

Error

SMS Collection Evaluator failed to write to file %1.

Possible cause: Low disk space on the drive containing the file %1.

Solution: Make more space available on that drive.

Possible cause: The file %1 is read-only.

Solution: Clear the Read-only attribute from the file’s Properties dialog box.

Possible cause: Another process has the file %1 locked.

Solution: Wait for the other process to finish, then retry the operation.

Possible cause: The file %1 is corrupt.

Solution: Delete the file, and then stop and restart SMS Collection Evaluator. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.

2527

Error

SMS Collection Evaluator failed to read file %1.

Possible cause: The file %1 is corrupt.

Solution: Delete the file, stop and restart SMS Collection Evaluator (you can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components), and then update all collection memberships; in the SMS Administrator console, right-click Collections, point to All Tasks, and then choose Update Collection Membership.

2528

Warning

SMS Collection Evaluator cannot continue processing collection %2 because subcollection %1 has not been defined yet.

SMS Collection Evaluator is skipping collection %2 and will retry after it processes other collections.

Solution: Manually update the subcollection’s membership at the parent site; in the SMS Administrator console, right-click the collection, point to All Tasks, then choose Update Collection Membership.

2529

Error

SMS Collection Evaluator at a secondary site failed to write member data to collection %1.

Possible cause: Low disk space on the drive containing \Sms\Inboxes\Colleval.box.

Solution: Make more space available on that drive.

2530

Error

SMS Collection Evaluator failed to update collection %1 in the collection source. (On primary sites, this is the SMS site database. On secondary sites, this is \Sms\inboxes\colleval.box.)

Possible cause: Low disk space on the disk drive of the site server inbox.

Solution: Make more space available on that drive.

2531

Error

SMS Collection Evaluator failed to retrieve a SQL Server command from the collection membership rule.

Possible cause: An SMS Provider failure occurred while inserting the WBEM Query Language (WQL) string into the SQL Server database, or the rule was added improperly.

Solution: Recreate the rule in the SMS Administrator console and save it. If the WQL string had been stored correctly, it should remain after it was resaved, and the proper SQL string should be stored in the database.

2532

Error

SMS Collection Evaluator failed to connect to 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.

2533

Error

SMS Collection Evaluator failed to enumerate discovery architectures because it cannot retrieve the discovery architecture list from the 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.

2534

Warning

SMS Collection Evaluator failed to update the membership of collection %1 because it has been locked. SMS Collection Evaluator will retry updating the collection’s membership, and the update will eventually occur, but getting this message repeatedly might mean that a server process is locking a collection and then failing to unlock it when the process is finished. If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.

2535

Error

Collection %1 has no name. SMS Collection Evaluator cannot continue processing the collection without a name.

Solution: Add a name by editing the collection in the SMS Administrator console.

2536

Informational

SMS Collection Evaluator has created the collection result table for collection %1 in the SMS site database.

2537

Informational

SMS Collection Evaluator has updated the membership of collection %1.

2538

Informational

SMS Collection Evaluator has processed all direct rules for collection %1.

2539

Informational

SMS Collection Evaluator has processed all membership rules for collection %1.

2540

Informational

SMS Collection Evaluator has removed duplicate resources for collection %1.

Resources can be included in the same collection more than once if the same resource matches more than one membership criterion. Duplicates are removed to prevent the same resource from receiving the same advertisement multiple times.

2541

Informational

SMS Collection Evaluator has updated the results for collection %1.