Commit error in AppeonDB
- Issue
- Oscar Naranjo
- PowerServer 2020 or older (Obsolete)
- Sunday, 21 July 2019 05: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
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.