HP Web Jetadmin - Using Microsoft SQL Server with HP Web Jetadmin
16
instance name is correct and that SQL Server is configured to allow remote connections.
(provider: SQL Network Interfaces, error: 28 - Server doesn't support requested protocol)
wrong server name - Could not connect to the database, Message: A network-related or
instance-specific error occurred while establishing a connection to SQL Server. The server
was not found or was not accessible. Verify that the instance name is correct and that
SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces,
error: 26 - Error Locating Server/Instance Specified)
wrong instance name - Could not connect to the database, Message: A network-related
or instance-specific error occurred while establishing a connection to SQL Server. The
server was not found or was not accessible. Verify that the instance name is correct and
that SQL Server is configured to allow remote connections. (provider: SQL Network
Interfaces, error: 26 - Error Locating Server/Instance Specified)
wrong catalog (database) name - Could not connect to the database, Message: Cannot
open database "hpwja2" requested by the login. The login failed., Login failed for user
'jimesf'.
wrong user name/password - Could not connect to the database, Message: Login failed
for user 'jimesf2'. (notice how user name is wrong)
no license installed (for versions of Web Jetadmin prior to 10.3 SR3) - Could not connect
to the database, Message: Login failed for user 'jimesf'. (notice how user name is correct)
Another technique for displaying connection status is to add /instrumentable at the end of URL
used to launch Web Jetadmin from a browser. Click DatabaseManager to view connection
status.
An example of a case where a TCP/IP connection could not be made to the remote SQL Server
would appear as such:
A successful connection to a remote SQL Server is shown below. Notice that Integrated Security is
true in this case meaning Windows Authentication was used for the Windows machine account.