Install-Panther WebSphere


Appendix G . Error Messages


Panther Installation Error Messages

A Panther installation was not successful if you receive an error message and the program terminates. The following messages describe some of the more common error messages and how to resolve them.

Recurring errors: Occasionally, errors described in this section seem to recur even though the file smvars is in order. More often than not, the problem is that the smvars file (in the config directory), although correct, has not been converted to binary (smvars.bin), which is the required format used by Panther. If the ASCII version of smvars has been edited, be sure to run var2bin to convert it to binary format. Otherwise Panther is not aware of the changes, and it will seem as though smvars was not updated.

Please enter terminal type or <RETURN> to exit.

Cause:
SMTERM is not set (and, under UNIX, TERM is also not set) or the value could not be found in smvars.bin (left column of smvars).

Action:
Enter the terminal type if known or press Enter to set SMTERM correctly. Once the variable is defined, run prodev again.

See the left column of the smvars file and correct the specification. Use var2bin to convert the file to binary. And/Or:

UNIX: Set the variable at the command line.

Windows: Set the variable to mswin in prol5w32.ini or prol5w64.ini.

If you are running in character mode and the screen appears disorganized, with all the text bunched together along with special characters, check the value of SMTERM; you probably only need to change its value, but you may also need to create a new video file.

Filename: No such file or directory

Cause:
The filename in brackets is specified as the value of the SMVIDEO, SMKEY, SMMSGS, or some similar configuration variable in the environment or in smvars.bin, but the file could not be found.

Action:
Correct the name, and use the full pathname of the file. If you correct it in smvars, recompile smvars with the var2bin utility.
SMMSGS: Environment variable missing

Cause:
(or the same message with some other configuration variable). Panther could not find an entry for the cited variable in SMVARS or in the environment (refer to the following note). This error usually means that you have some variables defined in your environment, but not all that are required, and SMVARS is not defined.

Note: Most Panther setup variables can be set in the environment, rather than depending on values set in an SMVARS-defined file. If Panther can't find a required variable specification in either the environment or in the SMVARS file, that variable will be cited as missing. Refer to the Configuration Guide for more details.

SMVARS: Bad file format

Cause:
SMVARS is set to be the name of an existing file, but it is not a binary SMVARS file. The most common incorrect value for SMVARS in this case is the path and name of the source SMVARS file instead of the binary SMVARS file.

Action:
Point to the binary file that has the .bin extension.
SMVARS: Environment variable missing

Cause:
SMBASE (or SMVARS, if you are using one) is not set, or not set properly. Normally, Panther looks for smvars.bin in the config directory under the directory pointed to by SMBASE. If SMBASE is not set, you must have an SMVARS variable to tell Panther explicitly where the SMVARS file can be found. If SMBASE is not set property, and Panther cannot find an SMVARS variable, the above message is given.

Action:
Correct (or set) the SMBASE variable specification, or determine why setting it is not taking effect.

Windows: Check to see that SMBASE is being set in autoexec.bat and that you have not run out of environment space.

UNIX: Make sure that the variable is exported (via the export sh/ksh command or setenv csh command).

SMVARS: No such file or directory

Cause:
SMVARS is not set correctly.

Action:
Check that the full pathname (including drive letter under Windows) of the file is included and correct.

DLL Messages

The following error messages might occur after a Windows installation and are specific to DLLs required for Panther's database drivers and to DLL version mismatches.

Oracle Tuxedo-Specific Messages

Cannot find LIBWSC.DLL

Cause:
Windows is unable to find the Oracle TUXEDO DLLs.

Action:
Check that Oracle Tuxedo is present and configured properly.

Informix-Specific Messages

Cannot load DLL INF7DM32.DLL
Cannot load DLL INF7DMNT.DLL
Cannot load DLL INF7DMN4.DLL
Cannot load DLL INF9DMN4.DLL
Cannot load DLL TMINF132.DLL

Cause:
Windows is unable to find the Panther database driver DLLs or the Informix software.

Action:
Check that the Panther util directory is on the PATH. If you do not wish to use the Panther database driver DLLs, edit PROL5W32.INI to remove the database name from the install entry.

Microsoft SQL Server-Specific Messages

Cannot load DLL mssdm32.dll
Cannot load DLL tmmss132.dll

Cause:
Windows is unable to find the Panther database driver DLLs or the Microsoft SQL Server software.

Action:
Check that the Panther util directory is on the PATH. If you do not wish to use the Panther database driver DLLs, edit PROL5W32.INI to remove the database name from the install entry.

ODBC-Specific Messages

Cannot load DLL odb2dm32.dll
Cannot load DLL odb3dm32.dll
Cannot load DLL tmodb132.dll

Cause:
Windows is unable to find the Panther database driver DLLs or the ODBC software.

Action:
Check that the Panther util directory is on the PATH. If you do not wish to use the Panther database driver DLLs, edit PROL5W32.INI to remove the database name from the install entry.

Oracle-Specific Messages

Cannot load DLL ora815dm32.dll
Cannot load DLL emb815dm32.dll
Cannot load DLL oxa815dm32.dll
Cannot load DLL exa815dm32.dll
Cannot load DLL ora9dm32.dll
Cannot load DLL emb9dm32.dll
Cannot load DLL oxa9dm32.dll
Cannot load DLL exa89m32.dll
Cannot load DLL tmora132.dll

Cause:
Windows is unable to find the Panther database driver DLLs or the Oracle software.

Action:
Check that the Panther util directory is on the PATH. Verify that Oracle is installed correctly. If you do not wish to use the Panther database driver DLLs, edit PROL5W32.INI to remove the database name from the install entry.

Sybase-Specific Messages

Cannot load DLL db10dm32.dll
Cannot load DLL ct10dm32.dll
Cannot load DLL db11dm32.dll
Cannot load DLL ct11dm32.dll
Cannot load DLL tmsyb132.dll

Cause:
Windows is unable to find the Panther database driver DLLs or the Sybase software.

Action:
Check that the Panther util directory is on the PATH. If you do not wish to use the Panther database driver DLLs, edit PROL5W32.INI to remove the database name from the install entry.

DLL Version Mismatch Messages

Application Error: Call to Undefined Dynalink

Cause:
Panther is picking up an older version of cktbl32.dll from a previous installation.

Action:
Check that the current Panther util directory with the correct cktbl32.dll is on the PATH or copy cktbl32.dll to the Windows directory.

Graph-Related Messages

If graph widgets are not displaying correctly, the following graph-specific errors might be displayed;

Warning: chart <Begin> failed: -1

Cause:
All graphs are blank indicating that the gdsp program (in the util directory) was not found on the path. (UNIX only.)
Warning: missing graph files in $SMPATH

Cause:
All graphs are blank indicating that: the grafcap file is invalid or not found in SMPATH (UNIX) and the IPT setting in the file LIBSTI.INI does not point to the directory that contains the grafcap file (Windows).

License Manager Error Messages

In most circumstances, Panther license management is transparent to the developer. This section describes the error messages that can be generated from Panther and from the underlying license manager software, FLEXlm.

Panther License-Related Messages

The messages described in this section can appear when the screen editor is invoked.

All License Types

Prolifics License Manager: Bad date in license file.

Cause:
The date on one of the FEATURE or INCREMENT lines is not correct.

Action:
Verify that the FEATURE and INCREMENT lines in the license file are correct or contact your system administrator.
Prolifics License Manager: Bad encryption code in license file.

Cause:
The password on one of the FEATURE or INCREMENT lines is not correct.

Action:
Verify that the FEATURE and INCREMENT lines in the license file are correct and that none of the backspaces indicating continued lines are followed by a space, or contact your system administrator.
Prolifics License Manager: Cannot communicate with server. cannot connect to license server ([code,code])

Cause:
Could not connect with the license server.

Action:
Make sure the license server daemon lmgrd is started on the system specified in the SERVER line of the license file, or contact your system administrator. The two codes can help locate the problem.
Prolifics License Manager: Cannot connect daemon prold with license server.

Cause:
There is no DAEMON line in the license file for prold.

Action:
Verify that the license file entry is correct or contact your system administrator.
Prolifics License Manager: Cannot find license file.

Cause:
The license manager is unable to find the license file.

Action:
Make sure LM_LICENSE_FILE in your initialization file or environment points to the correct license file and that it is readable.
Prolifics License Manager: Cannot read license file

Cause:
The license manager could not read the license file because of a permissions or access problem.

Action:
Correct the problem or contact your system administrator.
Prolifics License Manager: ERROR #[code] , [message]

Cause:
An unexpected error occurred in the license manager.

Action:
Contact your system administrator.
Prolifics License Manager: [product] feature does not exist.

Cause:
There is no FEATURE or INCREMENT line in the license file for [product].

