Troubleshooting, Some reasons why a test might fail, Table 5-1 – HP NonStop G-Series User Manual

Page 63

Advertising
background image

Select Services to display the Services window.

5.

Select the package and the service that requires editing and select Edit.

6.

Edit the service.

7.

Save the service and then go to

Step 4

in the previous list.

8.

Some Reasons Why a Test Might Fail

Here are some reasons why a service test might fail and possible solutions.

If this . . .

Do this . . .

A parameter is incorrect. Edit the service.

The Jolt server is down.

Check the server. The TUXEDO service is down. You do not need to edit the service.

Troubleshooting

If you encounter problems while using the Repository Editor, see

Table 5-1

.

Table 5-1. Repository Editor Troubleshooting Table

If . . .

Then . . .

You receive any error

Make sure the browser you are running is Java-enabled:

For Netscape browsers, look under the Options menu,
there should be a choice for Show Java Console. If this
does not exist, the browser probably does not support
Java.

For Internet Explorer, make sure the version is 3.0 (or
later).

If running Netscape Navigator, check the Java Console
for error messages.

If running appletviewer, check the system console (or the
window where you started the appletviewer).

You cannot connect to the
Jolt Server (after entering
Server and Port Number)

Check and make sure that:

Your Server name is correct (and accessible from your
machine). Check that the port number is the correct port.
There must be a JSL or JRLY configured to listen on that
port.

The Jolt server is up and running. If any authentication is
enabled, check that you are entering the correct user
names and passwords.

If the applet was loaded via http, the Web server, JRLY
and the Jolt server must be on the same machine (i.e., the
Server name entered into the Repository Editor must be
the same machine as the one used in the URL to
download the applet).

Advertising