CCA-AG-5718: Agent unable to establish a database connection for blueprint and/or CCA-DIS-8579: Failed to connect to remote database during discovery of the component blueprint "Microsoft SQL Server {version}" on server
Article ID: 132331
Updated On:
Products
CA Configuration Automation
CENDURA
Issue/Introduction
In CCA, when attempting to discover the SQL Server using the MS SQL Server blueprint, you may encounter one (or more) of the following errors:
- CCA-AG-5718: Agent unable to establish a database connection for blueprint
- CCA-DIS-8579: Failed to connect to remote database during discovery of the component blueprint "Microsoft SQL Server {version}" on server
- CCA-AG-5710: Agent unable to establish a database connection. Invalid username or password, logon denied
Environment
Configuration Automation - All versions
Resolution
The database blueprint discovered the installed application and its configuration files, but not the database data.
The blueprint does 2 things:
1 - Attempts to find the application and its installed path and from there gather configuration information (by files or commands)
2 - Attempts to connect to the database itself using the specified credentials in the blueprint
Now, the best practice for this is NOT to put the username and password in the blueprint; you want to keep it standard. What you would do is discover the blueprint (as it seems you did), then go into that server(s) --> components, and select that discovered blueprint. Within there, you can go to "Component Parameters and Variables" --> "User Input" and fill out the username\password here
From here, in the components screen, checkbox that component and do "Select Actions" --> Run Discover. The rediscover should pick up the actual database data
This allows for each server to have a specific credential (incase each database instance has a different set of user\pass) and keeps the blueprint generic. The only time to modify the original blueprint is if every single database login uses the same username and pass. If the later, then no need to run a rediscovery in components, the OOTB with User\Pass should work
The blueprint does 2 things:
1 - Attempts to find the application and its installed path and from there gather configuration information (by files or commands)
2 - Attempts to connect to the database itself using the specified credentials in the blueprint
Now, the best practice for this is NOT to put the username and password in the blueprint; you want to keep it standard. What you would do is discover the blueprint (as it seems you did), then go into that server(s) --> components, and select that discovered blueprint. Within there, you can go to "Component Parameters and Variables" --> "User Input" and fill out the username\password here
From here, in the components screen, checkbox that component and do "Select Actions" --> Run Discover. The rediscover should pick up the actual database data
This allows for each server to have a specific credential (incase each database instance has a different set of user\pass) and keeps the blueprint generic. The only time to modify the original blueprint is if every single database login uses the same username and pass. If the later, then no need to run a rediscovery in components, the OOTB with User\Pass should work
Feedback
Yes
No
Powered by
