This error could have 2 reasons:

•The web service has not all rights which are needed to create / modify files on the folder ..\alg - see Necessary Rights for ASP Service

•Your license file expired or more projects are used then included in the license - for more details view the log file

Connection to the Activation Server could not be established. Typical causes of this error are:

•Activation Server is down

•WebServiceURL in the project template is wrong

•Client does not have Internet access or access is blocked by a firewall

•Client Proxy        Server settings are wrong

Configuration file licprotectorws.config  or a file in the folder \pconfig could not be read. Possible reasons are

•The XML format is wrong. Use an XML editor to edit the file and check all configuration settings

•The defined project config file is missing

•The defined project main file (defined in the config file) is missing

ProjectID is missing - check the configuration file in the folder \pconfig  (older installations  licprotectorws.config )

An unknown instcode is used - check the configuration file in the folder \pconfig (older installations  licprotectorws.config )

No projects could be found - check the configuration file in the folder \pconfig (older installations  licprotectorws.config )

Bad request

•ProjectName is empty - check project template

•A request to the Activation Server was made not using Licence Protector

Unknown request type. This situation could only occur, if the Licence Protector version is newer than the Activation Server server version and Licence Protector uses a command, which is unknown to the Activation Server

Writing to database failed. Check, if the database is running and check the database setup.

Reading from database failed. Check, if the database is running and check the database setup

The Activation Key was already used or is locked.

Increase the number, how often the key can be used (Maximum Key / ID Usage) or unlock the key - details

Unknown project name - the ProjectID used in the configuration file in the folder \pconfig (older installations  licprotectorws.config )must match the project name, defined in the project template. Check the activation workflow configuration file, if the file name of the project file is correct.

The project name should contain no spaces and is case sensitive - see project name.

The error also occurs if the Web Service URL is wrong.

The output file, which is generated on the folder .\alg during product activation, is missing or has a wrong XML format - for more details view the log file. Check if you have spaces or special characters in the project name.

This error indicates, that the Automatic License Generator, which is used to create Activation Keys as a response to the Transaction, can not create Activation Keys. Most often a project definition is missing or wrong on the Activation Server.

If you use a date, make sure that the date format matches the settings of the server operating system - e.g. if you have an US operating system, the date format in the XML file must match this format (e.g. 01/30/2008 - wrong format would be 30.01.2008).

Also, if the ProductID and ModuleID in the config file do not match with the ID you use in the command for the product activation, this could generate the error.

If this error occurs in combination with error 9 (see log file), then check necessary rights for ASP Service. Especially make sure that all subfolders and files have the necessary rights.

If the error occurs in combination with the message: The project-configuration file xy.xml could not be loaded then the necessary rights for ASP Service for the files in the sub folder \alg are missing. Especially make sure that all files with the extension .XML have the rights. The rights settings could have been changed if you have replaced the files.

To get the detail error, login into the Web Administration Interface, select menu Tools, Download Logfile. Search in the logfile for this error.

•Upload the correct project definition

•Select menu Tools, Restart Webservice

Time difference between server and client does not match.

Error 3014 tells you that a request (e.g. product Transaction) or an answer between a Licence/All-In-One Protector client and the Web Activation Service (WAS) failed due to an invalid ticket. A ticket ensures that a request can not be faked by simply replaying it. That is because the ticket may have expired. As default a ticket stays valid for 24 hours.
 
If your user does not have the correct time set on his PC, the error 3014 may also occur. You can react as follows:

•tell the user to correct the local time setting on his client

•increase the validity of all tickets.  Change in the Product Configuration page the value: Maximum time difference between server / customer PC in minutes. The default value is 1440 which is 24 hours.

Notice: The greater the value is set, the weaker is your protection against replay attacks.
 
Notice: Make sure that your Activation Server  has also set the correct time. We recommend using the network time protocol NTP to ensure that the time of the server is set correctly. Consult the OS's documentation how to turn this on.

In case a download or upload of a license file is done, the error could also indicate that the length of the encryption code exceeds 40 characters.

Serial Number / ID / Activation Key does not exist on the Activation Server

The project is configured in the way, that a Serial Number / ID / Activation Key must be added on the Activation Server before it can be used (see: Accept only uploaded Serial Numbers / IDs). When a product activation is done with a Serial Number / ID / Activation Key, which is not stored in the database, error 3015 is generated.

Solution

•Add a key on the Activation Server

•Only create Serial Numbers using the Activation Server and not the Licence Protector Generator

The license was locked.

Error 3014 tells you that a request (e.g. product Transaction) or an answer between a Licence/All-In-One Protector client and the Web Activation Service (WAS) failed due to an invalid ticket. A ticket ensures that a request can not be faked by simply replaying it. That is because the ticket may have expired. As default a ticket stays valid for 24 hours.
 
If your user does not have the correct time set on his PC, the error 3014 may also occur. You can react as follows:

•tell the user to correct the local time setting on his client

•increase the validity of all tickets.  Change in the Product Configuration page the value: Maximum time difference between server / customer PC in minutes. The default value is 1440 which is 24 hours.

Notice: The greater the value is set, the weaker is your protection against replay attacks.
 
Notice: Make sure that your Activation Server  has also set the correct time. We recommend using the network time protocol NTP to ensure that the time of the server is set correctly. Consult the OS's documentation how to turn this on.

In case a download or upload of a license file is done, the error could also indicate that the length of the encryption code exceeds 40 characters.

Deactivation not possible. This error typically occurs when the product was already deactivated and you try to deactivate it again.

Solution: Reactivate the product

Another reason for the error is that you are using a Licence Protector version 4.x and an Activation Server version below 4.1. Update to 4.1 or higher.

A license file download is not possible because the name of the license file in combination with the used ID does not exist or the security code is wrong or tge length of the encryption code exceeds 40 characters. See DownloadLic

A web service call is made from an IP-address, which was not added in the white list within the security settings

There is a problem with your license. If you are a hosting customer contact support@mirage-systems.de. If you run your own server send us the log file and the license file (folder ALG, lpwas.lic).

Configuration file licprotectorws.config or a file in the folder \pconfig could not be read

The XML format is wrong. Use an XML editor to edit the file and check all configuration settings

If you use a date, make sure that the date format matches the settings of the server operating system - e.g. if you have an US operating system, the date format in the XML file must match this format (e.g. 01/30/2008 - wrong format would be 30.01.2008).

This error indicates too many open connections for the SQL-Server. Reboot the SQL Server.  Another reason for the error is that you are using a Licence Protector version 4.x and an Activation Server version below 4.1. Update to 4.1 or higher.

The unique ID / Serial Number is missing for a license file upload.

The command UploadLic needs a unique ID / Serial Number.