Solutions

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
Error 04001
Error 04002
Error 04003
Error 04004
Error 04005
Error 04006
Error 09999
Error 10001
Error 10014
Error 10015
Error 10016
Error 10017
Error 10501
Error 10502
Error 10504
Error 10505
Error 10506
Error 10507
Error 10508
Error 10999
Error 11006
Error 11007
Error 11008
Error 11009
Error 11010
Error 11011
Error 11012
Error 11013
Error 11014
Error 11015
Error 11016
Error 11017
Error 11020
Error 11021
Error 11022
Error 11023
Error 11024
Error 11025
Error 11026
Error 11027
Error 11028
Error 11029
Error 11502
Error 11503
Error 11509
Error 11512
Error 11514
Error 11515
Error 11516
Error 11517
Error 11519
Error 11520
Error 11521
Error 11522
Error 11523
Error 11524
Error 12001
Error 12008
Error 12009
Error 12010
Error 12011
Error 12012
Error 12013
Error 12015
Error 12016
Error 12017
Error 12018
Error 12019
Error 12020
Error 12021
Error 12025
Error 12026
Error 12027
Error 12028
Error 12029
Error 12030
Error 12501
Error 12502
Error 12503
Error 12504
Error 12505
Error 12506
Error 12507
Error 12508
Error 12509
Error 12510
Error 12511
Error 13001
Error 13002
Error 13003
Error 13004
Error 13005
Error 13006
Error 13007
Error 13008
Error 13009
Error 13010
Error 13011
Error 13012
Error 13013
Error 13014
Error 13015
Error 13016
Error 13017
Error 13018
Error 13019
Error 13020
Error 13021
Error 13022
Error 13023
Error 13024
Error 13025
Error 13026
Error 13027
Error 13028
Error 14001
Error 14002
Error 14003
Error 14004
Error 14005
Error 14006
Error 14009
Error 14010
Error 14016
Error 14017
Error 14018
Error 14019
Error 14020
Error 14022
Error 14024
Error 14025
Error 14026
Error 14027
Error 14028
Error 14029
Error 14030
Error 14031 (.NET only)
Error 14032
Error 14033
Error 14501
Error 14502
Error 15002
Error 15003
Error 15004
Error 15005
Error 15006
Error 15007
Error 15009
Error 15010
Error 15011
Error 15012
Error 15013
Error 15016
Error 15020
Error 15021
Error 15022
Error 15023
Error 15051
Error 15052
Error 15053
Error 15054
Error 15055
Error 1004
Error 1005
Error 1007
Error 1008
Error 1009
Error 16100
Error 16101
Error 16102
Error 16105
Error 16106
Error 16107
Error 16116
Error 16124
Error 16133
Error 20000
Error 20001
Error 20002
Error 20003
Error 20004
Error 20005
Error 20006
Error 20007
Error 20008
Error 20009
Error 20010
Error 20011
Error 20012
Error 20013
Error 20014
Error 20015
Error 20016
Error 20017
Error 20018
Error 20019
Error 20020
Error 20021
Error 20023
Error 20024
Error 20025
Error 20026
Error 20027
Error 20028
Error 20029
Error 20030
Error 20031
Error 20032
Error 20033
Error 20034
Error 20035
Error 20036
Error 20037
Error 20038
Error 20040
Error 20041
Error 20042

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

When configuring PowerServer profile, no PowerServer port is provided.

Error 00004

Priority1

Error Message

PowerServer port is out of the valid range.

Possible Cause

The specified PowerServer port is not between 1 and 65535.

Error 00005

Priority1

Error Message

Failed to parse the source code. Line: %1

Possible Cause

The PBL list added to the Appeon configuration is incomplete, or the object is 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 > Appeon Profile Configuration window is complete. 3) Verify that no reference is made to the object defined in PBD.

Error 00006

Priority1

Error Message

AEM URL is empty.

Possible Cause

When configuring the PowerServer profile, the AEM URL is empty.

Solution

Please input the correct URL.

Error 00007

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

Transaction object name is empty.

Possible Cause

When configuring the transaction object, the transaction object name is not provided.

Solution

Please input the correct name of the transaction object.

Error 00012

Priority1

Error Message

No database type is specified for the transaction object.

Possible Cause

When configuring the transaction object, no database type is specified for it.

Error 00013

Priority1

Error Message

No data source is specified for the transaction object.

Possible Cause

When configuring the transaction object, no data source is assigned to it.

Error 00014

Priority1

Error Message

Web server profile name is empty.

Possible Cause

When configuring the Web server profile, no profile name is specified.

Error 00015

Priority1

Error Message

Web server name is empty.

Possible Cause

When configuring the Web server profile, no machine name or IP address of the Web server is specified.

Error 00016

Priority1

Error Message

Web server port is empty.

Possible Cause

Web server port is not specified when configuring the Web server profile.

Solution

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

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

Error 00020

Priority1

Error Message

The Web server profile name already exist.

Possible Cause

When configuring the Web server profile, the provided profile name already exists.

Error 00021

Priority1

Error Message

FTP Port is incorrect.

Possible Cause

The FTP Port was not specified when configuring the Web server profile.

Solution

Specify a valid FTP port.

Error 00022

Priority1

Error Message

FTP Port is invalid.

Possible Cause

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

Solution

Specify a valid port ranging from 0~65535.

Error 00023

Priority1

Error Message

No selected ODBC data source.

Possible Cause

No data source is selected when configuring the ODBC interface.

Solution

Select a data source from the list.

Error 00024

Priority1

Error Message

Failed to log into application server.

Possible Cause

The user name and password used to connect to the application server are incorrect.

Solution

Provide the correct user name and password.

Error 00025

Priority2

Error Message

Failed to get detailed information of the specified cache.

Possible Cause

