Error "Unable to establish a connection to the Altiris DB Management service"
Last Updated May 04, 2006
Make sure that the Altiris Deployment Server DB Management service is actually running. This can be done from the Service Control manager in Windows. After the service is running, try opening the DS console. If it fails then move on to solution 2.
If the Altiris Deployment Server DB Management service is running, stop it. The mmsettings table can now be edited. Delete all entries in the mmsettings table. If you are using Microsoft SQL, use Enterprise Manager to delete all entries from the mmsettings table in the eXpress database. If you are using MSDE* then run following lines from a command prompt: C:\Program Files\Microsoft SQL Server\80\Tools\Binn
osql –E 1>use express 2>delete from mmsettings 3>go
If you are not logged on as a user with SQL SA rights, you will need to replace the first line in the example above with:
osql -U sa
Start the Altiris Deployment Server DB Management service. The Altiris Deployment Server DB Management service should "register" itself with the SQL database when it started. Stopping and then restarting the service should properly update the mmsettings table with the correct mm_id, address, port, and hostname. Once a valid entry is in the mmsettings database the console will be able to start and connect to the DB manager. From a command prompt, you can verify the content of the mmsettings table by typing the following query (this assumes you are logged on as a user with SQL rights on the SQL computer):
osql -E 1. Use express. 2. Select * from mmsettings. 3. Go.
If you are not logged on as a user with SQL right you will need to replace the first line in the example above with:
osql -U sa
The results should return only one row and the information should reflect the correct IP address and name of the computer running the DB management service.
It is required that the Altiris eXpress Server service and Altiris Deployment Server DB Management service are running as a user that has DBO rights to the eXpress database. Check to ensure that the account that the Altiris Deployment Server DB Management service is running as has DBO rights to the eXpress database.
To do verify the rights go in to the SQL Server Enterprise Manager. (Note: This program only comes with full SQL and not MSDE). Drill down to Console Root > Microsoft SQL Servers > SQL Server Group > (SQL server w/ express database) > Security > Logins. In the right-hand pane, you will see a list of logins there. Specifically add the user that you are running the Altiris Deployment Server DB Management service as to that list by following these steps:
Right-click in the right-hand pane and select New Login.
Type in the username or browse for it using the Browse button next to the name field.
Note: You must enter the specific username, and not just a windows group that the user is part of.
Ensure that the Authentication on the General tab is set to grant access.
Click on the Database Access tab.
Check the Permit check box for the eXpress database. With the eXpress database selected, make sure the public and db_owner roles are checked in the Database roles for express window below.
For more details on adding new users in SQL, search for New SQL Login under the SQL help index.
Another requirement of the Altiris Deployment Server DB Management service login is that it has administrative rights on the SQL machine as well as the machine it is running on. Check the Windows authentication on both the SQL machine and the machine running the Altiris Deployment Server DB Management service.
Make sure that the Altiris Deployment Server DB Management service has rights to run as a service. To do this go to the local security settings on the machine running the service by typing Secpol.msc in the run command. Drill down to Local Policies > User Rights Assignment and double-click on the Log on as a service policy. If the user is not listed then add the specific user and check the checkbox under Local Policy Setting. Note that if domain-level policy settings are defined, they override local policy settings. It is uncommon for this policy to be restricted at the domain level; however, you may need to check the security settings under the domain controller.
Check any firewalls and ensure that there is nothing blocking traffic on the designated port. The default communication port for the DB Manager is TCP 505. This port is also listed in the mmsettings table.
Reinstall the Deployment Server over the top of the existing Deployment Server by running C://DSSetup/axinstall.exe. Open the Deployment Server console and verify it is running correctly.
Verify the MMsettings table in the SQL database has a single entry and that the information is correct. Note: Only the top entry is used by the Altiris Deployment Server DB Management service (middle man).
Other possible resolutions:
Create a new ODBC connection for Altiris eXpress Database and restart the Altiris DB Management service.
Give one of the VM NICs valid IP/subnet/gateway/DNS information. Restart the DB Management Service. The service should successfully start and write corresponding information into the mmsettings table. Relaunch the console, and it should load without errors.
Change the DS services with Domain Admin account.
See also article 22609, "Security issues with the Deployment Server database."
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe