Error: 'SQL Server does not exist or access denied.' (NETIQKB31946)

fact
VigilEnt Security Manager 2.2

fact
VigilEnt Security Manager 4.1

fact
VigilEnt Security Manager 2.3

fact
VigilEnt Security Manager 2.3 SR1

fact
VigilEnt Security Manager 2.3 SR2

fact
VigilEnt Security Manager 2.3 SR3

fact
VigilEnt Security Manager 3.0

fact
VigilEnt Security Manager 3.0 SR1

fact
VigilEnt Security Manager 3.0 SR2

fact
VigilEnt Security Manager 4.0

symptom
Error: 'SQL Server does not exist or access denied.'

symptom
SQL Server error occurs when logging into VigilEnt Security Manager.

symptom
The following error occurs when logging into VigilEnt Security Manager from a remote GUI:

Unable to connect to server xxxx
Server: Msg 17, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exist or access denied.

symptom
Logging into VigilEnt Security Manager from a local GUI does not produce this error.

cause
The machine that the VigilEnt Security Manager GUI is installed on cannot connect to the database server, because different protocols are being used.

fix
Many times configuring the GUI machine to use a different protocol (TCP/IP or multi-protocol) will resolve the problem.

1. Open Client Network Utility, which can be found in Start | Programs | Microsoft SQL Server.

2. Switch to the Alias tab.

3. Click Add.

4. Enter the name of the server or workstation where the Microsoft SQL Server is hosting the VigilEnt Security Manager database.

5. Select the Multiprotocol radio button.

6. Click OK.

7. Close the utility.

note
There are two options for getting the "Client Network Utility":

• Using Microsoft SQL Server installation media, install just client tools on the target system.

• If Microsoft SQL Server is not installed on the host, go to a system where Microsoft SQL Server is installed and copy the files to a floppy disk. Search in [boot drive]:\Winnt\System32 for all files with the pattern "cliconf*.*".

Formerly known as NETIQKB31946