Failed to get the detailed information of the specified cache from the application server.

Error 00026

Priority2

Error Message

Failed to add the transaction object.

Possible Cause

Failed to add a transaction object in the application server.

Error 00027

Priority 2

Error Message

Failed to edit the transaction object.

Possible Cause

Failed to edit a transaction object in the application server.

Error 00028

Priority 2

Error Message

Failed to delete the data source.

Possible Cause

Failed to delete a data source in the application server.

Error 00029

Priority 2

Error Message

Failed to add the data source.

Possible Cause

Failed to add a data source in the application server.

Error 00030

Priority 2

Error Message

Failed to edit the data source.

Possible Cause

Failed to edit a data source in the application server.

Error 00031

Priority 1

Error Message

Duplicate transaction object name.

Possible Cause

A transaction object with the same name already exists.

Solution

Save the new transaction object with a different name.

Error 00032

Priority 2

Error Message

Failed to get the cache list from the application server.

Possible Cause

1) The network connection is unstable. 2) The application server shuts down.

Error 00051

Priority 1

Error Message

Failed to get object %1 from the memory stack.

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 object is defined in the PBD file, which causes the object to be ruined.

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 | Appeon Profile Configuration window is complete. 3) Verify that the script makes no reference to the object defined in the PBD file.

Error 00052

Priority 1

Error Message

The child object %1 of %2 cannot find the parent object %3.

Possible Cause

The PBL list added to the PowerServer Toolkit configuration 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 | Appeon Profile Configuration window is complete. 3) Verify that the script makes no reference to the object defined in the PBD file.

Error 00053

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 | Appeon 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

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 > Appeon Profile Configuration window is complete. 3) Verify that the script makes no reference to the object defined in the PBD file.

Error 00056

Priority 2

Error Message

Cannot find the function object in the template using event ID %1.

Possible Cause

The event ID is not defined in the PowerServer Toolkit template.

Error 00057

Priority 1

Error Message

Failed to get PowerServer information.

Possible Cause

1) PowerServer is not started. 2) PowerServer Profile was configured incorrectly.

Solution

1) Start PowerServer. 2) Verify that the PowerServer Profile is configured correctly.

Error 00058

Priority 1

Error Message

Cannot find %1's ancestor object %2.

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

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 > Appeon Profile Configuration window is complete. 3) Verify that the script makes no reference to the object defined in the PBD file.

Error 00059

Priority 1

Error Message

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

Possible Cause

Cache name can only contain a combination of letters, underscores ("_"), dot ("."), and numbers.

Error 00060

Priority 1

Error Message

The database port for the data source exceeds the valid range.

Possible Cause

The port must range from 0 to 65535.

Error 00901

Priority 1

Error Message

Cannot connect to DSN. The database server is %1.

Possible Cause

Failed to connect to the database configured for the application.

Solution

Configure the database connection settings correctly and make sure that the connection test is successful.

Error 00902

Priority 1

Error Message

Failed to get syntax of %1 DataWindow in %2.

Possible Cause

1) There are syntax errors in DataWindow. 2) The PBL file version does not match the specified PowerBuilder version.

Solution

1) Full build the application in the PowerBuilder IDE. 2) Fix the syntax errors in DataWindow. 3) Verify that the PBL file version is the same as the specified PowerBuilder version.

Error 00904

Priority 1

Error Message

Failed to load the file: %1.

Possible Cause

1) The file format is corrupt or the file is incomplete. 2) The login account has no read permission on the file.

Solution

1) Delete the file and re-deploy the application. 2) Assign the read permission to the current login user.

Error 00905

Priority 1

Error Message

Failed to save the file: %1.

Possible Cause

1) No disk space is available. 2) The current login user has no write permission on the file.

Solution

1) Prepare enough disk space. 2) Assign the write permission to the current login user.

Error 00906

Priority 1

Error Message

You need to configure a proper database connection for the application before deploying it.

Possible Cause

The application connects to databases and uses DataWindows, but no database connection is configured.

Solution

Configure a proper DB profile in the application profiles configuration page.

Error 01001

Priority 1

Error Message

Failed to generate %1 %2.

Possible Cause

This error is caused by another error which occurred previously.

Solution

Please check the log file and fix the previous error.

Error 01002

Priority 1

Error Message

It is unsupported to generate %1 %2.

Possible Cause

PowerBuilder source code contains some Appeon unsupported features.

Solution

Remove or workaround the Appeon unsupported features in the source code.

Error 01003

Priority 1

Error Message

Failed to analyze %1 %2.

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

1) Verify that the PBL list added to the PowerServer Toolkit | Appeon Profile Configuration window is complete. 2) Verify that the script makes no reference to the object defined in the PBD file.

Error 01004

Priority 1

Error Message

It is unsupported to analyze %1 %2.

Possible Cause

The PowerBuilder object contains Appeon unsupported features.

Solution

View the unsupported features in the UFA report and remove or workaround them.

Error 01005

Priority 1

Error Message

Configuration for Web service object (%1) is incorrect.

Possible Cause

1) The Web service was not configured. 2) The WSDL file, service or port for the Web server was configured incorrectly.

Solution

Specify the correct settings for Web service, including the WSDL file, service and port.

Error 01006

Priority 1

Error Message

Error in loading XML file %1.

Possible Cause

The user erroneously modified or deleted the RuleTemplate.xml file under the PowerServer Toolkit directory.

Solution

Please reinstall PowerServer Toolkit.

Error 02002

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 Appeon 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/2008 R2/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

PowerServer Toolkit is corrupted. Please reinstall PowerServer Toolkit.

Error 02011

Priority 1

Error Message

Unable to find the destination directory.

Possible Cause

Cannot write to the Web server. Please contact the administrator and grant proper rights to the login user.

Error 02012

Priority 1

Error Message

