Instant Protection PLUS 3 uses the Protection PLUS function library and Automation Client library and can return error codes associated with those libraries, as well as its own internal error codes. Errors that occur during activation are likely Automation Client error codes. The Automation Client can return error codes from SOLO Server. Refer to the Directory of Return Codes in our knowledge-base for a complete list of error codes and their descriptions.
| Error Number | Description |
|---|---|
| -2 | This is the default value returned by the fake.dll or fakeVB.dll when the application has not yet been wrapped. This is only relevant when using the Instant Protection PLUS 3 wrapper and does not apply to the Instant Protection PLUS 3 DLL. |
| -1 | The Instant Protection PLUS 3 API is not available. Make sure you selected to use the API in the wizard. The checkbox can be found on the Wrapper Settings page when wrapping or the File Output page when using the Instant Protection PLUS 3 DLL. This can also occur if the application attempts to call an Instant Protection PLUS 3 API function after having already called WR_Close. This error may be returned when using the Instant Protection PLUS 3 DLL if the DLL has been unloaded and reloaded. |
| 0 | The function call has failed, or returned a false condition. |
| 1 | The function call has succeeded, or returned a true condition. |
| 2 | Invalid parameters have been passed to the function. Please make sure you are passing valid values into the parameters of the function. |
| 3 | Cannot modify license file attributes. The license file is in a state that can not be manipulated. Please make sure the user has permissions to modify this file. On Windows NT based operating systems make sure they have at least Power User permissions on the license file. |
| 4 | Reserved. |
| 5 | Cannot write to the license file or network floating semaphore file. Verify that the directory and file in question are not marked as READ-ONLY. Also verify that the user has access to write this file into this directory. |
| 6 | Cannot close license file. This can happen for many reasons, contact Technical Support for further information with troubleshooting this problem. |
| 7 | Cannot open license file. Verify that the user has the correct permissions to the file and folder which contains the file. |
| 8 | Cannot read license file. |
| 9 | The license file could not be created. The most common reason is due to user’s security restrictions. |
| 10 | The license file could not be deleted. Either the file is currently in use, or the user does not have the proper security rights on the computer. |
| 11 | Reserved. |
| 12 | Invalid Password. Internal error. Please contact Technical Support for further assistance. |
| 13 | The password used to open the license file is not the same password used when creating the license file. Please contact Technical Support for further assistance. |
| 14 | Invalid parameters have been passed to the function. Please make sure you are passing valid values into the parameters of the function. |
| 15 | Cannot locate the license file. If using non-registry based license files, verify the license file is in the same folder as the application executable. |
| 16 | The memory could not be allocated to read the license file. |
| 17 | The memory to the license file was not released after the file was closed or created. Please contact Technical Support. |
| 18 | The license file handle is invalid. |
| 19, 20 | Reserved. |
| 21 | License Full. An attempt has been made to add a computer ID to the license file, but the license file is at maximum capacity (100 computer id's). |
| 22 | A duplicate computer id is being added to the license file without specifying the flag allowing duplicate computer id's. |
| 23 | The network floating semaphore file cannot be created because all of the seats are presently being used. |
| 24 through 37 | The field number or value used during a Get or Set function call is invalid. |
| 37 | Reserved. |
| 38 | The internal checksum for the license file could not be verified. This may indicate the license file has been tampered with or is corrupt. |
| 39 through 42 | Reserved. |
| 42 through 46 | There are insufficient user permissions to the registry. Make sure that the program is run first by an Administrator so that the "aliases" in the registry can be properly created. |
| 47 through 55 | Reserved. |
| 56 | The parameter supplied does not match the parameter input into one of the functions. This is most commonly caused by using a slot that does not exist when implementing the WR_LFGet and WR_LFSet functions. |