Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved Commit error in AppeonDB

  1. Issue
0
Votes
Undo
  1. Oscar Naranjo
    Oscar Naranjo
  2. PowerServer 2020 or older (Obsolete)
  3. Sunday, 21 July 2019 17:31 PM UTC

Hello everyone,

We have been in the migration process to the R3 PowerBuilder and PowerServer version. Eventually, our deploys in the test server fail. We have been researching why it happens. We have been realized that when we have more than 3 deploys on the server if we try to deploy an additional, it fails. Attached the error generated in the deploy process.

Additionally, if we run the app there are many of the 13016 errors.

We also noticed that in our local versions for PowerServer developers, we can have an unlimited number of versions and never it deploys with errors.

 

Do we have a limit of objects or applications for a test license?

 

Parameters in AppeonDev.ini

[DeployConfig]
BatchDWSynLen=10000000
BatchDWSynNum=600
BatchDWSqlNum=1100
BatchESqlNum=1100

Server Information:

Product Edition: TESTING FOR WORKGROUP (Appeon)
Product Version: Appeon PowerServer 2017 Build 1858.00 64-bit Edition
Operating System: Windows 8.1/Server 2012 R2
Application Server: .NET
Maximum Universal Sessions&Devices: 50
Activation Status: ACTIVATED
Clustering Option: No
Offline Option: Yes
Number of CPUs Licensed: *
Number of Cores Per CPU: *
Type of CPU Licensed: Physics

Best Regards,

Oscar Naranjo

 

 

Attachments (2)
Error_AppeonDeploy.JPG Error_AppeonDeploy.JPG
ERROR APP.png ERROR APP.png
Powerbuilder 12.6 webservice WSDL cannot access er...
Multi Tenant Set up PowerBuilder/Oracle
Responses (2)
Oscar Naranjo
Oscar Naranjo Accepted Answer Pending Moderation
  1. Monday, 22 July 2019 19:52 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hi ZhaoKai,

Thank you for your reply, we double-checked that we had the configuration that you send to us, and we made some changes in the config.web file at the server.


Unfortunately, we still have the errors, now we do not have the commit errors in the deploy but we still have the errors 13016. What else can we do? Is there a way to connect to AppeonDB and verify if there is no corrupt data?

Best Regards,

Oscar Naranjo

 

Comment
Kai Zhao @Appeon
  1. Kai Zhao @Appeon
  2. Tuesday, 23 July 2019 00:52 AM UTC
Hi Oscar,



Please make the database type is correct in Welcome > Application > Transactions > Transaction Objects > %your application% page. Please full deploy application to see if there is any deploy error.



And please report the issues via our standard support ticketing system to ensure it is being properly received and tracked by our tech support:

https://www.appeon.com/standardsupport/. Many thanks in advance.





Regards,

ZhaoKai
  1. Helpful
There are no comments made yet.
Kai Zhao @Appeon
Kai Zhao @Appeon Accepted Answer Pending Moderation
  1. Monday, 22 July 2019 01:10 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

Hi Oscar,

This issue has nothing to do with license. Please refer to article below to adjust the value of related parameters in both Toolkit AppeonDev.ini file and IIS web.config xml file.
https://www.appeon.com/support/documents/appeon_online_help/ps2019/appeon_troubleshooting_guide/ch07s02s04.html#Error02004

Regards,
ZhaoKai

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.