Cannot connect to PowerServer: %1.

Possible Cause

1) The server name, port or password is incorrect. 2) The Deployment Security setting in AEM is enabled.

Solution

Please check that the PowerServer server name and port. If deployment security in AEM is enabled, you must also check the deployment username and password.

Error 02013

Priority 1

Error Message

Connection to PowerServer is terminated.

Possible Cause

If the number of DataWindows exceeds 4000, deploying the DataWindow syntax under Windows XP may encounter connection failure. PowerServer Toolkit will resume the connection after this error and the running of the Web application will not be affected.

Solution

Reducing the number of DataWindows to less than 2000 can totally eliminate this problem.

Error 03001

Priority 1

Error Message

File %1 is invalid.

Possible Cause

The file is destroyed or the file format is incorrect.

Solution

1) Re-deploy the application using the "Full Application Deployment" option in PowerServer Toolkit. 2) Reinstall PowerServer Toolkit.

Error 03002

Priority 1

Error Message

File %1 is not found.

Possible Cause

The specified file does not exist.

Solution

1) Re-deploy the application using the "Full Application Deployment" option in PowerServer Toolkit. 2) Reinstall PowerServer Toolkit.

Error 03003

Priority 1

Error Message

Invalid registry information!

Possible Cause

The registry information is incorrect. For example, the format is incorrect, or the registry information is incomplete.

Solution

Reinstall PowerServer Toolkit.

Error 03004

Priority 1

Error Message

Flow module is already loaded.

Possible Cause

The flow module cannot be loaded repeatedly.

Solution

Close the program that is loading the flow module and then start the program again.

Error 03501

Priority 1

Error Message

Cannot find the PBL file.

Possible Cause

The PBL files have been deleted or moved to a different location.

Solution

Locate the correct PBL files and re-deploy the application.

Error 03502

Priority 1

Error Message

PBL files have been changed. Please re-deploy the application under the debug mode.

Possible Cause

The PBL files on the local machine have been changed. But the files in the Web server are not changed correspondingly and the debug information is not updated with these changes.

Solution

Re-deploy the application under the debug mode.

Error 03503

Priority 1

Error Message

Files in the Web server are not updated. Please re-deploy the application under the debug mode.

Possible Cause

The PBL files on the local machine have been changed. But the files in the Web server are not changed correspondingly and the debug information is not updated with these changes.

Solution

Re-deploy the application under the debug mode.

Error 03504

Priority 1

Error Message

The default Web server is not started. Please start Web server.

Possible Cause

Web server is not started.

Solution

Start Web server.

Error 03505

Priority 1

Error Message

The default PowerServer is not started. Please start PowerServer.

Possible Cause

PowerServer is not started.

Solution

Start PowerServer.

Error 03506

Priority 1

Error Message

Web server configuration settings error. Please check and correct the settings.

Possible Cause

The port or name settings in the Web server configuration file is incorrect. Please check the settings and test them.

Solution

Correct the configuration settings for the Web server.

Error 03507

Priority 1

Error Message

PowerServer configuration settings error. Please check and correct the settings.

Possible Cause

The port or name settings in the PowerServer configuration file is incorrect. Please check the settings and test them.

Solution

Correct the configuration settings for the PowerServer.

Error 03508

Priority 1

Error Message

No access rights to the Web server. Please check the Web server permission settings.

Possible Cause

The current user account cannot write to the Web server. Please use a different user account or grant Write permission to the current user.

Solution

Enable the Write permission in the Web server.

Error 03509

Priority 1

Error Message

One or more files do not match. Please re-deploy the application under the debug mode.

Possible Cause

The debug information on the local machine do not match with the deployed file or other unknown errors.

Solution

Deploy the application again under the debug mode.

Error 03510

Priority 1

Error Message

Another PowerServer Toolkit tool is running.

Possible Cause

When Appeon Debugger is started, it detects that another PowerServer Toolkit tool is running.

Solution

Close the other PowerServer Toolkit tool and start the Appeon Debugger again.

Error 03511

Priority 1

Error Message

The application deployed in the Encrypted mode cannot be debugged.

Possible Cause

When the application is deployed in the Encrypted mode, it cannot be debugged using the Appeon Debugger.

Solution

Select the Debug mode and deploy the application again.

Error 04001

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

The Web server information in the ADTConfig.xml file is ruined.

Error 04004

Priority 1

Error Message

Cannot get PowerServer information from the ADTConfig.xml file.

Possible Cause

The PowerServer information in the ADTConfig.xml is ruined.

Error 04005

Priority 10

Error Message

Failed to open Deploy.dll, hence failed to load the deploy module.

Possible Cause

The Deploy.dll file does not exist or the file is corrupt.

Solution

Replace with the correct Deploy.dll file. Or reinstall PowerServer Toolkit.

Error 04006

Priority 10

Error Message

Failed to initialize the deploy module.

Possible Cause

The EonDeploy.dll file is not found or the file is corrupt.

Solution

Reinstall PowerServer Toolkit.

Error 09999

Priority 1

Error Message

Possible Cause

The error messages returned from Windows OS, such as, Insufficient storage space, Insufficient memory, etc.

Error 10001

Priority 1

Error Message

Cannot find the transaction object named %1 in the current session.

Possible Cause

The transaction object is not configured in AEM.

Solution

Configure the transaction object in AEM. Refer to PowerServer Configuration Guide for detailed instructions.

Error 10014

Priority 2

Error Message

Internal error. Please contact the system administrator.

Possible Cause

1) The network environment is unstable, causing data to be incomplete and data protocol errors. 2) Other unknown errors.

Solution

Contact the administrator and check the PowerServer log files for detailed error information. Or send the log files to Appeon technical support engineers.

Error 10015

Priority 2

Error Message

Error in connecting to AppeonDB.

Possible Cause

