Instant Protection PLUS 3 error & return codes

For additional information regarding these Return Codes, or to report the occurrence of a Return Code not included on this list, please contact us and a member of our Technical Support staff will respond to your query as promptly as possible.

IMPORTANT NOTE: In addition to the these Return Codes, Instant Protection PLUS 3 may, as circumstances dictate, display a return or error code that has actually been generated by either the SOLO Server interface or an interaction with Protection PLUS.  Please refer to the Common SOLO Server Web Service Return Codes or Common Protection PLUS 4 / Protection PLUS 5 Return Codes for comprehensive listings of possible values and their associated descriptions.

Return Code = 2

The activation server could not be found. Verify that the computer is connected to the Internet, and that the firewall/proxy is set-up properly. Alternatively, check that the activation server is set correctly under the menu option Tools / Options / Server Settings tab.

Return Code = 4

It could connect to the Internet, but the activation server could not be found.  Verify that the computer's firewall/proxy is set-up properly. Alternatively, check that the activation server is set correctly under the menu option Tools / Options / Server Settings tab.

Return Code = 6

This is an internal problem that is normally remedied by either rebooting the computer or installing the latest version of your preferred Web browser. Also, verify that the computer's firewall/proxy is set-up properly

Return Code = 8

The URL for one of the Internet communication functions is incorrect.  Verify that the computer's firewall/proxy is set-up properly. Alternatively, check that the activation server is set correctly under the menu option Tools / Options / Server Settings tab.

Return Code = 9

The license file could not be created. Make sure that the program is first executed by the Administrator so that the license file and "aliases" get properly created as described in the Using Protection PLUS on Windows Vista and Windows 7 whitepaper.

Return Code = 13

If this Return Code occurs during start-up:  The License File password is invalid.  Generally, this indicates that the License File password has been changed within the wrapped application, but alias files containing the old password remain on the computer.  You will probably need to delete these alias files from the machine.  If this Return Code occurs during activation:  There is no network connection available to connect to the Internet or, possibly, the connection timed out.  Verify the presence of an Internet connection.  Alternatively, try disabling any firewall or Internet security software.

Return Code = 15

The License File was not found.  When using a pre-created License File, the application will attempt to open the License File in the same folder as the application.

Return Code = 42

There are insufficient user permissions to the registry. Make sure that the program is first executed by the Administrator so that the "aliases" in the registry get properly created as described in the Using Protection PLUS on Windows Vista and Windows 7 whitepaper.

Return Code = 69

The supplied Activation Code was not correct.  This Return Code typically signifies that one of the following conditions has occurred:

  1. The Trigger Code seed value used in the client application does not match the server setting.  You can open the applicable IPP file (be certain that you have the correct IPP file opened if you are activating a user via telephone) in Instant Protection PLUS 3 and step through the wizard to the page that shows the application connected to SOLO Server.  This page has the Trigger Code and RegKey2 seed values.  Log into your SOLO Server account, go to your Product Option listing, and click on the Product Option that the customer is attempting to activate.  Look for the Trigger Code seed value and verify that it is the same.
  2. The Trigger Code number configured in SOLO Server does not match a supported Instant Protection PLUS 3 Trigger Code.  Log into your SOLO Server account, go to your Product Option listing, and click on the Product Option that the customer is attempting to activate.  Look for the Trigger Code number value and make sure it is a supported Trigger Code number.

Once the client and the server settings match, this error should no longer continue to occur.

Return Code = 70

The supplied Activation Code 2 (RegKey2) is not valid.  This Return Code typically signifies that one of the following conditions has occurred:

  1. The Trigger Code RegKey2 seed value used in the client application does not match the server setting.  You can open the IPP file in Instant Protection PLUS 3 and step through the wizard to the page that shows the application connected to SOLO Server. his page has the Trigger Code and RegKey2 seed values.  Log into your SOLO Server account, go to your Product Option listing, and click on the Product Option that the customer is attempting to activate.   Look for the RegKey2 seed value and verify that it is the same.
  2. The Trigger Code number configured in SOLO Server needs additional numeric data (i.e., Registration Code 2) during activation and the Product Option Type is not properly configured to "send down," or transmit, a Registration Code 2 value.  Log into your SOLO Server account, go to your Product Option listing, and click on the Product Option that the customer is attempting to activate.  Look for the Trigger Code number to see which Instant Protection PLUS 3 Trigger Code you are sending down.  Then make sure the Product Option Type is configured to one of the following types that is capable of transmitting a Registration Code 2 value:
    1. PLUS Activation Code with Quantity
    2. PLUS Activation Code with Fixed Value
    3. PLUS Activation Code with Days Left
    4. PLUS Activation Code with License Counter

Once the client and the server settings match, this error should no longer continue to occur.

Return Code = 304

Key generator found.  Instant Protection PLUS 3 has basic keygen detection that scans all windows looking for common keygen terminology or specific keygen names.  This feature is enabled on the Telephone Activation Options page in the Instant Protection PLUS 3 Wizard and is only performed during telephone activation.  You can customize the keygen search under the Tools / Options / KeyGen Settings tab.

Return Code = 305

If the user has modified their HOSTS file to attempt to re-direct the online license checks or online activations to another server, this Return Code will be generated.  (NOTE:  The contents of the HOSTS file is only checked if you employ online activation or online license status-checking techniques.)

Return Code = 309

The user is attempting to activate an expired license.  This occurs when the expiration date returned to the application by SOLO Server during the activation process is less than or equal to the current system date of the computer.  The user should purchase a new license; or, alternatively, you may edit the "Download Until" date (as specified on the License Details page in SOLO Server) to allow the user to continue to use the license.  If, for whatever reason, the user pushed their machine's system clock ahead, you will need to activate with Trigger Code 48 to reset the Last Used Date and Time to the current system date and time.

Return Code = 50XX

Please refer to the Common SOLO Server Web Service Return Codes for a comprehensive list of possible values and their associated descriptions.

Return Code = 8080

If the user has modified their HOSTS file to attempt to re-direct the online license checks or online activations to another server, this Return Code will be generated.  (NOTE:  The contents of the HOSTS file is only checked if you employ online activation or online license status-checking techniques.)

Return Code = 9XXX

Please refer to the Common Protection PLUS 4 / Protection PLUS 5 Return Codes for a comprehensive list of possible values and their associated descriptions.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us