Troubleshooting

Table 9-3 lists some common problems and solutions encountered when configuring EAServer to run in FIPS mode using TLS.

Table 9-3: Common FIPs and TLS problems

Problem or symptom

Possible cause or solution

EAServer does not start and displays this error message on the console:

Certicom Security Builder GSE not installed.
Please refer to EAServer troubleshooting guide.
Failed to load library: d:\52\EAServer\dll\defaultmem, reason: The specified module could not be found.   [126]
Failed to locate library in the following search path: [.;D:\52\EAServer\jdk\jdk1.3.1_06\bin;D:\52\EAServer\cpplib;D:\52\EAServer\jdk\jdk1.3.1_06\jre\bin;

This indicates the Certicom installation failed. Verify that the EAServer installation program ran successfully. Also verify the Certicom Registry key is configured correctly. Use the regedit Windows utility to view registry entries.

EAServer starts, but displays this error message on the console:

Certicom Security Builder GSE not installed.
Please refer to EAServer troubleshooting guide.
Failed to load library: d:\52\EAServer\dll\defaultmem, reason: The specified module could not be found.   [126]
Failed to locate library in the following search path:
[.;D:\52\EAServer\jdk\jdk1.3.1_06\bin;D:\52\EAServer\cpplib;D:\52\EAServer\jdk\

This indicates that the defaultmem.dll file cannot be located. This file is part of the EAServer installation and must be in %JAGUAR%\dll\defaultmem.dll.

A dialog box displays this message:

The procedure entry point sb_memcpy could not be located in the dynamic link librarydefaultmem.dll

and this error message displays on the console:

Sybase, Inc. One Sybase Drive, Dublin, CA 94568 USA. 
Failed to load library: d:\52\EASErver\dll\libjctssecsrv_f140, reason: The specified module could not be found [126]
Failed to locate library in the following search path:
[.;D:\52\EAServer\jdk\jdk1.3.1_06\bin;D:\52\EAServer\cpplib;D:\52\EAServer\jdk\jdk1.3.1_06\jre\bin

Verify that %JAGUAR%\dll\defaultmem.dll is installed from the EAServer installation. View the file properties using the File Explorer. The version and author string should contain “Sybase”.

EAServer starts, but freezes while starting, or takes a long time to start.

The random seeding may be taking longer than normal. Set the JAGUAR_RANDOMSEED variable. See Chapter 3, “Creating and Configuring Servers,” in the EAServer System Administration Guide.

The EAServer listener is set to sybpks_domestic, but the Web browser cannot connect to a secure port on EAServer.

Check the following:

  • Refer to the server log file to determine if the secure listener is active or not.

  • Ensure that the server certificate is valid and has not expired.

  • Ensure that the host/port settings are valid. The port should not be use in by another application. The most common reason for this is that another instance of EAServer is running.

The EAServer listener is set to sybpks_domestic_tls, but the Web browser cannot connect.

All security profiles that end with tls and the sypbks_tls_xxx security profiles accept only TLS.

Verify that your Web browser is configured to handle TLS. By default, most browsers disable TLS.

See the Web browser documentation for instructions on how to configure the settings for your browser.

The EAServer secure protocol listeners configured with sybpks_domestic, sybpks_intl, and sybpks_simple do not start.

Verify that the EAServer certificate is valid and has not expired.If FIPS 140-2 mode is enabled in EAServer, then only a subset of the security profiles are valid. sybpks_domestic, sybpks_intl, and so on are disabled. See Table 9-2 for a list of FIPS supported cipher suites.When FIPS is enabled, a message displays on the console. The FIPS setting can be determined using EAServer Manager or the getfipsmode jagtool command.