Solutions

Error 00001

Priority1

Error Message

PowerServer profile name is empty.

Possible Cause

When configuring the PowerServer profile, no profile name is provided.

Error 00002

Priority1

Error Message

PowerServer name is empty.

Possible Cause

When configuring the PowerServer profile, no machine name or IP address of the PowerServer is provided.

Error 00003

Priority1

Error Message

PowerServer port is empty.

Possible Cause

Priority1

Error Message

Deployment user name is empty.

Possible Cause

When configuring the PowerServer profile, the deployment security is enabled, but no deployment username is provided.

Error 00008

Priority1

Error Message

Data source name is empty.

Possible Cause

When configuring the data source, no data source name is specified.

Error 00009

Priority1

Error Message

Data source name already exists.

Possible Cause

When configuring the data source, the provided data source name already exists in the PowerServer.

Error 00010

Priority1

Error Message

The database server is empty.

Possible Cause

When configuring the transaction object, no database server address is provided.

Error 00011

Priority1

Error Message

Specify a valid Web server port.

Error 00017

Priority1

Error Message

Web server port is out of range.

Possible Cause

When configuring the Web server profile, the specified port is not between 1 and 65535.

Error 00018

Priority1

Error Message

Web root is empty.

Possible Cause

When configuring the Web server profile, the local file transfer is selected, but no Web root is specified.

Error 00019

Priority1v

Error Message

The FTP server is empty.

Possible Cause

Priority 1

Error Message

Duplicate transaction object name.

Possible Cause

A transaction object with the same name already exists.

Solution

Priority 2

Error Message

Remove the garbage control %1 in the %2 object.

Possible Cause

PowerBuilder object contains some garbage objects. PowerServer Toolkit will automatically remove these garbage objects. This is only a prompt. It will not affect the parsing result, and you can disregard it.

Error 00054

Priority 1

Error Message

Cannot find the container object %2 for %1.

Possible Cause

1) PowerServer Toolkit failed to export the object. 2) The PBL list added to the PowerServer Toolkit configuration window is incomplete or the script makes reference to the object defined in the PBD file.

Solution

1) Verify that the application was full built in the PowerBuilder IDE and no errors were reported. 2) Verify that the PBL list added to the PowerServer Toolkit | PowerServer Profile Configuration window is complete. 3) Verify that the script makes no reference to the object defined in the PBD file.

Error 00055

Priority 1

Error Message

Cannot find %1 data type of %2 variable in %3.

Possible Cause

The PBL list added to the PowerServer Toolkit configuration window is incomplete or the script makes reference to the object defined in the PBD file.

Solution

Priority 1

Error Message

Cache name ""%1"" contains illegal characters.

Possible Cause

Priority 2

Error Message

Failed to initialize PowerServer.

Possible Cause

Failed to open the adtconfig.xml file. adtconfig.xml is corrupt or modified manually.

Error 02003

Priority 1

Error Message

PowerServer configuration is incorrect.

Possible Cause

adtconfig.xml is corrupt or manually modified.

Solution

Please re-configure the PowerServer Profile in PowerServer Toolkit.

Error 02004

Priority 1

Error Message

Format returned from PowerServer is incorrect.

Possible Cause 1:

The PowerServer version and the PowerServer Toolkit version are not the same.

Solution 1:

Please use PowerServer and PowerServer Toolkit of the same version.

Possible Cause 2:

Certain DataWindow syntax has not been deployed successfully. This happens only for very large applications with an excessive number of DataWindow SQL (say over 10,000) or embedded SQL (say over 3,000).

Solution 2:

Step 1: Adjust the value of the following parameters in the AppeonDev.ini file (located under C:\Program Files\Appeon\PowerServer\Toolkit\ and will be copied to the "bin" folder of application package by PowerServer Package Wizard):

[DeployConfig]
BatchDWSynLen= 10000000
BatchDWSynNum= 200
BatchDWSqlNum= 500
BatchESqlNum=500

BatchDWSynLen specifies the length (in byte) of the DataWindow syntax, which when reached the deployment tool will commit to PowerServer at one time.

BatchDWSynNum specifies the number of DataWindow syntax, which when reached the deployment tool will commit to PowerServer at one time.

BatchDWSqlNum specifies the number of DataWindow SQL, which when reached the deployment tool will commit to PowerServer at one time.

BatchESqlNum specifies the number of embedded SQL, which when reached the deployment tool will commit to PowerServer at one time.

By increasing the value of the above parameters (typically BatchDWSqlNum and BatchESqlNum) according to the number of DataWindow SQL and embedded SQL used in your application, this will reduce the server calls so it eliminates the chance of failing to commit certain syntax. If you have no idea of the number of DataWindow SQL and embedded SQL, you can increment the value by 200 each time and then full deploy the application to see if this error disappears.

Step 2: Modify the IIS web.config xml file.

Go to C:\Inetpub\wwwroot\appeon\AEM, and add the following code to the web.config XML file. By default, the value of the Execution Timeout is 100 seconds, and the value of the Max Request Length is 4096K. You can use larger values for these two properties according to the specific needs.

......
<system.web>
<httpRuntime executionTimeout="30000" maxRequestLength = "102400" />
<httpHandlers>
......

Restart the IIS server to make this change take effect.

Error 02005

Priority 1

Error Message

Error in deploying %1 file.

Possible Cause

1) The file is not generated or deleted.

2) A file with the same name already exists and is read-only.

3) The file is in use.

4) The file is deployed via FTPS (with the "Require explicit FTP over TLS/SSL" option enabled in PowerServer Toolkit), while Windows 7/8/8.1/2012 has a known issue with TLS 1.2.

Solution

Solution for cause 1, 2, or 3: Full deploy the application with the "Full Application Deployment" option in PowerServer Toolkit.

Solution for cause 4: Microsoft Support provides a hotfix for this known issue. Please apply the hotfix according to https://support.microsoft.com/en-us/help/2888853/fix-the-supplied-message-is-incomplete-error-when-you-use-an-ftps-clie, and then re-deploy the application.

Error 02006

Priority 1

Error Message

Failed to delete Web files.

Possible Cause

1) The files on the Web server were modified to be Read-only. 2) The administrator changed the permission. 3) The Web server is being used. 4) The Application Profile for this application is removed.

Solution

Check that the Web files exist and are not read-only, and that the Web server is not being used and the application profile is not removed from PowerServer Toolkit.

Error 02007

Priority 1

Error Message

Cannot connect to the Web server: %1.

Possible Cause

1) The Web server IP, port, user name or password is incorrect. 2) The Web server Web root is empty.

Error 02010

Priority 1

Error Message

Error in generating the WAR file.

Possible Cause

Priority 1

Error Message

Failed to load the DLL file %1.

Possible Cause

PowerServer Toolkit is destroyed. Please reinstall PowerServer Toolkit.

Error 04002

Priority 1

Error Message

Cannot find the SRD file %1.

Possible Cause

The SRD file for the DataWindow failed to generate.

Error 04003

Priority 1

Error Message

Cannot get Web server information from the ADTConfig.xml file.

Possible Cause

Priority 2

Error Message

The Web application you attempt to run was removed from the server. It cannot be run.

Possible Cause

1) The application has been removed from the server. 2) The system is being updated.

Error 10505

Priority 2

Error Message

Transaction has timed out. The transaction is rolled back: %1.

Possible Cause

Transaction has timed out, due to a long transaction execution time.

Solution

1) Modify the source code and reduce the transaction execution time. 2) Increase the transaction timeout period in AEM. However, if the time is set too long, the performance will slow down because the database will be locked for a longer time.

Error 10506

Priority 2

Error Message

Session failed. Please run the application again.

Possible Cause

1) The server is restarted. 2) The session has timed out.

Solution

Please click Refresh on the IE toolbar and log in to the application again.

Error 10507

Priority 1

Error Message

The server status is %1.

Possible Cause

Server is still in the process of starting.

Solution

Please wait until server turns its status to "running".

Error 10508

Priority 1

Error Message

Session has timed out.

Possible Cause

The session has been idle for a specified amount of time.

Solution

Increase the session timeout period in AEM, but do not set it too long. A long existing session may cause security problems.

Error 10999

Priority 1

Error Message

Keyword not supported: 'dsn'.

Possible Cause

PowerServer does not support using ODBC Driver to connect with the SQL Server database.

Solution

To resolve this, go to AEM, and change the ODBC driver to the Native Driver for SQL server.

Error 11006

Priority 1

Error Message

A fatal IOException occurred when retrieving the status of the server %1.

Possible Cause

1) Cannot have I/O communication with the remote server using HTTP. 2) Exceptions occurred when calling methods in the remote server, causing failure to return data.

Solution

1) Check that the server is running and can be connected. 2) Check that PowerServer residing in the server is started. 3) If both network and PowerServer are working, send the log files on the local and remote machines to Appeon technical support engineers.

Error 11007

Priority 0

Error Message

The PowerServer configuration file cannot be empty!

Possible Cause

The configuration file retrieved from the remote server is empty, due to a file transfer error.

Solution

1) Check that the network connection works normally. 2) Check that the PowerServer is running. 3) If both network and PowerServer are working, send the log files on the local and remote machines to Appeon technical support engineers.

Error 11008

Priority 1

Error Message

A fatal IOException occurred when retrieving the configuration file from the remote server: %1.

Possible Cause

1) Cannot have I/O communication with the remote server using HTTP. 2) Exceptions occurred when calling methods in the remote server, causing failure to return data.

Solution

1) Check that the server is running and can be connected. 2) Check that PowerServer residing in the server is started. 3) If both network and PowerServer are working, send the log files on the local and remote machines to Appeon technical support engineers.

Error 11009

Priority 0

Error Message

Failed to read the Sting array in the configuration file from the remote server.

Possible Cause

Cannot construct the object using the stream.

Solution

1) Check that the network can be connected. 2) Check that PowerServer is running. 3) If both network and PowerServer are working, send the log files on the local and remote machines to Appeon technical support engineers.

Error 11010

Priority 0

Error Message

An unexpected exception occurred when replicating PowerServer configuration files!

Possible Cause

Failed to replicate the local configuration file due to an unknown error.

Solution

Priority 0

Error Message

Please input a valid port number with a range from 0 to 65535.

Possible Cause

The specified port number is out of the invalid range.

Error 11517

Priority 0

Error Message

IP address or machine name cannot be localhost or 127.0.0.1!