The JDK version is not 1.3 or above.

Solution

Check that the JDK version is 1.3 or above.

Error 10016

Priority 2

Error Message

The running PowerServer does not support Web applications deployed in this version (version = %1).

Possible Cause

The PowerServer version and PowerServer Toolkit version used to deploy the Web application is not the same.

Solution

1) Use the PowerServer Toolkit of the same version to deploy the application and use the PowerServer of the same version to run it. 2) Reinstall Appeon 5.0 for PowerBuilder.

Error 10017

Priority 2

Error Message

Failed to connect to data source: %1. The cause is: %2.

Possible Cause

1) The database driver does not exist or the version is incorrect. 2) The settings for connection URL or the driver are incorrect. 3) The user name and password is incorrect.

Solution

1) Check that the database driver exists and the version is compatible. 2) Check in the user documents provided by the database driver vendor that the settings for URL and driver are correct. 3) Check that the user name and password are correct. Specially check the cases and spaces.

Error 10501

Priority 2

Error Message

Session is terminated by the Appeon system.

Possible Cause

The session has timed out. The session is inactive for the specified amount of time.

Solution

Specify a proper timeout period in AEM > Application > Timeout settings. A proper timeout period would be 1.5 to 3 times of the operation interval.

Error 10502

Priority 2

Error Message

Session is terminated by AEM.

Possible Cause

The session is deleted in AEM by the system administrator.

Solution

Click Refresh in the IE toolbar and log in to the application again.

Error 10504

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

Appeon 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 Appeon 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 Appeon configuration files!

Possible Cause

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

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 11011

Priority 0

Error Message

Cannot find the file: %1.

Possible Cause

The specified file does not exist on the server.

Error 11012

Priority 0

Error Message

An exception occurred when denying write access to the file: %1.

Possible Cause

This is a rarely occurred exception caused by enabling the Java security.

Solution

Please send the PowerServer log files to the Appeon technical support engineers.

Error 11013

Priority 1

Error Message

A fatal IOException occurred when writing %1 to the local disk.

Possible Cause

An IOException occurred when reading or writing the specified file.

Solution

1) Check that the specified file is not read-only. If it is read-only, reset it. 2) Please send the log files to the Appeon technical support engineers.

Error 11014

Priority 0

Error Message

An unexpected exception occurred and caused failure to write Appeon configuration files to the local disk!

Possible Cause

An unknown error occurred when writing the specified file to the local disk.

Solution

Please send the PowerServer log files to the Appeon technical support engineers.

Error 11015

Priority 1

Error Message

A fatal IOException occurred when communicating with servlet I/O.

Possible Cause

Cannot have I/O communication with the remote server through HTTP.

Solution

1) Check that the server is running and can be connected. 2) Check that PowerServer residing in the server is started. 3) Send the log files on the local machine and the remote server to the Appeon technical support engineers.

Error 11016

Priority 0

Error Message

An unexpected exception occurred and caused failure to read the local Appeon configuration files!

Possible Cause

An unknown error occurred when reading the local configuration file.

Solution

Please send the PowerServer log files to the Appeon technical support engineers.

Error 11017

Priority 1

Error Message

An IOException occurred when reading the file: %1.

Possible Cause

An IOException occurred when reading the local configuration file.

Solution

Please send the PowerServer log files to the Appeon technical support engineers.

Error 11020

Priority 0

Error Message

An error occurred when synchronizing the method: %1. The remote server called is: %2.

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 work correctly, send the log files on the local and the remote servers to the Appeon technical support engineers.

Error 11021

Priority 0

Error Message

An unexpected exception occurred and caused failure to synchronize the method: %1.

Possible Cause

An unknown error occurred when synchronizing the AEM configuration settings on the local PowerServer to the remote PowerServer.

Solution

Send the PowerServer log files to the Appeon technical support engineers.

Error 11022

Priority 1

Error Message

A fatal IOException occurred when synchronizing method: %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 work correctly, send the log files on the local and the remote servers to the Appeon technical support engineers.

Error 11023

Priority 0

Error Message

A ClassNotFoundException occurred when synchronizing method: %1.

Possible Cause

Cannot construct the object by using the stream from Servlet.

Solution

Send the PowerServer log files to the Appeon technical support engineers.

Error 11024

Priority 0

Error Message

An unexpected exception occurred and caused failure to synchronize method: %1.

Possible Cause

An unknown error occurred when synchronizing sessions on the local PowerServer from the remote PowerServers.

Solution

Send the PowerServer log files to the Appeon technical support engineers.

Error 11025

Priority 1

Error Message

A fatal IOException occurred when calling the specified 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 work correctly, send the log files on the local machine and the remote server to the Appeon technical support engineers.

Error 11026

Priority 0

Error Message

An unexpected exception occurred and caused the ClusterNotify thread to stop!

Possible Cause

An unknown error terminated the HTTP communication.

Solution

Send the PowerServer log files to the Appeon technical support engineers.

Error 11027

Priority 1

Error Message

An unexpected exception occurred and resulted in failure to retrieve status of the server: %1.

Possible Cause

An unknown exception caused the failure to get the server status.

Solution

Please send PowerServer log files to the Appeon technical support engineers for in-depth investigation.

Error 11028

Priority 10

Error Message

Application server connection error!

Possible Cause

The network is disconnected. Or the application server is shut down.

Solution

Check that the network can be connected, and application server can be accessed.

Error 11029

Priority 10

Error Message

PowerServer is in the process to start. Please refresh the page later.

Possible Cause

PowerServer is in the "process to start" state, not in the "running" state.

Solution

Wait until PowerServer turns to the "running" state.

Error 11502

Priority 0

Error Message

Failed to get session information from the specified 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 work correctly, send the log files on the local and the remote machines to the Appeon technical support engineers.

