%11Discovery 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 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.%0
Disable alternate sources (such as Microsoft Windows Update, Microsoft Windows Server Update Services, or UNC shares) for ...
Disabling these drivers will prevent computers from installing these drivers. Computers currently running operating system ...
Disconnecting the out of band management console from this computer may require a restart. Restarting is required to re-enable ...
Discovery Data Manager failed to complete the rule refresh process.%12 Possible cause: Refer to the previous Discovery Data ...
Discovery Data Manager failed to connect to the discovery database.%12 Possible cause: SQL Server problem. Solution: 1. Review ...
Discovery Data Manager failed to copy the .ncf (assignment rule) file "%1" to Asstdata.box, the point of replication to client ...
Discovery Data Manager failed to create a full refresh file to send to the secondary site.%12 Possible cause: Low disk space ...
Discovery Data Manager failed to create the discovery data record (DDR) to send to the new parent site.%12 Possible cause: ...
Discovery Data Manager failed to enumerate discovery architectures.%12 Possible cause: SQL Server problem. Solution: 1. Review ...