Possible Cause

IP address or machine name cannot be localhost or 127.0.0.1!

Solution

Please input the IP address or machine name.

Error 11519

Priority 0

Error Message

The interval should be a positive integer, greater than 0 and less than 2147483648.

Possible Cause

The specified interval is invalid.

Solution

Input the interval between 0 and 2147483648.

Error 11520

Priority 0

Error Message

You must select one option between "Enable Remote Backup" and "Enable Local Backup".

Possible Cause

If Heartbeat Backup is selected, you must select between "Enable Remote Backup" and "Enable Local Backup"

Solution

Select "Enable Remote Backup" or "Enable Local Backup"

Error 11521

Priority 1

Error Message

Errors occurred when synchronizing AEM configuration information to the specified remote server: %1. The method is: %2.

Possible Cause

1) Cannot communicate with the remote server using HTTP protocol. 2) Exceptions in calling methods in the remote server. Data cannot be returned.

Solution

1) Verify that the target server is running and can be connected. 2) Verify that the PowerServer residing on the target server is running. 3) If both network and PowerServer work correctly, send log files for the local machine and the target server to the Appeon technical support engineers for in-depth investigation.

Error 11522

Priority 1

Error Message

Errors occurred in calling the remote method. The method is: *; the remote server is: *

Possible Cause

1) Cannot communicate with the remote server using HTTP protocol. 2) Exceptions in calling methods in the remote server. Data cannot be returned.

Solution

1) Verify that the target server is running and can be connected. 2) Verify that the PowerServer residing on the target server is running. 3) Send log files for the local machine and the target server to the Appeon technical support engineers for in-depth investigation.

Error 11523

Priority 2

Error Message

It exceeds the CPU count in the license.

Possible Cause

The number of CPUs on the current machine exceeds the CPU count specified in the license file.

Solution

Please purchase a new license with more CPUs.

Error 11524

Priority 2

Error Message

The license of the remote PowerServer does not match with the license on the local server.

Possible Cause

The license of the remote PowerServer does not match with the license on the local server.

Solution

Replace the license file in the remote PowerServer with the license file on the local server.

Error 12001

Priority 10

Error Message

Failed to get the transaction information from the PowerServer configuration file (transaction object name = %1). Please make sure you have configured this transaction object in AEM correctly.

Possible Cause

1) Transaction object is not configured in AEM. 2) The configuration file is corrupt.

Solution

Re-configure the transaction object in AEM.

Error 12008

Priority 0

Error Message

Application name is null.

Possible Cause

The value of application name passed to the method is null.

Solution

1) Check that the network can be connected. 2) Restart PowerServer. 3) If the error still occurs, send the log files to the Appeon technical support engineers.

Error 12009

Priority 0

Error Message

Property %1 has already been defined.

Possible Cause

The application name passed to the method already exists.

Solution

1) Check that the newly added application does not have the same name with the existing application. 2) The network can be connected. 3) Restart PowerServer. 4) If the error still occurs, send the log files to the Appeon technical support engineers.

Error 12010

Priority 0

Error Message

Argument cannot be null or empty string.

Possible Cause

The argument passed to the method is empty.

Solution

1) Check that the network can be connected. 2) Restart PowerServer. 3) If the error still occurs, send the log files to the Appeon technical support engineers.

Error 12011

Priority 1

Error Message

Error occurred when loading the application configuration file!

Possible Cause

Error occurred when loading the application configuration from the configuration file.

Solution

Check that ApplicationsConfig is not corrupt and the format is correct. Delete it if it is corrupt or the format is incorrect.

Error 12012

Priority 1

Error Message

Error occurred when loading the server configuration information!

Possible Cause

Error occurred when loading the server configuration from the configuration file.

Solution

Check that ServerConfig is not corrupt and the format is correct. Delete it if it is corrupt or the format is incorrect.

Error 12013

Priority 1

Error Message

Error occurred when loading %1 file!

Possible Cause

Error occurred when loading the server configuration from the configuration file.

Solution

1. Check that ServerConfig exists and is not corrupt. If it does not exist or it is corrupt, copy it from the other clustered machine. 2. Send the log files to the Appeon technical support engineers.

Error 12015

Priority 0

Error Message

ServerConfig object is null.

Possible Cause

The argument passed to the method is empty.

Solution

1) Check that the network can be connected. 2) Restart PowerServer. 3) If the error still occurs, send the log files to the Appeon technical support engineers.

Error 12016

Priority 0

Error Message

ApplicationsConfig is null.

Possible Cause

The argument passed to the method is empty.

Solution

1) Check that the network can be connected. 2) Restart PowerServer. 3) If the error still occurs, send the log files to the Appeon technical support engineers.

Error 12017

Priority 1

Error Message

Errors occurred when writing the ServerConfig file.

Possible Cause

The ServerConfig file is corrupt.

Solution

Check that the file is intact. If it is corrupt, delete it.

Error 12018

Priority 1

Error Message

Errors occurred when writing the ApplicationsConfig file.

Possible Cause

The ApplicationsConfig file is corrupt.

Solution

Check that the file is intact. If it is corrupt, delete it.

Error 12019

Priority 1

Error Message

Errors occurred when loading the application configuration.

Possible Cause