Error 11503

Priority 0

Error Message

Failed to get transaction information from the specified 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) Send the log files on the local machine and the remote server to the Appeon technical support engineers.

Error 11509

Priority 1

Error Message

AEM could not interface with the specified PowerServer. Please verify that your PowerServer is running and that the settings are correct.

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) Send the log files on the local machine and the remote server to the Appeon technical support engineers.

Error 11512

Priority 0

Error Message

Error occurred when updating AEM settings on the local machine. Please read the log for more details.

Possible Cause

1) Cannot update the AEM new settings to the server because the configuration file is read-only. 2) Cannot read or write the file because the file is corrupt.

Solution

1) Remove the Read-only property of files in the %PowerServer%\AEM\config folder. 2) Send the log files to the Appeon technical support engineers.

Error 11514

Priority 0

Error Message

Please enter the IP address or machine name of the PowerServer.

Possible Cause

The IP address or machine name of the PowerServer is not specified.

Solution

Input the IP address or machine name of the PowerServer.

Error 11515

Priority 0

Error Message

Please enter the port number of the PowerServer.

Possible Cause

The port number of the PowerServer is not specified.

Solution

Input the port number of the PowerServer.

Error 11516

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

1. Check that ServerConfig exist 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 12025

Priority 1

Error Message

The selected application %1 does not exist in the PowerServer.

Possible Cause

1) The Web application is undeployed. 2) The Web application is manually removed.

Error 12026

Priority 2

Error Message

The application number exceeds the license limit %1.

Possible Cause

The application number exceeds the maximum number allowed in license.

Solution

Purchase a valid Appeon PowerServer edition.

Error 12027

Priority 0

Error Message

Error: AEMConfig is empty.

Possible Cause

The parameter passed into the method is empty.

Solution

Send the log files to the Appeon technical support engineers.

Error 12028

Priority 1

Error Message

Failed to write the web.config file.

Possible Cause

web.config is corrupt.

Solution

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

Error 12029

Priority 0

Error Message

ConnectionCacheConfig is empty.

Possible Cause

Errors in passing the internal parameters.

Solution

Send the log files to Appeon technical support engineers.

Error 12030

Priority 1

Error Message

Errors in writing the data-source.config file.

Possible Cause

The data-source.config file is corrupt.

Solution

Delete the file if it is corrupt.

Error 12501

Priority 10

Error Message

Post data is null!

Possible Cause

Network exceptions caused the data passed by PowerServer Toolkit to be empty.

Solution

1) Re-deploy the application using PowerServer Toolkit. 2) Check that the network is stable.

Error 12502

Priority 10

Error Message

Session is not found!

Possible Cause

1) The PowerServer Toolkit version is different from the PowerServer version. 2) An invalid user calls the server interface.

Solution

Check that the PowerServer Toolkit version and the PowerServer version are the same.

Error 12503

Priority 10

Error Message

Cannot read the Msg's total!

Possible Cause

The data format passed by PowerServer Toolkit is incorrect, because 1) The network error occurred. 2) The PowerServer Toolkit version and the PowerServer version are different.

Solution

1) Check that the network is stable. 2) Check that the PowerServer Toolkit version and the PowerServer version are the same.

Error 12504

Priority 10

Error Message

Call parseAndExecuteCommand: Cannot read FuctionType!

Possible Cause

The data format passed by PowerServer Toolkit is incorrect, because 1) The network error occurred. 2) The PowerServer Toolkit version and the PowerServer version are different.

Solution

1) Check that the network is stable. 2) Check that the PowerServer Toolkit version and the PowerServer version are the same.

Error 12505

Priority 2

Error Message

Authority is required!

Possible Cause

1) Deployment username and password were not configured in PowerServer Toolkit. 2) The PowerServer Toolkit version and the PowerServer version are different.

Solution

1) Check that the deployment user name and password are correctly configured in PowerServer Toolkit. 2) Check that the PowerServer Toolkit version and the PowerServer version are the same.

Error 12506

Priority 10

Error Message

The input function type (%1) is invalid. No code can be found to match this type!

Possible Cause

The data format passed by PowerServer Toolkit is incorrect, because 1) The network error occurred. 2) The PowerServer Toolkit version and the PowerServer version are different.

Solution

1) Check that the network is stable. 2) Check that the PowerServer Toolkit version and the PowerServer version are the same.

Error 12507

Priority 10

Error Message

%1: Cannot read the parameter count!

Possible Cause

The data format passed by PowerServer Toolkit is incorrect, because 1) The network error occurred. 2) The PowerServer Toolkit version and the PowerServer version are different.

Solution

1) Check that the network is stable. 2) Check that the PowerServer Toolkit version and the PowerServer version are the same.

Error 12508

Priority 10

Error Message

%1: Parameter count mismatch!

Possible Cause

The data format passed by PowerServer Toolkit is incorrect, because 1) The network error occurred. 2) The PowerServer Toolkit version and the PowerServer version are different.

Solution

1) Check that the network is stable. 2) Check that the PowerServer Toolkit version and the PowerServer version are the same.

Error 12509

Priority 10

Error Message

%1: Cannot read the parameter length!

Possible Cause

The data format passed by PowerServer Toolkit is incorrect, because 1) The network error occurred. 2) The PowerServer Toolkit version and the PowerServer version are different.

Solution

1) Check that the network is stable. 2) Check that the PowerServer Toolkit version and the PowerServer version are the same.

Error 12510

Priority 10

Error Message

%1: Cannot read the Parameter value!

Possible Cause

The data format passed by PowerServer Toolkit is incorrect, because 1) The network error occurred. 2) The PowerServer Toolkit version and the PowerServer version are different.

Solution

1) Check that the network is stable. 2) Check that the PowerServer Toolkit version and the PowerServer version are the same.

Error 12511

