
The following example shows a successful connection to a local SQL Server.
The following are common troubleshooting steps:
1. For remote SQL Server databases on versions of HP Web Jetadmin prior to 10.3 SR3, a license
must be installed in HP Web Jetadmin (see Appendix A). Even though the license might have
been installed previously, the license might need to be reinstalled after HP Web Jetadmin is
upgraded to a new version. It is also possible that although License Manager indicates that the
license is installed, HP Web Jetadmin is not recognizing the license. A more reliable method for
making sure that the license is installed is to go to Help > About > Details in HP Web Jetadmin.
Remember to restart the HP Web Jetadmin service after the license is installed.
2. If name resolution issues occur, fully qualify the server name in the configuration file or use the IP
address instead of the hostname.
3. If the user password was edited in the configuration because it changed, remember to change the
heading back to PlainTextPassword for that section.
4. Use SQL Server Configuration Manager to confirm that TCP/IP is enabled on the remote SQL
server.
5. Check the firewall settings to make sure that the port used for the remote connection is open. The
default port is 1433, but this port can be changed as described later in this document.
6. SQL Server 2008 R2 defaults to using a dynamic port. Either configure SQL Server to use a fixed
port or start the SQL Browser service to allow for remote connections.
7. Confirm that the user HP Web Jetadmin is using to connect to the database has at minimum (or
read/write/execute at a minimum, see the Database rights section) rights (DBO rights are
preferred) on the database. An excellent technique to test that the user login is correct is to use
SQL Server Management Studio to log in to the instance. If the same credentials entered in the
DatabaseSettings.config.xml file cannot successfully log in to the instance through SQL Server
Management Studio, HP Web Jetadmin will have the same problems. One of the following
command-line utilities can also be used to determine if the login is correct:
osql -U(user name) -P(password) -S(server name\instance)
sqlcmd -U myName -P myPassword -S theServerName\instance
If the login succeeds, confirm that the login has the correct rights on the HP Web Jetadmin
database.
Commenti su questo manuale