Technical Memo: LICENSE ERROR MESSAGES





Products	Support	Download	Contact

LICENSE ERROR MESSAGES

Contents | Index | About the Icons

When troubleshooting any potential license problems, make sure that your OPCOM messages are enabled by typing:

    $ REPLY/ENABLE

Here is a list of some common licensing error messages, and the appropriate action that will fix the problem:

Code 10:

The current version of VMS is probably a Beta version, to confirm this type:

    $ WRITE SYS$OUTPUT F$GETSYI("VERSION")

If the version does not begin with a "V", define the following logical:

    $ DEFINE/SYS PKMS$VMS_VERSION "V5.5" (or "V6.1" etc.)

Code 31:

Type the following command:

    $ SHOW LOGICAL PKMS*

If the logical is not defined, run the command file:

    $ @SYS$MANAGER:SSV$STARTUP

Code 32:

The translated key has an invalid length, so at least one key item was ommitted or not entered correctly.

You must re-enter the license key with the procedure:

    $ @SCRIPTSERVER:PKMS_LOAD

Code 33:

The translated key has at least one invalid Checksum

You must re-enter the license key with the procedure:

    $ @SCRIPTSERVER:PKMS_LOAD

Make sure that the key is entered EXACTLY as shown on the paper key, including case-sensitivity, paying close attention to l vs. 1 ("el" vs. one) and 0 vs. O (zero vs. "oh").

Code 40:

NOTE: Three possible problems. Please contact the GrayMatterSoftware Sales Dept.

1)
The node name translated is possibly invalid - type the following:
$ SHOW LOGICAL SYS$NODE
This name must match the node name on the key.
2)
The CPU type does not match the key modules - type the following:
$ WRITE SYS$OUTPUT F$GETSYI("HW_NAME")
This cannot say "SERVER" unless the key has VAX as a module.
3)
The node is not licensed for a cluster - type the following:
$ WRITE SYS$OUTPUT F$GET SYI (CLUSTER_MEMBER")

This cannot say "TRUE" if the license key is "N" for ALLOW CLUSTER. For cluster installations, make sure the file SYS$MANAGER:SSV$STARTUP.COM is in SYS$COMMON.

miscellaneous errors

%SYSTEM-F-NOLOGNAME,"No logical name match"

PKMS logical not found - see code 31.

%SSV-F-IVCPUCLASS, This ScriptServer license does not support this type of CPU,stopping queue.

The version of ScriptServer that is running doesn't recognize the Hardware name as a valid string. First, check to see if there is a more current version of ScriptServer that will support that machine. If not, the code will have to be changed in the next release, and the customer can work around the problem if we issue them a temporary key for that node with the ANY module in it.