Technical article 127927

What do the numeric error codes from the license manager indicate?

OpenServer 6OpenServer 5UnixWare 7

Written

Problem

When adding or registering a license, I see the error:

Unable to run brand command to add a license on the system.

When checking the error "Details", there is a message:

Unable to run brand command to add a license on the system. Invalid License Code or License Number was specified. Error: invalid or missing License Data Exit Value: -###

How can I determine what the numeric exit value indicates?

Solution

Use the following table to translate the exit codes from the brand command:

Error return codes: 0 No error - success -1 Incorrect MD5 sum passed -2 Nodelock file doesn't exist -3 Storage allocation failure -4 Bundled license has no parent -5 Specified license doesnt exist -6 No licenses to work with -7 No default license db was found -8 No such serial number -9 Cant be used during iteration -10 Nodelock file is corrupt -11 Can't read nodelock file - perms? -12 Cant open data for writing -13 Couldn't backup data file -14 Couldn't get file lock -15 Nodelock file is empty -16 License has expired -17 License hasnt started yet -18 Many licenses satisfy criteria -19 License already exists -20 License already registered -21 Nodelock file doesnt have OS lic -22 Multiple OS licenses exist -23 Nodelock sanity checks failed -24 Nodelock file has handle already -25 Invalid nodelock file handle -26 License already has handle -27 Invalid license handle -28 Defaults handle already exists -29 Bad product ID specified -30 Bad version string -31 Bad serial number specified -32 Bad license type specified -33 Bad date specified -34 Bad license code provided -35 Bad third line specified -36 Bad parameter value -37 Bad license flag specified -38 Invalid annotation integer -39 Invalid annotation string -40 Invalid license description -41 Bad bitstring handle passed -42 Bad flagstring handle passed -43 Bad duration specified -44 Unsupported lic type found -45 License has handle checked out -46 Nodelock file not verified -47 Attribute not set -48 License not a container license -49 Cant be expressed as an integer -50 Internal Gradient failure -51 Dependent 'h' license missing -52 Dependent 'l' license missing -53 Depending 'r' license missing -54 Dangling registration license -55 Duration license already used -56 API call not supported yet -57 OID already set

From the Xinuos technical article database, record 127927. Reproduced with permission. The original is at www.sco.com/ta/127927, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.