The following error occurs when logging on to the LANDesk 32 bit Remote Console:
The LANDesk 32 bit Console on the Core Server is usually functional and the web console is usually functional as well when this error is occurring.
The remote console uses the value stored in the Core's Registry to access the database.
Look under the String called Server under this registry key:
It may be possible that this is an FQDN, a hostname, or an IP Address. If the value is FQDN or hostname, name resolution must be working and properly returning and IP Address. The IP Address must be accessible. If not, this error will occur.
The remote console machine also needs to be able to resolve the database server name (or whatever value is in the database connection string) to an IP address. Look under the String called Server under this registry key:
HKLM\Software\LANDesk\ManagementSuite\Core\Connections\Local String: ServerName Value: (Will be FQDN, Hostname, or IP)
Ensure the machine running the remote console can contact the database server directly over the appropriate ports using the name from the registry key in the previous step. Test accessibility using ping and telnet to the SQL port (1433).
ping SqlServer telnet SqlServer 1433 ping SqlServer.Domain.tld telnet SqlServer 1433 ping 10.1.1.1 telnet 10.1.1.1 1433
Note: If DNS is not working, update the hosts file temporarily for testing until DNS can be configured properly.
Check for any firewalls or IPSec or other rules that could be blocking the ports. The firewall is commonly enabled on the CoreServer.
If the Server is SQL 2005, verify that it has been properly configured. Under the SQL Server 2005 Network Configuration section confirm that both Named Pipes and TCP/IP is enabled. Under the properties of TCP/IP verify that an enabled IP address exists.
If the client has MSDE installed they may have a problem with the instance name. Because the Console was defaulting to the SQL DB instead of the MSDE instance, the console wont connect. To fix the issue create a system DSN that points to the coreservername\ldmsdata instance.
If users can't connect to port 1433 then they may need to create a System DSN. In the configuration settings for the DSN they can manually configure the port that is used by SQL. Doing this will point the SQL client to the new port.Note: The web console does not need to contact the database server directly.
Creating a System DSN to point to a non-standard SQL port
1. Go to Start --> Control Panel, double-click Administrative Tools, then double-click Data Sources (ODBC).
2. Click the System DSN tab, and then click Add.
3. Select "SQL Server" and click "Finish"
4. Give the Data Source a descriptive name.
5. Describe the data source.
6. Enter the Netbios Name, FQDN, or IP address of the core server, depending on your environment requirements, and click Next.
7. (If a different port is being used other than 1433, click "Client Configuration", uncheck "Dynamically determine port", and then enter in the desired port number.
8. Enter SQL credentials to connect to the database.
- Ensure SQL Server is configured to allow remote connections. The following Microsoft Knowledgebase Article details this process: http://support.microsoft.com/kb/914277
- Database corruption can cause issues with database connection and/or essential database services starting properly.http://support.microsoft.com/kb/914277
For LDMS 9.5
- Go to Start > All Programs > Microsoft SQL Server 2008 R2 > Configuration Tools
- Select the SQL Server Configuration Manager
- Click on the SQL Server Services
- In the right pane, look for the SQL Server Browser
- This service must be running
- If the service shows Disabled, do the following:
- Right click on the service, select Properties
- Click on the Service tab
- Look for the Start Mode, click on the Disabled, a drop down will appear with options, select the Automatic
- Select Apply, OK
- Next right click on the service again, and select Start
For general information regarding the error "SQL Server does not exist or access denied" error message, see the following Microsoft Knowledgebase article: