What may cause the BMC Client Management agent service to not remain started and prevent from being able to login to the Console?

How do I perform a UDL test to check the SQL Server database connection?

Check the mtxagent.log file on the Master server - typically located in C:\Program Files\BMC Software\Client Management\Master\log
Search for ERR and check if there are any errors listed below
 
2022/12/14 02:33:00 Vision64Database                ERR [2608] Failed to connect to odbcdirect using (<Hostname>\SQLEXPRESS, Driver={ODBC Driver 17 for SQL Server};Server=<Hostname>\SQLEXPRESS;Database=bcmdb;Uid=bcmdbuser;), Error:
2022/12/14 02:33:00 Vision64Database                I   [2608] Trying to close connection: 24048897ae0
2022/12/14 02:33:00 Vision64Database                I   [2608] Closed connection successfully: 24048897ae0
2022/12/14 02:33:00 Vision64Database                ERR [2608] Failed to identify database syntax (connection allocation error)
2022/12/14 02:33:00 Vision64Database                ERR [2608] Database not identified. End program. Please verify parameters.
2022/12/14 02:33:00 AgentModules                    ERR [2608] Initialisation failed for Vision64Database
2022/12/14 02:33:00 AgentInit                       I   [2608] Starting cleanup, reason code 2
2022/12/14 02:33:00 AgentCore                       ERR [2608] received logoff event without previous logon
 
Make sure that the database server is up and running, the database instance service is running, and able to login to SQL Server Management Studio and view the database using the 'bcmdbuser' or 'facdbuser' credentials.  
 
Here is an alternate method to test the ODBC connection from the master server.
 
1) Create a new text document on the Desktop of the Master server that cannot connect to the Client Management database server, and change the name of the file to 'TEST.udl'.

This will create a Microsoft Data Link Properties connection tool that uses the same components that BCM uses when attempting to connect to the database.
 
Note: Make sure that the extensions option is enabled in the file explorer settings on the master server or else the file will only be renamed to TEST.udl.txt and will appear to simply be text file.
 
2) Double-click the file to run it.
 
3) In the 'Provider' tab, make sure that 'Microsoft OLE DB Provider for SQL Server' is selected.


4) Click on 'Connection' tab.
 
5) In the 'Select or enter a server name': field enter the same server name\instance name value that appears in the Vision64database.ini on the Master server.
 
6) In the 'User name': field enter the name of the user that appears in the Vision64databas.ini (..\Master\Config\Vision64Database.ini)


7) In the 'Password': field enter the default password for bcmdbuser.
 
8) Open the 'Select the database on the server': drop down field.


9) If successful, the client management DB can be selected. If not, it is confirmed that the client cannot connect to the SQL server and other things must be checked (I.e. Windows Firewall on the SQL server, SQL Server configuration, etc.) to make sure the clients are allowed to connect to SQL server. Involve the DBA to fix the SQL server connectivity issue.
 
10) If the connection is allowed then select the database name from the drop down list, click the 'Test Connection' button to verify connectivity.


11) If the 'Test Connection' returns the below message, then it is because TLS 1.2 is enabled on the server and the default ODBCDirect driver is unable to handle the connection.
 
---------------------------
Microsoft Data Link Error
---------------------------
[DBNETLIB][ConnectionOpen (SECCreateCredentials()).]SSL Security error.
---------------------------
OK  
---------------------------
 
In order to fix this issue, Microsoft ODBC Driver 17 needs to be installed on the BCM master server and this driver supports TLS 1.2 connection. Below knowledge article has detailed steps about installing the drivers and updating BCM configuration files to successfully connect to DB.
Client Management: I forced TLS 1.2 communication on my server but then BCM can not communicate with the SQL Server Database