Priority 10

Error Message

PowerServer is in the process to start. Please refresh the page later.

Possible Cause

PowerServer is starting. AEM cannot be accessed.

Solution

Please wait until PowerServer is started.

Error 13001

Priority 0

Error Message

The original DataWindow parameters are not compatible with the client parameters.

Possible Cause

The number of the original DataWindow parameters is different from the number of the client parameters.

Solution

1) Check that the network can be connected. 2) Check that PowerServer is started and works properly. 3) If the error still occurs, send the Appeon log files and SQL statements to the Appeon technical support engineers.

Error 13002

Priority 0

Error Message

Unsupported stored procedure syntax: %1.

Possible Cause

1) Errors in parsing the stored procedure. 2) The stored procedure syntax is unsupported.

Solution

Make sure that none of the following script is used: 1) execute sp_test to_date( :ls_date ), :li_id ; // Argument contains functions 2) execute sp_test "2001-02-12", :li_id + 100 ; // Argument contains expressions

Error 13003

Priority 10

Error Message

Unsupported PowerBuilder data type: %1.

Possible Cause

Unsupported PowerBuilder data type is used.

Solution

1) Comment out the data type in the PowerBuilder source code. 2) Send the log files to the Appeon technical support engineers.

Error 13004

Priority 0

Error Message

Cannot find the specified argument %1 in the argument list.

Possible Cause

When parsing the argument position in SQL statement, PowerServer Toolkit failed to match the SQL argument name with the argument name passed by the Appeon Xcelerator.

Solution

1) Check that the network is connected. 2) Check that PowerServer is started and works properly. 3) If the error still occurs, send the Appeon log files and SQL statements to the Appeon technical support engineers.

Error 13005

Priority 0

Error Message

Stored procedure syntax cannot be empty or null.

Possible Cause

The stored procedure syntax passed by Appeon Xcelerator is empty or null.

Solution

Check whether the stored procedure is empty in the PowerBuilder source code. If it is empty, it must be caused by an Appeon internal error, please send the Appeon log files and SQL statements to the Appeon technical support engineers.

Error 13006

Priority 0

Error Message

Failed to analyze the stored procedure syntax, due to %1.

Possible Cause

The stored procedure syntax is invalid or the syntax format is incorrect.

Solution

1) Verify that the stored procedure syntax is correct 2) Verify that the stored procedure is supported by Appeon.

Error 13007

Priority 0

Error Message

Register parameter error: index = %1, jdbcType = %2, value = %3.

Possible Cause

The unsupported data type causes failure to register the parameter.

Solution

1) Check that the parameter type is supported by Appeon. 2) If the parameter type is supported, ask the Appeon technical support engineers for help.

Error 13008

Priority 0

Error Message

Client parameter of the UpdateBlob statement cannot be null.

Possible Cause

The network is unstable or the Appeon Serve encountered exceptions which caused data lost.

Solution

1) Check the network is connected. 2) Check that PowerServer is started and works properly. 3) If the error still occurs, send the log files to the Appeon technical support engineers.

Error 13009

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 Appeon 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 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

1) Check that the DB 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 13020

Priority 10

Error Message

Call an unused method.

Possible Cause

Call an obsolete method.

Error 13021

Priority 10

Error Message

Errors in deleting all DataWindows.

Possible Cause

Cannot delete the DataWindow syntax, possibly because 1) The AppeonDB database is closed. 2) The parameter passed by PowerServer Toolkit is incorrect.

Solution

1) Check that the network connection is stable. 2) Check that PowerServer is running and works correctly.

Error 13022

Priority 1

Error Message

The application %1 is being deployed by another user.

Possible Cause

Another user is deploying an application with the same name to the same PowerServer.

Solution

Please wait until the deployment is finished. If you want to terminate the deployment, delete the deployment session in AEM.

Error 13023

Priority 10

Error Message

The value for SqlKey cannot be empty or null.

Possible Cause

The SQL Key passed from the client is empty.

Solution

1) Check that the PowerServer Toolkit deployment process is successful. 2) Check that the network connection is stable. 3) Check that PowerServer is running and works correctly.

Error 13024

Priority 10

Error Message

The value for embedded SQL cannot be empty or null.

Possible Cause

Embedded SQL passed from the client is empty.

Solution

1) Check that the PowerServer Toolkit deployment process is successful. 2) Check that the network is stable. 3) Check that PowerServer is running and works properly.

Error 13025

Priority 2

Error Message

Cannot find the following DataWindow syntax in AppeonDB: ApplicationName =%1 and DataWindowName =%2.

Possible Cause

1) The AppeonDB database is closed. 2) The passed application name and SQLKey is incorrect.

Solution

1) Check that the PowerServer Toolkit deployment is successful. 2) Check that the network is stable. 3) Check that PowerServer is running and works properly. 4) If the error still persists, ask the Appeon technical support engineers for help.

Error 13026

Priority 2

Error Message

Parameter error: the value for %1 is empty or null.

Possible Cause

The first parameter passed from the client is empty. The application name, version type etc. cannot be empty.

Solution

1) Check that the PowerServer Toolkit deployment is successful. 2) Check that the network is stable. 3) Check that PowerServer is running and works properly. 4) If the error still persists, ask the Appeon technical support engineers for help.

Error 13027

Priority 10

Error Message

Unsupported database type. The DBMS code is %1.

Possible Cause

Possibly because the database type dynamically set in PowerScript does not conform to the Appeon conventions.

Solution

Refer to the PowerServer Help for how to dynamically set database type.

Error 13028

Priority 2

Error Message

Blob or Clob variable for UpdataBlob cannot be empty.

Possible Cause

There is no parameter passed from the client or the passed parameter is null when executing the UpdataBlob statement.

Solution

Verify that the argument is not empty or null.

Error 14001

