Review the following solutions and try them in the order most applicable to your environment.
1) Go to Start > Settings > Control Panel > Admin Tools > Data Sources ODBC > System DSN tab.
2) Highlight the Altiris eXpress Database source. Click on 'Configure'
a.) On the first configuration page verify the name of the SQL server in the Server drop down menu. This should be the name of the machine that has SQL installed with the eXpress database.
b) Click Next and verify that the authentication method is correct. Windows NT is the most common authentication method used.
c) Click next again. Verify that the name of the default database is set to 'express'. (DS 6.5 allows the database name to be changed during install. Use the approriate name) Ensure that the check boxes for "Use ANSI quoted identifiers" and "Use ANSI nulls, paddings, and warnings" are checked.
d) Click next again and then click finish. Select "Test Data Source". If the test fails because of an authentication problem, you do not have DBO rights to the eXpress database (see Cause 3).
If you are still unable to connect resulting in the same error message, it could be that the server is unable to resolve using named pipes or TCP/IP. Try switching from one to the other in the client configuration. These options can be found in the "Client Configuration" button on the 2nd page of the wizard. If this does not help the first time then try one of the other suggested solutions, and try toggling between TCP/IP and Named Pipes again.
DS 5.6 only- Deployment server requires that the user that is opening the console have administrative rights on both the local machine and the machine running the Deployment Server services. Verify that the user has these permissions on both the Deployment Server and on the Remote Console machine (if applicable). Also verify that the NT account has not expired on the Deployment Server machine or in the domain. If the user is a domain user, add that specific user account to the local administrators group on both the Remote Console Machine and the Deployment.
DS 6.0 and above- in the .\deployment server\techsup directory is a utility called 'DSDBsecurity'. Double click on this executable, authenticate and select 'Set Role Permissions' This utility gives all users who are member of the Public group within SQL rights to open up and use the console.
5.6 Only- Verify that the user has DBO rights to the eXpress database. Note that if the user has anything less then DBO rights to the eXpress database, a connection is possible, however any specific stored procedures CANNOT be accessed by an account that does not have DBO rights, and your database will become corrupted.
Verify the user account permissions through SQL Server Enterprise Manager (Note: This program only comes with full SQL Server and is not included 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. Sometimes SQL cannot get a full list of users from a Windows user group (i.e. BUILTIN\Administrators).
Add the specific user you are logged in as then try to run the console. To add the user follow these steps:
1) Right click in the right hand pane and select new login.
2) Enter or browse for the username. Note that you must enter the specific user name and not a Windows group that the user is part of.
3) Ensure that the authentication on the general tab is set to grant access.
4) Click on the Database Access tab
5) Check the permit check box for the eXpress database
6) With the eXpress database selected, verify that the public and db_owner roles are checked in the Database roles for eXpress window below.
7) Click OK.
Fore more details on adding new users in SQL, search for "New SQL Login" under the SQL help index. If there are still problems with authenticating to SQL and accessing the eXpress database check the Windows event viewer logs and SQL error logs. Using SQL profiler can also be a helpful tool to trace authentication attempts to the database.
DS 6.0 and above- make sure the user is a member of the public group on the SQL server. Run DSDBsecurity.
Check any firewalls between the machine running the Altiris eXpress Server service and the machine opening the console. Firewalls and proxy servers can be the cause of some Remote Consoles not opening while other Remote Consoles and the Main DS console CAN be opened
If the Remote Console is going through a firewall then go back into the "Client Configuration" settings in the Altiris eXpress Database ODBC System DSN (as described in Solution A).
Uncheck the "Dynamically Determine Port" and specify a specific port for the console to communicate on.
There are several reasons that SQL could fail. Whenever SQL does fail it is a good idea to first check the windows event viewer logs and the SQL error logs. Often times SQL will fail because of a transaction log growing too large, this is largely due to the high number of transactions Deployment Server has with the database. To prevent this by set the recovery model on the eXpress database to simple or add a maintenance plan to backup the eXpress database nightly. For more information search for "database recommendations" in the Altiris Support Knowledge base and review the SQL user guide.