Exceptions occurred when loading the application configuration from the file.

Solution

1) Check that the file is not read-only. Reset it if it is read-only. 2) Send the log files to the Appeon technical support engineers.

Error 12020

Priority 1

Error Message

Failed to load the ServerConfig object!

Possible Cause

Errors occurred when loading the server configuration from the configuration file.

Solution

1. Check that ServerConfig exist and is not corrupt. If it does not exist or it is corrupt, delete it. 2. Send the log files to the Appeon technical support engineers.

Error 12021

Priority 1

Error Message

Failed to load the ThreadQueues Config object from file %1!

Possible Cause

Errors occurred when loading the ThreadQueues configuration from the configuration file.

Solution

Priority 0

Error Message

The PB type of the parameter is invalid.

Possible Cause

1) The stored procedure does not exist in the database. 2) The stored procedure parameter uses instance variables.

Error 13010

Priority 10

Error Message

DataObject name cannot be empty.

Possible Cause

PowerServer failed to get the DataObject name.

Solution

1) Check that the PowerBuilder source code is correct. 2) Check that the network is connected. 3) Check that PowerServer is starting and works properly.

Error 13011

Priority 0

Error Message

This column's data type %1 requires the use of an embedded SQL statement.

Possible Cause

The column in the SQL statement used to dynamically create a DataWindow contains unsupported data type.

Solution

Check that the column data type can be used to create DataWindows and ensure that it can be executed in the PowerBuilder

Error 13012

Priority 0

Error Message

User SQL cannot have parameters in Verify SQL Command.

Possible Cause

When using SetSQLSelect in the DataWindow to modify the SQL statement, SetSQLSelect cannot contain parameters.

Error 13013

Priority 2

Error Message

Failed to parse the result meta of the Select statement, due to %1.

Solution

Please contact the Appeon technical support engineers and provide them with the log files.

Error 13014

Priority 2

Error Message

Failed to parse parameter meta of stored procedure, due to %1

Solution

Please send log files to the Appeon technical support engineers.

Error 13015

Priority 10

Error Message

Failed to get DataWindow SQL from PowerServer (Application = %1, DataObject = %2, DBType = %3). Please make sure you have deployed your application correctly.

Possible Cause

Failed to get DataWindow SQL from AppeonDB, possibly because 1) AppeonDB is shut down or failed to work. 2) The DataWindow has not been deployed correctly. View the deploy log for the error. 3) The database type used by the PowerBuilder application and the database type used by the Web application are not the same.

Solution

1) Check that AppeonDB is started and works properly. 2) Check that the DataWindow was deployed successfully. 3) Check that the database type selected for deployment in PowerServer Toolkit and the database type selected for running in AEM are the same.

Error 13016

Priority 10

Error Message

Cannot find the following embedded SQL in AppeonDB: ApplicationName =%1 and SQLKey =%2.

Possible Cause 1

The AppeonDB database is closed or failed to work.

Solution 1

Verify that AppeonDB works correctly.

Possible Cause 2

The embedded SQL has not been deployed successfully. This happens only for very large applications with an excessive number of DataWindow SQL (say over 10,000) or embedded SQL (say over 3,000).

Solution 2

Step 1: Adjust the value of the following parameters in the AppeonDev.ini file (located under C:\Program Files\Appeon\PowerServer\Toolkit\ and will be copied to the "bin" folder of application package by PowerServer Package Wizard):

[DeployConfig]
BatchDWSynLen= 10000000
BatchDWSynNum= 200
BatchDWSqlNum= 500
BatchESqlNum=500

BatchDWSynLen specifies the length (in byte) of the DataWindow syntax, which when reached the deployment tool will commit to PowerServer at one time.

BatchDWSynNum specifies the number of DataWindow syntax, which when reached the deployment tool will commit to PowerServer at one time.

BatchDWSqlNum specifies the number of DataWindow SQL, which when reached the deployment tool will commit to PowerServer at one time.

BatchESqlNum specifies the number of embedded SQL, which when reached the deployment tool will commit to PowerServer at one time.

By increasing the value of the above parameters (typically, BatchDWSqlNum and BatchESqlNum) according to the number of DataWindow SQL and embedded SQL used in your application, this will reduce the server calls so it eliminates the chance of failing to commit certain syntax. If you have no idea of the number of DataWindow SQL and embedded SQL, you can increment the value by 200 each time and then full deploy the application to see if this error disappears.

Step 2: Modify the IIS web.config xml file.

Go to C:\Inetpub\wwwroot\appeon\AEM, and add the following code to the web.config XML file. By default, the value of the Execution Timeout is 100 seconds, and the value of the Max Request Length is 4096K. You can use larger values for these two properties according to the specific needs.

..............

<system.web>

<httpRuntime executionTimeout="30000" maxRequestLength = "102400" />

...............

Restart the IIS server to make this change take effect.

Error 13017

Priority 10

Error Message

The value for Application Name is empty or null.

Possible Cause

The Application Name argument passed from the client is empty.

Solution

Check that the application name and the deployment configuration are correct.

Error 13018

Priority 10

Error Message

The value of DataWindow name is empty or null.

Possible Cause

The DataWindow Name argument passed from the client is empty.

Solution