Priority 2

Error Message

License has expired on %1.

Possible Cause

Trial license has expired.

Solution

Please contact Appeon to purchase a proper license.

Error 14002

Priority 2

Error Message

Unable to validate license key "%1". The number has exceeded the limit of your current license.

Possible Cause

The session number has exceeded the limit specified in the license file.

Solution

Kill other active sessions to make the session number within the license limit or contact Appeon to purchase a more powerful edition.

Error 14003

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.

  1. Click the Activate button to generate the license.activation.bin file and send it to us.

  2. Provide us the screenshot of the Licensing page.

  3. 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 Appeon. 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 Appeon.

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 Appeon 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 Appeon file is corrupt.

Solution 1

Please reinstall Appeon.

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 and Windows Server 2008 only.

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.

  1. Click the Activate button to generate the license.activation.bin file and send it to us.

  2. Provide us the license.appeon file you are currently using.

  3. Provide us the screenshot of the Licensing page.

  4. 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://www.appeon.com/support/documents/appeon_online_help/2017/server_configuration_guide_for_j2ee/ch04s03s04.html#Re-activation.

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.

  1. Run 'ipconfig /all' on your machine and then provide us the result.

  2. 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 Appeon 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 Appeon 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 website.

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 website; 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 website.

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 website.

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 Appeon 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 Appeon 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 Appeon 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 Appeon 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 Appeon 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 Appeon user document.

Possible Cause

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

Solution

1) Verify that the transaction object is specified in the PowerBuilder source code. 2) Verify that the PowerServer Toolkit deployment is successful.

Error 20008

Priority 2

Error Message

when declaring cursor or stored procedure, DynamicStagingArea object is not instantiated. For more help, please consult the Appeon user document.

Possible Cause

When using Dynamic SQL Format 4, make sure to instantiate the DynamicStagingArea object before declaring the cursor or stored procedure.

Error 20009

Priority 2

Error Message

You have not been logged into the mail system yet! For more help, please consult the Appeon user document.

Possible Cause

Use functions in the MailSession object when you have not been logged into the system or login failed.

Solution

Use the MailLogon function to log in to the system.

Error 20010

Priority 2

Error Message

Transaction object is not connected. For more help, please consult the Appeon user document.

Possible Cause

Commit or Rollback a transaction when the transaction object is not connected.

Solution

1) Check that the transaction object is connected. 2) Check that the transaction object is configured in AEM.

Error 20011

Priority 2

Error Message

Transaction object is already connected. It cannot be connected again. For more help, please consult the Appeon user document.

Possible Cause

Transaction object has already connected with the database while it is used to connect to the database again.

Solution

Modify the PowerBuilder source code and avoid using a transaction object to connect the database repeatedly.

Error 20012

Priority 2

Error Message

Menu file is invalid. Failed to create the file! For more help, please consult the Appeon user document.

Possible Cause

The menu file is not a valid XML file. It may be corrupt. The Loadxml function failed to work.

Solution

1) Check that the menu file is a valid XML file. 2) Refer to PowerServer Help and verify that no unsupported features are used. 3) Re-generate the application and fix the errors if there are any.

Error 20013

Priority 2

Error Message

Cannot create the WSDLReader object. For more help, please consult the Appeon user document.

Possible Cause

1) SoapToolkit3.0 is not installed. 2) Memory is insufficient.

Solution

1) Install SoapToolkit3.0. 2) Close the other programs to release memory.

Error 20014

Priority 2

Error Message

Failed to load the WSDL file. For more help, please consult the Appeon user document.

Possible Cause

1) The specified WSDL file does not exist. 2) The network is unstable.

Solution

1) Check that the WSDL file is configured before deployment. 2) Check that the WSDL file resides in the corresponding folder on Web server after deployment. 3) Check that the network connection is stable.

Error 20015

Priority 2

Error Message

Cannot get the Service definition from the WSDL file. For more help, please consult the Appeon user document.

Possible Cause

1) The WSDL file content is invalid 2) The WSDL file is incomplete.

Solution

1) Check that the WSDL file is correct. 2) Re-deploy the application using PowerServer Toolkit.

Error 20016

Priority 2

Error Message

Cannot get the Port definition from the WSDL file. For more help, please consult the Appeon user document.

Possible Cause

1) The WSDL file content is invalid. 2) The WSDL file is incomplete.

Solution

1) Check that the WSDL file is correct. 2) Re-deploy the application using PowerServer Toolkit.

Error 20017

Priority 2

Error Message

Cannot get the Operation definition from the WSDL file. For more help, please consult the Appeon user document.

Possible Cause

1) The WSDL file content is invalid. 2) The WSDL file is incomplete.

Solution

1) Check that the WSDL file is correct. 2) Re-deploy the application using PowerServer Toolkit.

Error 20018

Priority 2

Error Message

Cannot get the Part definition from the WSDL file. For more help, please consult the Appeon user document.

Possible Cause

1) The WSDL file content is invalid. 2) The WSDL file is incomplete.

Solution

1) Check that the WSDL file is correct. 2) Re-deploy the application using PowerServer Toolkit.

Error 20019

Priority 2

Error Message

Cannot get the definition of SoapClient from the WSDL file. For more help, please consult the Appeon user document.

Possible Cause

SoapToolkit3.0 was not installed.

Solution

Install SoapToolkit3.0.

Error 20020

Priority 2

Error Message

Failed to initialize SoapClient. For more help, please consult the Appeon user document.

Possible Cause

1) The specified WSDL file does not exist. 2) The specified WSDL file contains incorrect values. 3) The network is unstable.

Solution

1) Check that the WSDL file exists and is correct. 2) Check that the WSDL file is configured before deployment. 3) Check that the network connection is stable.

Error 20021

Priority 2

Error Message