Action:
Verify that the FEATURE or INCREMENT lines in the license file are correct, obtain a new license file, or contact your system administrator.
Prolifics License Manager: Feature [product], Version [version] has expired.

Cause:
The expiration date in the license file of [product] has been reached.

Action:
Obtain a new license file or contact your system administrator.
Prolifics License Manager: Initialization failed.

Cause:
Problems in the license file.

Action:
Contact your system administrator.
Prolifics License Manager: Invalid data received from license server.

Cause:
The license server did not respond to a request or the response was invalid.

Action:
Contact your system administrator.
Prolifics License Manager: Invalid license file syntax.

Cause:
A feature name, daemon name, or server name is too long or a FEATURE or INCREMENT line specifies no hostid, or the number of licenses is not greater than zero.

Action:
Verify that the license file entry is correct or contact your system administrator.
Prolifics License Manager: malloc() call failed

Cause:
License manager could not allocate memory that it needed. The most likely cause is that the program's heap has been corrupted.

Action:
Contact your system administrator.
Prolifics License Manager: Network software (TCP/IP) not available.

Cause:
Could not communicate with the license manager because network software is not present or is correctly configured.

Action:
Contact your system administrator.
Prolifics License Manager: Platform not enabled.

Cause:
Should not happen. Indicates that license daemon prold is not licensed to run on your platform.

Action:
Contact your system administrator.
Prolifics License Manager: Server does not support feature [product].

Cause:
The feature [product] does not have a FEATURE or INCREMENT line in the license file.

Action:
Verify that the license file entry is correct, obtain a new license file, or contact your system administrator.
Prolifics License Manager: Time zone offset from GMT more then 24 hours

Action:
Fix the TZ environment variable or contact your system administrator.
Prolifics License Manager: Unknown vendor key type

Cause:
Program's object file is corrupt.

Action:
Contact your system administrator.

Floating Licenses

Prolifics License Manager: All [product] licenses are currently in use.

Cause:
All available licenses for [product] are in use. If your license request has been queued, you get a series of messages showing who has the licenses reserved or how many licenses are in use.

Action:
Try again later or contact your system administrator.
Prolifics License Manager: Cannot communicate with license server or your [product] license was obtained by another user when the license server was restarted.

Cause:
Occurs when you select an item from the New or Open menu options; indicates that the license server has been taken down. If the license server was then restarted, another user got the license for the [product] you were using.

Action:
You can continue editing and can save any screens that are currently open in the editor but must restart Panther (prodev) before you can pick any New and Open menu options.
Prolifics License Manager: FLEXlm key data bad.

Cause:
Program's object file is corrupt.

Action:
Contact your system administrator.
Prolifics License Manager: Bad server hostname in license file.

Cause:
Server named on a SERVER line could not be found.

Action:
Obtain a new license file or contact your system administrator.
Prolifics License Manager: No SERVER lines in license file.

Cause:
The license file cannot be used because there are no SERVER lines for a counted feature.

Action:
Verify that the license file entry is correct, obtain a new license file, or contact your system administrator.
Prolifics License Manager: Version [version] not supported on server.

Cause:
The version [version] of the program being run is greater than that supported by the license file.

Action:
Obtain a new license file or contact your system administrator.

Node-locked Licenses

The following Panther startup error information is specific to node-locked licenses.

Prolifics License Manager: Cannot find ethernet device.

Cause:
On most systems, the license manager must locate an ethernet board to verify the password on the FEATURE or INCREMENT lines.

Action:
Contact your system administrator.
Prolifics License Manager: [product] not authorized for this computer.

Cause:
[product] is not licensed to run on the current computer.

Action:
Contact your system administrator.
Prolifics License Manager: Version [version] not supported.

Cause:
The version [version] of the program being run is greater than that.

Action:
Obtain a new license file or contact your system administrator.

Create License Utility

The following error information is specific to the create_license utility.

No license files (.lic) were detected.

Cause:
Could not detect any license files (.lic) in the current directory.

Action:
Check the filenames of the license files in $SMBASE/licenses. Your license files should have one of the following names: proserv.lic (Panther application server engine), prodev.lic (development client), or proweb.lic (web application broker).
Unable to create license.dat

Cause:
Encountered an error when trying to create the license.dat file.

Action:
Check file permissions and disk space to allow the create_license utility to write to disk.
Inconsistent DAEMON lines.

Cause:
Two license files (.lic) have DAEMON lines, but they are inconsistent with each other. Since the resulting license.dat file and the vendor daemon (prold) are for a single machine, any DAEMON lines among license files should be the same.

