Troubleshooting

This section describes solutions to some problems that you can encounter when using the Web Console.

Unable to Access Service Registry

If you receive either an Error 404 or a “Connection refused” message when you try to use the Web Console, it is likely either that the Registry is not running or that you specified an incorrect URL.

Make sure that you specify http://hostname:6060/soar/. You might need to specify the domain in addition to the hostname: hostname.domain.

To make sure that the Registry is running, use the command-line or web interface to the Application Server domain for the Registry. For details, see Administering the Application Server Domain for Service Registry in Service Registry 3 2005Q4 Administration Guide.

Preferred Locale Is Not Used

If the Web Console is not using your preferred locale, check your web browser preference settings. Make sure the preferred locale is at the top of the list of locales. See Changing the Default Language for details.

Search Panel Labels Do Not Appear in Current Locale

If the Search Panel labels do not appear in the current locale after you change the locale and click Reset Locale, click End Session, then Return to Registry. See Changing the Default Language for information on changing the locale.

Unable to Create ExternalLink or ServiceBinding

You might get an error in one of the following situations:

• When you specify an ExternalURI for an ExternalLink object

• When you specify an AccessURI for a ServiceBinding object

The error message looks like this:

The URL: uri is not resolvable. 
Use Absolute Path Format [scheme:][//authority][path][?query][#fragment]

This error means that the administrative task described in Allowing Access to External Web Sites in Service Registry 3 2005Q4 Administration Guide has not been performed. The Service Registry administrator for your site needs to perform this task and restart the Registry before you can create these objects.

Web Console Error Messages Are Not Clear

For clarification of the problem that is causing a Web Console error message, examine the server log for the Application Server domain for the registry. For details, see Administering the Application Server Domain for Service Registry in Service Registry 3 2005Q4 Administration Guide.

New Registry Object Cannot Be Saved

If you get an error message when you try to save a new object in the Registry:

• If you are using a Registry-generated certificate, make sure that you imported the certificate into your web browser.

• If you are using a third-party certificate, make sure your administrator placed the Certificate Authority root certificate in the truststore of the Application Server domain for the Registry. For details, see To Add Root Certificates to the Trusted Certificates in the Registry Domain in Service Registry 3 2005Q4 Administration Guide.

Web Console is Unresponsive

If the Registry Console becomes unresponsive, perform the following steps:

1. Make a note of the error messages that appear.

2. Clear the session cookie in your web browser. To clear the cookie, find the cookie with the name JSESSIONID at the site where the Registry is running and remove it. If you are unsure, delete all cookies.

3. Restart the Web Console as described in Starting the Web Console.

4. Contact Registry Support and inform them of the error messages and of the steps that led to the error.