Failed to load DLL file. For more help, please consult the Appeon user document.

Possible Cause

1) The DLL files were not deployed when the application was deployed. 2) The DLL file was not downloaded to the correct location.

Solution

1) Check that the DLL files are configured for deployment before deploying the application. 2) Manually copy the file to the correct location.

Error 20023

Priority 2

Error Message

DataWindow description file does not exist. For more help, please consult the Appeon user document.

Possible Cause

The DataWindow description file does not exist or the DataWindow description file was removed.

Solution

Re-deploy the application and ensure that the DataWindow description file is correctly deployed.

Error 20024

Priority 2

Error Message

Failed to parse the DataWindow description file. For more help, please consult the Appeon user document.

Possible Cause

The DataWindow template is not of the correct version or the DataWindow description file is corrupt.

Solution

Check that the PowerServer Toolkit deployment reports no errors.

Error 20025

Priority 2

Error Message

Failed to apply data memory. For more help, please consult the Appeon user document.

Possible Cause

There are many running programs which occupy large amount of memory. The memory left is insufficient for applying the data memory.

Solution

Close the other programs.

Error 20026

Priority 2

Error Message

Failed to parse SyntaxFromSQL. For more help, please consult the Appeon user document.

Possible Cause

The stored procedure for the corresponding database has not been installed.

Solution

Check that the stored procedure for the corresponding database has been correctly installed before dynamically creating the DataWindow. For detailed instructions, refer to PowerServer Configuration Guide for .NET or PowerServer Configuration Guide for J2EE.

Error 20027

Priority 0

Error Message

Cannot find the image file. For more help, please consult the Appeon user document.

Possible Cause

1) The image file was not correctly uploaded to the server. 2) The image file cannot be found on the specified local directory.

Solution

1) Check that the image file location settings in PowerServer Toolkit are correct and that the image file exists on the local machine. 2) Redeploy the application using PowerServer Toolkit.

Error 20028

Priority 2

Error Message

Print error. For more help, please consult the Appeon user document.

Possible Cause

No printer is installed on the local machine or the default printer does not work.

Solution

Check that the printer works correctly.

Error 20029

Priority 2

Error Message

Failed to create RichText DataWindow. Incorrect information of RichText control in the local system. For more help, please consult the Appeon user document.

Possible Cause

The riched20.dll file does not exist in the system32 folder or riched20.dll is not registered.

Solution

Check that the riched20.dll file exists in the system32 folder and has been registered.

Error 20030

Priority 2

Error Message

Cannot parse the invalid RTF file. For more help, please consult the Appeon user document.

Possible Cause

The format file information in the source code of RichText DataWindow has been manually modified.

Solution

Re-create the RichText DataWindow. Avoid manually changing the RTF file in the source code.

Error 20031

Priority 2

Error Message

Information of InputField in RichText DataWindow is incomplete. For more help, please consult the Appeon user document.

Possible Cause

The InputField information in the source code of RichText DataWindow has been manually modified.

Solution

Re-create the RichText DataWindow. Avoid manually changing the RTF text in the source code.

Error 20032

Priority 2

Error Message

Failed to print RichText DataWindow. No default printer in the local machine. For more help, please consult the Appeon user document.

Possible Cause

No printer is installed on the local machine or no default printer is set.

Solution

Set a printer as the default printer on the local machine.

Error 20033

Priority 2

Error Message

Print Preview failed. No default printer in the local machine. For more help, please consult the Appeon user document.

Possible Cause

No printer is installed on the local machine or no default printer is set.

Solution

Set a printer as the default printer on the local machine.

Error 20034

Priority 2

Error Message

InputField information does not match the DataWindow column information. For more help, please consult the Appeon user document.

Possible Cause

The InputField information in the source code of the RichText DataWindow has been manually modified.

Solution

Re-create the RichText DataWindow and avoid manually changing the InputField name in RTF in the source code.

Error 20035

Priority 2

Error Message

Settings of InputField location are incorrect. Need to adjust the location. For more help, please consult the Appeon user document.

Possible Cause

The InputField location in the source code of RichText DataWindow has been manually modified. This is an invalid operation.

Solution

Re-create the RichText DataWindow. Avoid manually changing the element location of RTF documents in the source code.

Error 20036

Priority 2

Error Message

Unable to validate license key 'instance'. The number has exceeded the limit of your current license.

Possible Cause

The number of instances that are currently running has exceeded the number specified in the license.

Solution

Close the unnecessary instance or increase your instance number limited in the license file.

Error 20037

Priority 2

Error Message

Failed to write to the INI file! Verify that the current user account has access to the Windows system directory. For more help, please consult the Appeon user document.

Possible Cause

The current user account has no access right to the Windows system directory.

Solution

Use an account with proper rights to log in to the Windows or ask the administrator to assign proper rights to the current account.

Error 20038

Priority 2

Error Message

RegMultiString, RegLink and RegBinary data is not supported in server execution mode of RegistrySet. For more help, please consult the Appeon user document.

Possible Cause

RegMultiString, RegLink and RegBinary data is not supported in server execution mode of RegistrySet.

Solution

Change the server execution mode to the client mode in AEM.

Error 20040

Priority 2

Error Message

Unable to validate license key "device". The number has exceeded the limit of your current license.

Possible Cause

The Developer license is limited to 5 concurrent users/devices, and your app is being accessed by more than 5 users/devices now.

Solution

Upgrade the Developer license to Workgroup or Enterprise license (which has no limit on concurrent users/devices), or log out some of the online users/devices.

Error 20041

Priority 2

Error Message

Unable to validate license key "{0}". The number has exceeded the limit of your current license.

Possible Cause

The number of applications or sessions that are currently running has exceeded the number specified in the license file.

Solution

Close some of the applications or sessions, or increase the number limited in the license file.

Error 20042

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.