You can view a brief description of any Silk Meter error by using the method errorReason. This method returns a short error description in a string or NULL if no error is reported.
The error code describes the attempt that satisfied most of the policy requirements. For example, if one policy rejects the license request because the software version is incorrect and another policy has an appropriate version but rejects the license request because all licenses are in use, the error code will state that all licenses are in use.
| Error Number | Error Code | Description |
|---|---|---|
| 0 | SGME_NO_ERROR | No error occurred during the issuing or confirmation of the license. The license is valid. |
| 1 | SGME_ERROR_RETURN_CHALLENGE_FAILED | The return challenge checksum from the Usage Control Server is incorrect. The Usage Control Server may not be authorized to issue a license. |
| 2 | SGME_ERROR_CALL_CHALLENGE_FAILED | The Usage Control Server refused to perform the requested operation because the call challenge checksum was incorrect. The client is not authorized to perform operations on this server. |
| 3 | SGME_FAILURE_PROPSERVICE | Communication with the COS Property Service failed. |
| 4 | SGME_FAILURE_LICMANAGER | Communication with the License Manager failed. |
| 5 | SGME_FAILURE_LICSERVER | Communication with the License Server failed. |
| 6 | SGME_FAILURE_NAMESERVICE | Communication with the COS Naming Service failed. |
| 7 | SGME_FAILURE_NAMES_READ | The object naming information file names.dat could not be read. |
| 8 | SGME_FAILURE_NO_NAME | The requested server name could not be resolved. |
| 9 | SGME_FAILURE_NAMES_WRITE | The object naming information file names.dat could not be updated. |
| 10 | SGME_FAILURE_MULTIPLE_SERVERS | Multiple servers for this producer are running on one host. |
| 11 | SGME_FAILURE_RENAMED_SERVER_EXECUTABLE | The server executable has been renamed. |
| 12 | SGME_FAILURE_PROPERTY_READ | A property could not be read from the COS Property Service. |
| 13 | SGME_FAILURE_PROPERTY_WRITE | A property could not be written to the COS Property Service. |
| 14 | SGME_FAILURE_NO_PRODUCER | The requested producer is not registered. |
| 15 | SGME_FAILURE_SVR_NAMESERVICE | Communication between the License Server and the COS Naming Service failed. |
| 16 | SGME_FAILURE_SVR_NAMES_READ | The License Server could not read the object naming information. |
| 17 | SGME_FAILURE_SVR_NAMES_WRITE | The License Server could not update the object naming information. |
| 18 | SGME_FAILURE_SVR_NO_NAME | The License Server could not resolve a server name in the naming file. |
| 19 | SGME_FAILURE_SVR_PROPERTY_READ | The License Server could not write a property to the COS Property Service. |
| 20 | SGME_FAILURE_SVR_PROPERTY_WRITE | The License Server could not read a property from the COS Property Service. |
| 21 | SGME_FAILURE_SVR_PROPSERVICE | Communication between the License Server and the COS Property Service failed. |
| 22 | SGME_FAILURE_SVR_LICMANAGER | Communication between the License Server and the License Manager failed. |
| 30 | SGME_FAILURE_PG | The Policy Generator failed. |
| 31 | SGME_FAILURE_PG_LICENSE | The Policy Generator was unable to obtain a valid license. |
| 32 | SGME_FAILURE_PG_LICMANAGER | Communication between the Policy Generator and the License Manager failed. |
| 33 | SGME_FAILURE_PG_AUTH | Authentication to use the Policy Generator failed. |
| 34 | SGME_FAILURE_PG_PERM | Permission to use the Policy Generator is insufficient. |
| 35 | SGME_FAILURE_POLICY_NOT_FOUND | The requested policy was not found in the license manager. |
| 50 | SGME_ERROR_OLD_SERVER_VERSION | The server version is lower then the version required by the policy. Please update your Silk Meter server. |
| 101 | SGME_ERROR_WRONG_PRODUCT | No policy for the requested product is available. |
| 102 | SGME_ERROR_WRONG_VERSION | No policy for the requested version of the product is available. |
| 103 | SGME_ERROR_WRONG_PLATFORM | No policy for the platform of the client is available for the requested product. |
| 104 | SGME_ERROR_WRONG_PART | The requested part of this product does not exist. |
| 105 | SGME_ERROR_KEY_INVALID | The key of the requested policy is invalid. |
| 106 | SGME_ERROR_DUPLICATE_POLICY_ID | The policy ID of the requested policy is a duplicate. |
| 107 | SGME_ERROR_POLICY_SYNTAX_ERROR | The text of the requested policy has syntax errors. |
| 108 | SGME_ERROR_WRONG_SERVERID | The host ID of the Usage Control Server is incorrect. The server is not authorized to issue licenses for the policy. |
| 109 | SGME_ERROR_NO_USER_GRANT | The current user has no authorization to use the product. |
| 110 | SGME_ERROR_NO_GROUP_GRANT | The user's current group isn't authorized to use the product. |
| 111 | SGME_ERROR_NO_HOST_GRANT | The user's current host isn't authorized to use the product. |
| 112 | SGME_ERROR_GRANTS_PGRANTS_MIXED | User grants and producer grants can't be mixed in a single policy. |
| 113 | SGME_ERROR_NO_LICENSES | All licenses for the requested product are in use. |
| 114 | SGME_ERROR_DATE_EXPIRED | Policy Expired. The current date is past the last day of the policy for this product. |
| 115 | SGME_ERROR_DATE_NOT_REACHED | The current date is before the starting date of the policy for this product. |
| 116 | SGME_ERROR_WRONG_DAY | Usage of this product is not authorized on this day of the week. |
| 117 | SGME_ERROR_WRONG_TIME | Usage of this product is not authorized at this time of day. |
| 118 | SGME_ERROR_NO_INVOKES | The number of invocations of this product has exceeded the number specified in the policy. |
| 119 | SGME_ERROR_NO_UNITS | The number of consumption units of this product has exceeded the number specified in the policy. |
| 120 | SGME_ERROR_WRONG_PASSWORD | The supplied password does not match. |
| 130 | SGME_ERROR_WRONG_HOSTNAME | The supplied host name does not match. |
| 140 | SGME_ERROR_NO_STANDALONE_LICENSE | No standalone license is available. |
| 150 | SGME_ERROR_DONGLE_CHECK_FAILED | Could not find the specified dongle. |
| 160 | SGME_ERROR_USAGEPERIOD_CORRUPTED | The data for the Usage Period check is corrupted. |
| 161 | SGME_ERROR_USAGEPERIOD_TOO_EARLY | The date has been set back since the last Usage Period usage. |
| 162 | SGME_ERROR_USAGEPERIOD_ALL_USED | All Usage Periods have been used for this policy. |
| 165 | SGME_ERROR_USAGEPERIOD_NO_JAVA | Usage Periods are not supported in Java standalone mode and by Java servers. |
| 166 | SGME_ERROR_USAGEPERIOD_NO_UNIX | Usage Periods are not supported in UNIX standalone mode and by UNIX servers. |
| 167 | SGME_STANDALONE_NOT_SUPPORTED | This function is not supported in standalone mode. |
| 170 | SGME_ERROR_SYSTEM_TIME_CORRUPTED | The system time has been set back or otherwise corrupted. |
| 171 | SGME_ERROR_NEED_DONGLEID | A dongle ID is required when using a usage_dongle_type attribute. |
| 172 | SGME_ERROR_DONGLE_FAILURE | Technical failure, unable to access dongle. |
| 173 | SGME_ERROR_DONGLE_MISSING | Couldn't find Micro Focus dongle. |
| 174 | SGME_ERROR_DONGLE_WRONG_ID | Couldn't find Micro Focus dongle with matching dongle id. |
| 175 | SGME_ERROR_DONGLE_NO_UNIX | Dongles not supported by UNIX. |
| 176 | SGME_ERROR_DONGLE_LATER_FAILURE | Dongle with ID found, but subsequent technical failure occurred. |
| 177 | SGME_ERROR_DONGLE_MEMORY_FULL | Not enough memory remaining on dongle. |
| 178 | SGME_ERROR_DONGLE_WRITE_FAILED | Write to dongle failed. |
| 179 | SGME_ERROR_DONGLE_TIME_ERROR | Time set back or time error occurred. |
| 180 | SGME_ERROR_DONGLE_NO_FILL | Fill_or_kill set, not enough tokens available. |
| 181 | SGME_ERROR_DONGLE_NOT_IMPLEMENTED | Dongles not implemented. |
| 190 | SGME_ERROR_MOBILE_INVALID_PARAMETER | Invalid parameters provided for mobile licensing. |
| 200 | SGME_ERROR_MOBILE_LICENSING | Mobile licensing error. |
| 202 | SGME_ERROR_POLICY_NOT_MOBILE | Mobile policy is required. |
| 203 | SGME_ERROR_MOBILE_OLD_SERVER_VERSION | License server is to too old for mobile licensing. |
| 205 | SGME_ERROR_NO_INSTALLED_MOBILE_POLICY | There is no local mobile policy with required policy ID. |
| 206 | SGME_ERROR_NO_MOBILE_PARENT_HOST | License server is not mobile parent host. |
| 207 | SGME_ERROR_INVALID_MOBILE_INSTALLATION | Mobile policy has not been installed properly. |
| 209 | SGME_ERROR_MOBILE_CHECKIN | Error on check in of mobile licenses. |
| 211 | SGME_ERROR_MOBILE_POLICY_ALREADY_INSTALLED | Mobile policy with required ID already installed on this machine. |
| 214 | SGME_ERROR_MOBILE_LOCAL_OR_STANDALONE | Cannot check out policy from local machine or in standalone mode. |
| 217 | SGME_ERROR_MOBILE_NO_TARGET_POLICY | Target policy is no mobile license. |
| 219 | SGME_ERROR_MOBILE_NOT_ENOUGH_LICENSES | There are not enough licenses on license server for requested mobile licenses. |
| 221 | SGME_ERROR_MOBILE_TARGET_IS_DONGLE | Target license is a dongle based license and not supported for mobile licensing. |
| 223 | SGME_ERROR_MOBILE_TARGET_IS_MOBILE | Target license is already a mobile license. |
| 225 | SGME_ERROR_MOBILE_TARGET_HAS_MAXUNITS | Target license has a maximum of units, which are not supported for mobile licensing. |
| 227 | SGME_ERROR_MOBILE_TARGET_IS_SILKCARD | Target license is a SilkCard license and not supported for mobile licensing. |
| 229 | SGME_ERROR_MOBILE_WRONG_TIMEFRAME | Timeframe error. |
| 231 | SGME_ERROR_WRONG_MOBILE_PARENT_HOST | Target license server is not parent of mobile licenses. |
| 233 | SGME_ERROR_LOCAL_POLICY_WITH_SAME_ID_EXISTS | There exists already a license with same policy id on local license server. |
| 10000 | SGME_ERROR_UNKNOWN | Unknown reason. |