%11SMS Discovery Data Manager failed to connect to the discovery database.%12 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.%0
SMS Despooler received an instruction and package file from site %1 that contains either software distribution data or inter-site ...
SMS Despooler received an instruction and package file from site %1 that contains either software distribution data or inter-site ...
SMS Despooler received an instruction and package file from site %1 that contains that site's public key, however the despooler ...
SMS Discovery Data Manager failed to complete the rule refresh process.%12 Possible cause: Refer to the previous SMS Discovery ...
SMS Discovery Data Manager failed to connect to the discovery database.%12 Possible cause: SQL Server problem. Solution: ...
SMS Discovery Data Manager failed to copy the .ncf (assignment rule) file "%1" to Asstdata.box, the point of replication ...
SMS Discovery Data Manager failed to create a full refresh file to send to the secondary site.%12 Possible cause: Low disk ...
SMS Discovery Data Manager failed to create the discovery data record (DDR) to send to the new parent site.%12 Possible cause: ...
SMS Discovery Data Manager failed to enumerate discovery architectures.%12 Possible cause: SQL Server problem. Solution: ...