Action:
Check the license files with DAEMON lines for typographical errors.
Inconsistent SERVER lines.

Cause:
Two license files (.lic) have SERVER lines, but they are inconsistent with each other. Since the resulting license.dat file is meant for one server machine, any SERVER lines among license files should be the same.

Action:
Check the license files with SERVER lines for typographical errors.

FLEXlm Informational Messages

The following messages are generated by FLEXlm license management software, and is provided courtesy of the FLEXlm Programmer's Guide.

Connected to node

Cause:
This daemon is connected to its peer on node.
CONNECTED, master is name

Cause:
License daemon logs this message when a quorum is achieved and everyone has selected a master.
DENIED: N feature to user (mm/dd/yy hh:mm)

Cause:
user was denied access to N licenses of feature.
EXITING DUE TO SIGNAL nnn
EXITING WITH CODE nnn

Cause:
An interrupt signal has been intercepted. All daemons list the reason that the daemon has exited.
EXPIRED: feature

Cause:
feature has passed its expiration date.
IN: feature by user (N licenses) (used: d:hh:mm:ss)

Cause:
user at d:hh:mm:ss.
IN server died: feature by user (N licenses) (used: d:hh:mm:ss)

Cause:
user has checked in N licenses of feature by virtue of the fact that his server died.
License Manager server started

Cause:
License daemon has been started.
Lost connection to host

Cause:
A daemon can no longer communicate with its peer on node host, which can cause the clients to have to reconnect, or cause the number of daemons to go below the minimum number, in which case clients may start exiting. If license daemons lose the connection to the master, they will kill all vendor daemons; vendor daemons will shut themselves down.
Lost quorum

Cause:
Not enough servers to satisfy quorum number. The daemon will process only connection requests from other daemons.

Action:
Check network connection between servers.
MASTER SERVER died due to signal nnn

Cause:
License daemon received fatal signal nnn.
MULTIPLE xxx servers running.
Please kill, and restart license daemon

Cause:
License daemon has detected multiple copies of vendor daemon xxx are running.

Action:
Kill all xxx daemon processes and restart the license daemon.
OUT: feature feature by user (N licenses) (used: d:hh:mm:ss)

Cause:
user has checked out N licenses of feature at d:hh:mm:ss.
Removing clients of children

Cause:
Top-level daemon logs this message when one of the child daemons dies.
RESERVE feature for HOST name
RESERVE feature for USER name

Cause:
A license of feature is reserved for either user name or host name.

Action:
None.
Restarted xxx (internet port nnn)

Cause:
Vendor daemon xxx was restarted at internet port nnn.
Retrying socket bind (address in use)

Cause:
The license server tries to bind sockets for approximately 6 minutes if they detect address in use errors.

Action:
Check for multiple lmgrds using the same TCP port number.
Selected (EXISTING) master node

Cause:
This license daemon has selected an existing master (node) as the master.
SERVER shutdown requested

Cause:
Daemon received shutdown request from a user-generated kill command.
[NEW] Server started for: feature-list

Cause:
A (possibly new) server was started for the features listed.
Shutting down xxx

Cause:
The license daemon is shutting down the vendor daemon xxx.
SIGCHLD received. Killing child servers.

Cause:
Vendor daemon logs this message when a shutdown is requested by the license daemon.
Started name

Cause:
License daemon logs this message whenever it starts a new vendor daemon.
Trying connection to node

Cause:
Daemon is attempting a connection to node.

FLEXlm Configuration Problem Messages

hostname: Not a valid server host, exiting

Cause:
This daemon was run on an invalid hostname.

Action:
Run lmgrd on the host(s) specified in the SERVER lines.
hostname: Wrong hostid, exiting

Cause:
Hostid is wrong for hostname.

Action:
Check the license file and ensure the hostnames match the hostids.
BAD CODE for feature-name

Cause:
Specified feature name has a bad encryption code.

Action:
Check the password received from Prolifics.
CANNOT OPEN options file file

Cause:
Options file specified in the license file could not be opened.

Action:
Check the path for the options file on the DAEMON line in the license file.
Couldn't find a master

Cause:
Daemons could not agree on a master.

Action:
Kill and then restart lmgrd on servers.
license daemon: lost all connections

Cause:
Indicates all the connections to a server are lost, which often indicates a network problem.

Action:
Check the network and restart the daemons.
lm_server: lost all connections

Cause:
All the connections to a server are lost; probably indicates a network problem.
lost lock, exiting