1) Check that the DataWindow settings in PowerServer Toolkit are correct. 2) Check that PowerServer Toolkit deployment process is successful. 3) Check that the network connection is stable. 4) Check that PowerServer is running and works properly.

Error 13019

Priority 10

Error Message

The value for DWSyntaxString is empty or null.

Possible Cause

The DWSyntaxString parameter values passed from the client are empty.

Solution

Priority 2

Error Message

Error in validating license signature!

Possible Cause

The license file is incorrect due to some reasons.

Solution

Please provide us the following information to fix this issue.

Click the Activate button to generate the license.activation.bin file and send it to us.
Provide us the screenshot of the Licensing page.
Provide us the appeonserver.log and appeonerror.log files, here is the article stating how to generate the log files: http://support.appeon.com/index.php?/Knowledgebase/Article/View/50/11/what-you-can-provide-to-us-for-further-debugging-when-you-run-into-the-appeon-server-related-issues.

Error 14004

Priority 2

Error Message

Missing license file.

Possible Cause

The license file is missing. The license file has been moved or deleted.

Solution

1. Please reinstall the PowerServer component. 2. Please apply for a new license.

Error 14005

Priority 2

Error Message

Invalid software license file %1.

Possible Cause

1. The license.appeon file is empty. 2. The license.appeon file is corrupt.

Solution

1. Check that license.appeon exists in the appeon\AEM\bin folder (eg. C:\Inetpub\wwwroot\appeon\AEM) 2. Update the license file. 3. Please reinstall the PowerServer component.

Error 14006

Priority 2

Error Message

Unable to validate the current license file.

Possible Cause

1. The license file is corrupt. 2. The license file is not for this PowerServer version.

Solution

1. Please reinstall PowerServer. 2. Update the license file.

Error 14009

Priority 2

Error Message

Error in validating hash code!

Possible Cause 1

The PowerServer file is corrupt.

Solution 1

Please reinstall the PowerServer component.

Possible Cause 2

The Windows system setting "System cryptography: use FIPS compliant algorithms for encryption, hashing and signing" is enabled on the server machine. This setting is available in Windows 7.

Solution 2

Please go to the Windows system setting: Local Security Policy > Security Options, and disable the option "System cryptography: use FIPS compliant algorithms for encryption, hashing and signing".

Error 14010

Priority 2

Error Message

The user (%1) has no access rights to the application (%2).

Possible Cause

The user's access rights to the application were restricted in AEM by the administrator.

Solution

On the AEM > Application > Client Security page, assign the user with proper rights to access the application.

Error 14016

Priority 2

Error Message

The license file installed to the machine hosting PowerServer allows only %1 CPU(s), but %2 CPUs are detected.

Possible Cause

The CPU number on the machine exceeds the maximum allowed number in the license file.

Solution

Please provide us the following information to fix this issue.

Click the Activate button to generate the license.activation.bin file and send it to us.
Provide us the license.appeon file you are currently using.
Provide us the screenshot of the Licensing page.
Provide us the appeonserver.log and appeonerror.log files, here is the article stating how to generate the log files: http://support.appeon.com/index.php?/Knowledgebase/Article/View/50/11/what-you-can-provide-to-us-for-further-debugging-when-you-run-into-the-appeon-server-related-issues.

Error 14017

Priority 2

Error Message

The Server ID in your license does not match with the one on your server.

Possible Cause

The server ID does not match the one binding in the license file.

Solution

Case 1: If you transfer to different machine, then you need to follow up the license re-activation process to provide us the license.reactivation.bin file which is generated on the old machine as well as the license.activation.bin file generated on the new machine, after that we will generate the correct permanent license file for your new machine. Here is the help documentation stating the license re-activation process for your reference: http://docs.appeon.com/pb2019r3/server_configuration_guide_for_net/Product_Activation.html.

Case 2: If you just use the virtual machine which cause the server ID to change or change the network card, then please provide us the following information to move forward.

Run 'ipconfig /all' on your machine and then provide us the result.
Go to the Licensing page and click the Activate button to generate the license.activation.bin file and send it to us.

Error 14018

Priority 2

Error Message

Your PowerServer %1-day trial license expired on %2.

Possible Cause

The trial license has expired.

Solution

Please contact Appeon and purchase a proper license.

Error 14019

Priority 2

Error Message

Cannot connect to AppeonDB. PowerServer failed to start.

Possible Cause

AppeonDB failed to start.

Solution

Restart PowerServer and check whether errors are reported in the log files.

Error 14020

Priority 2

Error Message

The application cannot be run because the product license information cannot be found.

Possible Cause

Cannot find the license file.

Solution

Check that the license file exists in the PowerServer installation directory.

Error 14022

Priority 2

Error Message

Server failed to start, because the CPU number exceeds the license limit.

Possible Cause

The CPU number exceeds the maximum allowed number in the license.

Solution

Purchase a new license with larger CPU number.

Error 14024

Priority 2

Error Message

The license of the remote PowerServer does not match with the license of the local server.

Possible Cause

The license files on the remote PowerServer and the local PowerServer do not match.

Solution

Replace the license on the remote PowerServer with the license on the local server.

Error 14025

Priority 2

Error Message

The license in use is for the %1 platform.

Possible Cause

Use an incorrect license file. For example, use a license for UNIX in Windows.

Solution

