Knowledgebase
Knowledgebase : Appeon > Errors
Error14031: The license data initialize faild. Solution: You need to
right-click on the license.appeon file and set the security for
"Everyone" user to "Full Control"
The problem is not related to the license. Try the solution below and
if the problem cannot be resolved, the customer needs to reinstall the
Appeon Server.
SOLUTION ONE:
The permission is not enough, please try to use the following
solution to solve this issue:
a. Right click the C:\Inetpub\wwwroot folder, select the Properties
items and select the Security tab page;
b. Add Everyone group if it is not listed in the box "Group or user
names";
c. Grant Full Control permission to the everyone group.
d...
You can set the "outer join syntax" setting in Appeon developer the
way you do it in PB.
After the settings are done please redeploy your application with
full deployment mode.
You may have an error "Failed to generate DWSQL" when using Appeon
developer on PB 11.5 and ASA.
Please try to upgrade your PowerBuilder to the latest PowerBuilder
11.5 version available.
First of all ensure that the database connection in Appeon Developer
Configuration | DB Type Profiles is successful.
Then we recommend you full build your PowerBuilder application.
Next, go to the \$Developer$\Project\your_application\release or
debug\dwsql\dwsql.log to get the last record, empty compiled this...
Please follow the instructions below:
1. Make sure the connection cache can ping successfully in the AEM
Console > Server Properties > Connection Cache > Edit Connection Cache
> [your_connectcache].
2. Go to the AEM Console > Application Properties > Transaction
Objects > [your_application] to set the Transaction Object to to
connection cache mapping.
3. Make sure the application profile configuration of Appeon developer
tool has been set the correct database settings.
sqlca.dbms = 'O10'
sqlca.servername =...
Error 10999: Failed to find the configuration of sqlca AEM. Please
make sure that the configuration of this transaction object in AEM is
right
Solution:
Please go to the AEM Console > Server Properties > Connection Cache
to add the 'MS SQL Server native driver' cache name and go to the AEM
Console > Application Properties > Transaction Objects >
[your_application] to add the Transaction Object to connect the cache
name.
What to do when downloading a file by Appeon File Server, though the
files exists under the specified directory and the physical directory
in AppeonFileService.log is correct, the download fails with no
indicated error?
That might be caused by that the cache of Appeon File Server doesn't
match the actual file. For example, if you manually modify or override
a file directly in Appeon File Server machine instead of uploading a
new file by Appeon File Server, then this error would occur.
Please go to Ap...
In the Internet Options window, make sure the Trusted sites Web
content zone is selected, then click the Custom Level button, and
double check the following settings are enabled (they are enabled by
default, but we recommend you make sure):
* Download signed ActiveX controls
* Run ActiveX controls and plug-Ins
* Script ActiveX controls marked safe for scripting
* Active scripting
* Click OK to save the changes
For more information please go to Appeon Help > appeon developer
user guide > runnin...
You may have this error when upgrading to a major version of Appeon
or installing an EBF (see attached).
Before contacting Appeon support please be sure of doing a FULL
deployment of your application with the new version.
If you are using Websphere you need to undeploy the application and
then redeploy it (full deployment)
If after doing a FULL deployment you still have the error, the issue
is probably caused by the different Web root between the web server
and the application server.
In the...
If you are having problems with your license, please create a ticket
in appeon.novalys.net/support with the following information:
* The screenshot of the license error message
* The AEM URL or the AppeonError.log and AppeonServer.log under the
Debug Mode
* The Appeon version, the OS information of the Appeon Server, and
your all the hardware information by executing ipconfig (mac address,
processor, etc)
Please note that we will be unable to reply to your request if any of
the above information is...
Regarding the Data Source not being displayed issue, please refer to
the solution in the Appeon Help> Appeon Server Configuration Guide for
J2EE> Database Connection Setup> Setting up Appeon Server data
sources\connection caches> Setting up data source for WebSphere>
Required configurations when global security is on.
This is NOT an Appeon Product Issue and is NOT covered by Technical
Support.
This is NOT an Appeon Product Issue and is NOT covered by Technical
Support.
Ensure the following before contacting Appeon:
* Supported Windows OS and Web browser version are being used.
* The URL is added to the Internet Explorer trusted sites list and
the security for the zone is set to medium or lower.
* The URL used to launch the application ends in index.htm NOT
application.htm (even though after accessing from index.htm it
automatically redirects to application.htm).
* If it still fails, restart the computer, disable the anti-virus
program and try again.
* If it...
If you get an HTTP 404 error this is NOT an Appeon Product Issue and
is NOT covered by Technical Support.
We suggest you try the following:
* Verify that the Web and application server are running properly.
* Verify there is network connectivity between the Windows PC and
the server.
* Verify that a non-Appeon Web page can be loaded. For example, if
the Appeon Web URL is www.domain.com/myapp/index.htm [1] then verify
thatwww.domain.com/index.htm [2] brings up the index.htm page on the
Web ro...
Ensure the following before contacting Appeon:
* That the Web and application server are running properly.
* That AEM can be loaded and there are no license errors. For
example, go to www.domain.com/AEM [1] and you should see the AEM login
screen. If you do not see the AEM login screen either Appeon Server
has not been installed or the Web and application server are not
running properly.
* Login to AEM and ping the connection cache that is used by the
application you cannot login/run. It MUST pin...
If the connection cache does not ping this is NOT an Appeon Product
Issue and is NOT covered by Technical Support.
Usually, this is caused by incorrect username/password or other
incorrect information supplied in the connection cache. Alternatively,
the next most common reason is the database is stopped. Please work
with your server and database administrator to resolve this issue.
Ensure the following before contacting Appeon:
* That all Windows updates have been applied.
* That anti-virus scan shows no viruses.
* That the Internet Explorer security option "Download signed
ActiveX control" is set to "Enable" (make sure to restart Internet
Explorer if making any changes).
* Documented steps to reproduce and provide test case or original
application source code.
This issue is caused by deploying Appeon in "Debug" mode. The mode is
specified in the Application Profile Configuration of the Appeon
Developer. Change to "Release" mode and perform a Full Deployment of
the application. If the problem still persists, provide documented
steps to reproduce and test case or original application source code.
If the Web application uses a Sybase Adaptive Server® Enterprise
(ASE) database or a SQL Anywhere database that is set as
ASE-compatible, database updates may fail. This is a known issue and
must be worked around during the development of the PowerBuilder
application. It is not covered by emergency Technical Support.
The cause of this issue is if the length is 0 or the value of the
data is NULL for any data in a database table where the data is of a
string type, such as varchar or char data type, the ...
In case you have a problem with you Appeon application, please send
us a test case and the error log from your server, please follow the
steps below:
1. Clear off the previous appeonserver.log and appeonerror.log in AEM
2. Set the log mode to "Debug Mode" in AEM
3. Reproduce the issue
4. Send the appeonserver.log and appeonerror.log to us
You can also try to use the Appeon client log functionality which is
a new feature of Appeon 6.6 (see attached).
ISSUE: The Appeon Xcelerator plug-in cannot be loaded.
CAUSE ANALYSIS: This issue may be caused by improper security
settings, limited login user permission or third-party software
conflict.
SOLUTIONS:
SOLUTION 1: Add the URL of Appeon Web application to the TRUSTED
SITES zone in Internet Explorer.
SOLUTION 2: Adjust IE security settings.
Click the TOOLS menu | INTERNET OPTIONS | SECURITY tab. Select the
APPROPRIATE WEB CONTENT ZONE. Click the CUSTOM LEVEL... button. Enable
the following...
PHENOMENON:
If you are not the administrator, you may run into the issue which
keep you from loading or installing the Appeon Xcelerator plug-in.
ANALYSIS:
Technically speaking, the user with the administrator right can
directly load/install the Appeon Xcelerator plug-in. For the user
without the administrator, you need to follow up the solution below to
manually load/install the Appeon Xcelerator plug-in.
SOLUTION:
Step 1: Click the IE information bar at the top which is saying "This
webs...
If you have this error when trying to deploy your application to the
Appeon Server please refer to the attached document
If you are using Chrome 42 and you are having problems with Appeon
plug-in, please take a look at the following article:Chrome 42
[http://www.ghacks.net/2015/04/15/chrome-42-blocks-java-silverlight-other-plugins-by-default-now/]
In case the your problem persist please close and reopen browser after
successful installation of the multi-browser plug-in. Please refer to
articles below to check client settings.
http://www.appeon.com/support/documents/appeon_online_help/2015/installation_guide/bk01ch05s02.ht...
Error code: 15056
The Appeon Workspace currently available on the Apple App store is
build #1988. This build of the Appeon Workspace is only compatible
with applications deployed with PowerServer 2019, which currently is
only available in the Workgroup and Enterprise Editions of
PowerServer.
Regardless, the Appeon Workspace that's available on the Apple App
Store will always be updated to the latest version available, this
will cause version mismatching to occur. This is because this
workspace is for de...
Help Desk by Novalys