%11Collection Evaluator failed to retrieve collection "%1" from the collection source. (On primary sites, the collection source is the site database. On secondary sites, it is \Sms\inboxes\colleval.box.)%12 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 the site can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. 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 Collection Evaluator. You can use Configuration Manager Service Manager, which is invoked from the Configuration Manager Console, to stop and start components.%0
Collection Evaluator failed to process Collection Settings for Collection %1. This Collection Settings will be retried %2 ...
Collection Evaluator failed to process Collection Settings Replication File %1 as Collection %2 referenced object of type ...
Collection Evaluator failed to process Collection Settings Replication File %1. This Collection Settings Replication file ...
Collection Evaluator failed to retrieve a SQL Server command from the collection membership rule.%12 Possible cause: An SMS ...
Collection Evaluator failed to retrieve collection "%1" from the collection source. (On primary sites, the collection source ...
Collection Evaluator failed to update collection "%1" in the collection source. (On primary sites, this is the site database. ...
Collection Evaluator failed to update the membership of collection "%1".%12 Possible cause: SQL Server problem. Solution: ...
Collection Evaluator failed to update the query rule "%1" of collection "%2" (%3).%12 Possible cause: Inventory or Resource ...
Collection Evaluator failed to write to file "%1".%12 Possible cause: low disk space on the drive containing the file "%1". ...