SOLO Server Return / Error Codes
Important
SOLO Server has a number of interfaces available for programmatic access. Older scripts referenced by the Automation Client library and Web Service interfaces have Return Code values that are documented in the manual topic for each script. More recent Web Service interfaces share a common list of Return Codes, which are documented below.
For other return codes not listed below, such as those from Protection PLUS, view our directory of return / error codes.
For additional information regarding these Return Codes, please open a support ticket and a member of our Technical Support staff will respond to your query as promptly as possible.
| Return Code | Description |
|---|---|
| 5000 | Invalid Encryption Key ID: For security purposes, these Web services use public-private key encryption and digital signatures. In order to determine the keys used server side for decryption/encryption and signature verification/creation, each request is required to include an EncryptionKeyID XML element containing the author's unique EncryptionKeyID. This Return Code is generated when this element is either missing or the EncryptionKeyID itself is not valid. |
| 5001 | Encryption required: For security purposes, these Web services require that all XML content aside from the EncryptionKeyID be encrypted and include a digital signature of the encrypted portion by the keys corresponding to the EncryptionKeyID. This Return Code is generated when this portion of the XML is not properly encrypted. |
| 5002 | Signature required: For security purposes, these Web services require that all XML content aside from the EncryptionKeyID be encrypted and include a digital signature of the encrypted portion by the keys corresponding to the EncryptionKeyID. This Return Code is generated when the digital signature has been erroneously omitted. |
| 5003 | Decryption failure: For security purposes, these Web services require that all XML content aside from the EncryptionKeyID be encrypted and include a digital signature of the encrypted portion by the keys corresponding to the EncryptionKeyID. This Return Code is generated when the encrypted portion of the XML cannot be successfully decrypted. |
| 5004 | Verification of digital signature failed: For security purposes, these Web services require that all XML content aside from the EncryptionKeyID be encrypted and include a digital signature of the encrypted portion by the keys corresponding to the EncryptionKeyID. This Return Code is generated when digital signature cannot be verified. |
| 5005 | Invalid parameters: Each Web method has optional and required input content. This Return Code is generated when one or more required input elements are missing. |
| 5006 | Security Check Failure: This Return Code is generated when too many failed activation attempts are made in a short period of time, suggesting the possibility of a "brute force attack" to acquire a successful activation. On the License Details page, click the "Reset Activation Check" button to clear the temporary block. |
| 5007 | Invalid Computer ID: This Return Code is generated when the UserCode2 (ComputerID) value in the request XML is either an invalid numeric value or 0 (zero). |
| 5008 | Invalid Activation Data: The License ID and/or Password could not be validated by SOLO Server. Make sure the user has a valid License ID and Password and is keying them correctly when attempting activation. |
| 5009 | Unregistered customer: If the RequireRegistration XML element is included and specified as True for an activation request, the system will verify that the customer is registered and reject the activation if the customer is indeed not registered. This Return Code is generated when this condition occurs. |
| 5010 | Invalid Product ID: If the ProductID XML element is included and populated for an activation request, the system will verify that this value matches the ProductID associated with the License ID. This Return Code is generated when this check fails. |
| 5011 | Invalid Product Option ID: If the ProdOption XML element is included and populated for an activation request, the system will verify that this value matches the ProdOption associated with the License ID. This Return Code is generated when this check fails. |
| 5012 | Invalid Product Version: The version of the application is less than the Minimum Activation Version specified on the Product Option. |
| 5013 | No Remaining Activations: The user has consumed the maximum number of activations allocated to the License ID. |
| 5014 | Invalid Product Option ID Type: An invalid Product Option Type has been specified for the associated License ID. You must select one of the PLUS Option Types to be able to use the license for activation. |
| 5015 | Invalid Installation ID: This return Code is generated when the InstallationID in the request XML is invalid. |
| 5016 | Deactivated Installation: The Installation ID has been deactivated within SOLO Server. A SOLO Server user must re-enable the Installation ID or issue a new License ID / Password to be able to continue. |
| 5017 | Invalid License Status: The License ID status, as displayed on the License Details page within SOLO Server, is something other than "OK". |
| 5018 | No remaining deactivations: This Return Code is generated by a failed deactivation request due to the absence of any remaining deactivations for the License ID. |
| 5019 | License ID has expired: This Return Code is generated when the specified expiration date of the License ID is now in the past. |
| 5020 | Internal authentication failed: This Return Code is generated when authentication has failed for an internal call to a Web method. |
| 5021 | Invalid IP address detected: The IP address of the activating machine is not among the Allowed Activation IPs as displayed on the License Details page in SOLO Server. This Return Code is only applicable if the Product Option associated with the License ID has been configured to restrict activation to one or more client IP addresses. |
| 5022 | Invalid System Time: The date/time as displayed by the system clock is not within the threshold specified by SOLO Server. The user must correct the system clock to be able to continue. |
| 5023 | Protection PLUS 5 SDK Access Not Enabled: This Return Code is generated when a call to a web method which requires access to SoftwareKey's Protection PLUS 5 SDK fails because either the author does not have a Protection PLUS 5 SDK license or the license has yet to be enabled by SoftwareKey. |
| 5024 | Invalid XML document: The XML document is not properly formatted and cannot be loaded. |
| 5025 | Plug-in failed: When a pre-activation plug-in is configured on a Product Option, this Return Code is generated during activation when there is an error loading or executing the plug-in not handled by the plug-in itself. |
| 5026 | Plug-in processing failed: When a pre-activation plug-in is configured on a Product Option, this Return Code is generated during activation when the plug-in processing indicates that the activation should be rejected. |
| 5027 | Invalid Network Session: The Network Session has been closed or has expired. |
| 5028 | No Network Seats Remaining: No more network seats are currently free. This error will continue to be returned for the License ID until another network session is closed or expires. |
| 5029 | Invalid Trigger Code Data: This Return Code is generated when the trigger code data is not valid. |
| 5030 | Protection PLUS 5 evaluation expired: This Return Code is generated when the Protection PLUS 5's license has expired. |
| 5031 | SOLO Server evaluation expired: This Return Code is generated when the SOLO Server's license has expired. |
| 5032 | Network Floating Access Not Enabled: Access to the network floating licensing features in SOLO Server are not enabled. Applies only to SOLO Server Shared and Dedicated URL. |
| 5033 | Account Closed: The account for the software author has been closed. Applies only to SOLO Server Shared and Dedicated URL. |
| 5034 | Network Floating Access Invalid Domain: Access to the network floating licensing features in SOLO Server are not allowed through the current domain. Applies only to SOLO Server Shared / Custom URL. |