Please contact Appeon to have the correct license.

Error 14026

Priority 2

Error Message

The license is not for the application server %1.

Possible Cause

Use an incorrect license file.

Solution

Please contact Appeon for the correct license.

Error 14027

Priority 2

Error Message

The current operating system is %1. But the license is for the platform other than Windows, Solaris, AIX, Red-Linux, HP-Unix.

Possible Cause

The current platform is Windows, Solaris, AIX, Red-Linux, or HP-Unix. But the license is not for this platform.

Solution

Please contact Appeon for the correct license.

Error 14028

Priority 2

Error Message

The remote PowerServer is a cluster version.

Possible Cause

The license on the local server is not for cluster version, while the license on the remote PowerServer is for cluster version.

Solution

To use the Appeon cluster functionality, all servers in the cluster must use the same license. You can replace the local license with the remote license, so all servers use the license for cluster version. If you do not want to use the PowerServer cluster functionality, replace the remote license with the local license, so all servers use the license for single server version.

Error 14029

Priority 10

Error Message

The current user has no permission to write the local license file.

Possible Cause

The current login account does not have write permission to files under the system folder.

Solution

Ask the administrator to assign proper rights to the current account or log in to the system using another account with proper rights.

Error 14030

Priority 10

Error Message

The local license file has been destroyed.

Possible Cause

Failed to access the local license file, probably because the file does not exist or the user has no permission to access it.

Solution

Ask the administrator to assign proper rights to the current account or log in to the system using another account with proper rights.

Error 14031 (.NET only)

Priority 1

Error Message

The license data initialize failed.

Possible Cause

Fail to initialize Appeon license file if the proper permission of using .Net framework and IIS server is not set.

Solution

Step 1: Execute the command line in a Windows prompt window:

            C:\WINDOWS\Microsoft.NET\Framework\2.0.**** aspnet_regiis -ga users
            C:\WINDOWS\Microsoft.NET\Framework\2.0.**** aspnet_regiis -i

Step 2: Grant proper rights to the Internet Guest Account and IIS Process Account so to manipulate the Web Root folder.

1. Right click the C:\Inetpub\wwwroot folder, select the Properties items and select the Security tab page;

2. Add IIS_WPG group if it is not listed in the box "Group or user names";

3. Grant Full Control permission to the IIS_WPG group.

Error 14032

Priority 2

Error Message

Failed to obtain the Server ID. Your PowerServer will stop working in % days. Please seek technical support in % days to resolve this issue.

Possible Cause

There are two reasons below:

1. PowerServer failed to find the network interface card address due to the malfunction of the network interface card.

2. The network interface card address and the address in the license file don't match.

Solution

Please check whether the network interface card address and the address in the license file match. If they don't match, please send the network interface card address to Appeon technical support so that they can create a new license for you.

Error 14033

Priority 2

Error Message

Failed to obtain the Server ID. % days remain to fix the problem.

Possible Cause

There are two reasons below:

1. PowerServer failed to find the network interface card address due to the malfunction of the network interface card.

2. The network interface card address and the address in the license file don't match.

Solution

Please check whether the network interface card address and the address in the license file match. If they don't match, please send the network interface card address to Appeon technical support so that they can create a new license for you.

Error 14501

Priority 10

Error Message

System error.

Possible Cause

1. The application configuration is incorrect. 2. The file is corrupt or the disk space is insufficient.

Solution

1. Check that no PowerServer files are missing. Refer to PowerServer Help for instructions if you need to configure the application settings again. 2. Reinstall PowerServer. 3. Check that the available disk space is over 100 M.

Error 14502

Priority 1

Error Message

The specified HTTP header does not exist.

Possible Cause

An incorrect parameter value is specified.

Solution

Verify that the parameter value is correct.

Error 15002

Priority 2

Error Message

Data source name cannot be null.

Possible Cause

Data source name is empty.

Solution

Specify the data source name.

Error 15003

Priority 2

Error Message

Failed to add/modify data source.

Possible Cause

The format of the configuration file for storing the data source information was destroyed.

Solution

Remove the configuration file of the data source.

Error 15004

Priority 2

Error Message

Failed to get the specified data source information.

Possible Cause

The format of the configuration file for storing the data source information was destroyed.

Solution

Remove the configuration file of the data source.

Error 15005

Priority 2

Error Message

Failed to delete the specified data source.

Possible Cause

The format of the configuration file for storing the data source information was destroyed.

Solution

Remove the configuration file of the data source.

Error 15006

Priority 2

Error Message

Failed to refresh the specified data source.

Possible Cause

The format of the configuration file for storing the data source information was destroyed.

Solution

Remove the configuration file of the data source.

Error 15007

Priority 2

Error Message

Failed to get all data source names.

Possible Cause

The format of the configuration file for storing the data source information was destroyed.

Solution

Remove the configuration file of the data source.

Error 15009

Priority 2

Error Message

Failed to add the data source.

Possible Cause

The specified data source settings are incorrect.

Solution

Check that the input data source settings are correct.

Error 15010

Priority 2

Error Message

Failed to modify the data source.

Possible Cause

The specified data source settings are incorrect.

Solution

Check that the input data source settings are correct.

Error 15011

Priority 2

Error Message

Failed to get the specified data source information.

Possible Cause