Cause:
Error closing lock file.
NO DAEMON line for daemon

Cause:
License file does not contain a DAEMON line for daemon.

Action:
Add DAEMON line for daemon in the license file.
NO DAEMON line for name

Cause:
Vendor daemon logs this error if it cannot find its own DAEMON name in the license file.

Action:
Edit license file.
NO DAEMON lines, exiting

Cause:
License daemon logs this message if there are no DAEMON lines in the license file; with no vendor daemons to start, there is nothing to do.

Action:
Edit license file.
No features to serve!

Cause:
Vendor daemon found no features to serve. This could be caused by bad data in the license file.

Action:
Inspect the license file for bad data.
No license data for feature, feature unsupported

Cause:
No feature line for feature in the license file.

Action:
Edit the license file.
Unable to re-open lock file

Cause:
Vendor daemon has a problem with its lock file, usually because of an attempt to run more than one copy of the daemon on a single node.

Action:
Locate the other daemon that is running via a ps command, and kill it with kill -9.
Unknown host: hostname

Cause:
hostname specified on a SERVER line in the license file does not exist in your host's database.

Action:
Check with your system administrator for the correct hostname. FLEXlm uses standard network services to find the host: Domain Name Server (DNS), Network Information Services (NIS or YP) or in /etc/hosts.
UNSUPPORTED FEATURE request: feature by user

Cause:
user has requested a feature that this vendor daemon does not support. This can happen for a number of reasons: the license file is bad, the feature has expired, or the daemon is accessing the wrong license file.

Daemon Software Error Messages

ATTEMPT TO START VENDOR DAEMON xxx with NO MASTER

Cause:
Vendor daemon was started with no master selected. This is an internal consistency error in the daemons.

Action:
Report error to Prolifics technical support.
BAD PID message from nnn: xxx (msg)

Cause:
Top-level vendor daemon received an invalid PID message from one of its children (daemon number xxx).
BAD SCONNECT message: (message)

Cause:
An invalid server connect message was received.
Cannot create pipes for server communication

Cause:
The pipe system call failed.

Action:
Report error to Prolifics technical support.
Can't allocate server table space

Cause:
A malloc error.

Action:
Check swap space
Connection to node TIMED OUT

Cause:
Daemon could not connect to node.

Action:
Check the network.
Error sending PID to master server

Cause:
Vendor server could not send its PID to the top-level server in the hierarchy.

Action:
Report error to Prolifics technical support.
f-do-notify called with no valid feature

Cause:
Internal inconsistency error.

Action:
Report error to Prolifics technical support.
Illegal connection request to DAEMON

Cause:
A connection request was made to DAEMON, but this vendor daemon is not DAEMON.

Action:
Report error to Prolifics technical support.
Illegal server connection request

Cause:
A connection request came in from another server without a DAEMON name.

Action:
Report error to Prolifics technical support.
KILL of child failed, errno = nnn

Cause:
A daemon could not kill its child.

Action:
Get PID of daemon and kill with kill -9.
No internet port number specified

Cause:
Vendor daemon was started without an Internet port.

Action:
Specify an Internet port on the SERVER line.
Not enough descriptors to re-create pipes

Cause:
Top-level daemon detected the death of one of its sub-daemons. In trying to restart the chain of sub-daemons, it was unable to get the file descriptors to set up the pipes to communicate.

Action:
This is a fatal error. The daemons must be restarted.
read: error message

Cause:
An error in a read system call was detected.
recycle_control BUT WE DIDN'T HAVE CONTROL

Cause:
The hierarchy of vendor daemons has become confused over who holds the control token. This is an internal error.
return_reserved: can't find feature listhead

Cause:
When a daemon is returning a reservation to the free reservation list, it could not find the listhead of features.
select: message

Cause:
An error in a select system call was detected.

Action:
Report error to Prolifics technical support.
Server exiting

Cause:
Server is exiting; normally due to an error.

Action:
Report error to Prolifics technical support.
SHELLO for wrong DAEMON

Cause:
Vendor daemon was sent a server hello message that was destined for a different DAEMON.
Unsolicited msg from parent!

Cause:
Normally, the top-level vendor daemon sends no unsolicited messages. If one arrives, this message is logged. This is a bug.

Action:
Report error to Prolifics technical support.
WARNING: CORRUPTED options list (o->next == 0)
Options list TERMINATED at bad entry

Cause:
Internal inconsistency was detected in the daemon's option list.

Action:
Report error to Prolifics technical support.