The specified data source settings are incorrect.

Solution

Check that the input data source settings are correct.

Error 15012

Priority 2

Error Message

Failed to delete the specified data source.

Possible Cause

The specified data source settings are incorrect.

Solution

Check that the input data source settings are correct.

Error 15013

Priority 2

Error Message

Failed to refresh the specified data source.

Possible Cause

The specified data source settings are incorrect.

Solution

Check that the input data source settings are correct.

Error 15016

Priority 2

Error Message

Failed to test the data source.

Possible Cause

The specified data source settings are incorrect.

Solution

Check that the input data source settings are correct.

Error 15020

Priority 2

Error Message

Failed to get all components from the specified package.

Possible Cause

Exceptions occurred when getting all components from the specified package. PowerServer may encounter runtime errors.

Solution

1. Check that the input package settings are correct. 2. Contact the PowerServer administrator and make sure that PowerServer runs correctly.

Error 15021

Priority 2

Error Message

Failed to delete the specified component.

Possible Cause

Exceptions occurred when deleting the specified component. PowerServer may encounter runtime errors.

Solution

1. Check that the input component settings are correct. 2. Contact the PowerServer administrator and make sure that PowerServer runs correctly.

Error 15022

Priority 2

Error Message

Failed to import the AEM configuration settings.

Possible Cause

1) ApplicationsConfig does not exist. 2) ApplicationsConfig has an incorrect file format. 3) ApplicationsConfig does not contain the settings for the current application.

Solution

Check that the application is correctly configured in AEM.

Error 15023

Priority 2

Error Message

Failed to export the AEM configuration settings.

Possible Cause

1) ApplicationsConfig does not exist. 2) ApplicationsConfig has an incorrect file format. 3) ApplicationsConfig does not contain the settings for the current application.

Solution

Check that the application is correctly configured in AEM.

Error 15051

Priority 2

Error Message

Failed to add the transaction object.

Possible Cause

1. ApplicationsConfig has an incorrect XML format. 2. ApplicationsConfig does not contain the information for the current application.

Solution

1. Check that the ApplicationsConfig file is correct and intact. If the file is corrupt, delete it. 2. Provide the log files to the Appeon technical support engineers.

Error 15052

Priority 2

Error Message

Failed to delete the transaction object.

Possible Cause

ApplicationsConfig has an incorrect XML format.

Solution

1. Check that the ApplicationsConfig file is correct and intact. If the file is corrupt, delete it. 2. Provide the log files to the Appeon technical support engineers.

Error 15053

Priority 2

Error Message

Failed to modify the transaction object.

Possible Cause

1. ApplicationsConfig has an incorrect XML format. 2. ApplicationsConfig does not contain the information for the current application.

Solution

1. Check that the ApplicationsConfig file is correct and intact. If the file is corrupt, delete it. 2. Provide the log files to the Appeon technical support engineers.

Error 15054

Priority 2

Error Message

Failed to get all transaction objects.

Possible Cause

ApplicationsConfig has an incorrect XML format.

Solution

1. Check that the ApplicationsConfig file is correct and intact. If the file is corrupt, delete it. 2. Provide the log files to the Appeon technical support engineers.

Error 15055

Priority 2

Error Message

Failed to get the specified transaction object information.

Possible Cause

ApplicationsConfig has an incorrect XML format.

Solution

1. Check that the ApplicationsConfig file is correct and intact. If the file is corrupt, delete it. 2. Provide the log files to the Appeon technical support engineers.

Error 1004

Priority 2

Error Message

The time period of the license is invalid.

Possible Cause

The license is set with invalid time period.

Solution

Ask your administrator to assign your user account with another valid license.

Error 1005

Priority 2

Error Message

The license has expired.

Possible Cause

The license has expired.

Solution

Ask your administrator to renew the license or assign your user account with another valid license.

Error 1007

Priority 2

Error Message

You are not logged in.

Possible Cause

Your user account is not logged in or activated.

Solution

Log in with your user account in AEM. If your user account is not assigned with a license, ask your administrator to assign your user account with a license on the Appeon web site.

Error 1008

Priority 2

Error Message

The current license has been disabled.

Possible Cause

The current license is disabled by the license administrator.

Solution

Ask your administrator to enable the license on the Appeon web site; or log in with a different user account.

Error 1009

Priority 2

Error Message

Cannot find a valid license.

Possible Cause

Your user account is not assigned with a license by the license administrator.

Solution

Ask your administrator to assign your user account with a license on the Appeon web site.

Error 16100

Priority 1

Error Message

Error in invoking the PowerBuilder license DLL. Method: {0}

Possible Cause

Exceptions occur when a method is called.

Solution

Restart the application server where PowerServer server is installed; or contact Appeon Support for assistance.

Error 16101

Priority 2

Error Message

The offline license has expired. Please renew it.

Possible Cause

The offline license has expired.

Solution

Ask your administrator to renew the license on the Appeon web site.

Error 16102

Priority 2

Error Message

Error in checking license data: {0}

Possible Cause

Exceptions occur when the license data is checked.

Solution

Fix the license data according to the error message or contact Appeon Support for assistance.

Error 16105

Priority 2

Error Message

This PowerServer is not activated.

Possible Cause

No user has logged into and activated this PowerServer.

Solution

Log in and activate this PowerServer with the user account that is assigned with a license.

Error 16106

Priority 2

Error Message

The license config file does not exist. Please activate PowerServer in AEM with either an online or offline license.

Possible Cause

The license configuration file does not exist.

Solution

Restart the application server where PowerServer server is installed; and then activate PowerServer again.

Error 16107

Priority 2

Error Message

License account or password is empty.

Possible Cause

License account or password is empty.

Solution

Input the correct user account and password to log in.

Error 16116

Priority 2

Error Message

No network connection.

Possible Cause

AEM cannot connect with Internet.

Solution

Fix the network connection or use a proxy server that can connect with Internet.

Error 16124

Priority 2

Error Message

License module must be initialized first.

Possible Cause

Errors occur when initializing the license module.

Solution

Restart the application server where PowerServer server is installed.

Error 16133

Priority 2

Error Message

You have lost connection to the license server (https://api.appeon.com) for more than {0} days. PowerServer has stopped functioning. Please re-establish your network connection to resume the functionality of PowerServer.

Possible Cause

PowerServer has disconnected from Internet for more than 5 days, so license is locked.

Solution

Fix the network connection or use a proxy server that can connect with Internet.

Error 20000

Priority 2

Error Message

The Server ID in your license does not match with the one on your server.

Possible Cause

The Server ID in the license file is not the same as the one on the server.

Solution

Contact Appeon Support to generate a new license file with the correct Server ID.

Error 20001

Priority 2

Error Message

RegMultiString, RegLink and RegBinary data are unsupported in the server execution mode of RegistryGet. For more help, please consult the PowerServer Help.

Possible Cause

RegMultiString, RegLink and RegBinary data are unsupported in the server execution mode of RegistryGet.

Solution

Use the supported data types, such as RegString, RegExpandString, RegULong, RegULongBigEndian, to save the data.

Error 20002

Priority 2

Error Message

RegMultiString data are unsupported in the client execution mode of RegistryGet. For more help, please consult the PowerServer user documents.

Possible Cause

RegMultiString data are not supported in the client execution mode of RegistryGet.

Solution

Use the supported data types, such as RegString, RegExpandString, RegULong, RegULongBigEndian, or RegBinary, to save the data.

Error 20003

Priority 2

Error Message

RegMultiString data are unsupported in the client execution mode of RegistrySet. For more help, please consult the PowerServer user documents.

Possible Cause

RegMultiString data are not supported in the client execution mode of RegistrySet.

Solution

Use the supported data types, such as eRegString, eRegExpandString, eRegULong, eRegULongBigEndian, eRegBinary, or RegLink to save the data.

Error 20004

Priority 2

Error Message

The thread pool settings cannot have a value less then zero or a value exceeding the maximum allowed number. For more help, please consult the PowerServer user documents.

Possible Cause

The thread number configured in AEM is invalid.

Solution

Configure a proper thread number in AEM. Refer to PowerServer Configuration Guide for help.

Error 20005

Priority 2

Error Message

The specified variable type is incorrect. For more help, please consult the PowerServer user documents.

Possible Cause

When creating the proxy object, the variable type is not set to CORBA or NonVisualObject.

Solution

Specify the variable type to CORBA or NonVisualObject when creating the proxy object.

Error 20006

Priority 2

Error Message

The class name of the object to be created does not exist. For more help, please consult the PowerServer user documents.

Solution

1) Check that class name exists. 2) Check that the component was successfully deployed to the server.

Error 20007

Priority 2

Error Message

No transaction object is specified when declaring cursor or stored procedure. For more help, please consult the PowerServer user document.

Possible Cause

1) The transaction object is not specified in the PowerBuilder source code. 2) The PowerServer Toolkit deployment contains errors.

Solution

Priority 2

Error Message

The application cannot be run because the current server license only supports mobile applications.

Possible Cause

The license supports the mobile applications, but not the Web applications.

Solution

Upgrade the license or change the license edition.

Prev	Up	Next
Error 20000-20042	Home	Technical Support

PowerServer Troubleshooting GuideErrors

Error 00001

Error 00002

Error 00003

Error 00004

Error 00005

Error 00006

Error 00007

Error 00008

Error 00009

Error 00010

Error 00011

Error 00012

Error 00013

Error 00014

Error 00015

Error 00016

Error 00017

Error 00018

Error 00019

Error 00020

Error 00021

Error 00022

Error 00023

Error 00024

Error 00025

Error 00026

Error 00027

Error 00028

Error 00029

Error 00030

Error 00031

Error 00032

Error 00051

Error 00052

Error 00053

Error 00054

Error 00055

Error 00056

Error 00057

Error 00058

Error 00059

Error 00060

Error 00901

Error 00902

Error 00904

Error 00905

Error 00906

Error 01001

Error 01002

Error 01003

Error 01004

Error 01005

Error 01006

Error 02002

Error 02003

Error 02004

Error 02005

Error 02006

Error 02007

Error 02010

Error 02011

Error 02012

Error 02013

Error 03001

Error 03002

Error 03003

Error 03004

Error 03501

Error 03502

Error 03503

Error 03504

Error 03505

Error 03506

Error 03507

Error 03508

Error 03509

Error 03510

Error 03511

PowerServer Troubleshooting Guide
Errors