1. Zhang JX
  2. PowerBuilder
  3. Tuesday, 16 February 2021 02:51 AM UTC

Hi all,

Thanks Appeon team to offer the Powerserver2021 beta trial opportunity.

I have successfully deployed the SalesDemo application with the help from Julie. laughing

When trying to deploy my own application, hit the error:

  Error: Illegal characters in path.
  Failed to create the .NET Datastore model.
  ---------- Finished Deploy of psndycapp (10:22:38 AM)

FYI:

1. PFC2019 framework, I have solved those DB connection issue by adding pfc related Security/Message tables

2. Followed the same power server project configuration exactly same as SalesDemo project setup, except the solution folder name.

 

Thanks in advance for advising.

Best Regards

JX

Accepted Answer
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 16 February 2021 15:15 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi Zhang;

   Please look for names of a Path, Folder or File that might have a space(s) in them. That could cause this type of error as Snap (C#) does not like spaces.

Regards ... Chris

Comment
There are no comments made yet.
Zhang JX Accepted Answer Pending Moderation
  1. Thursday, 18 February 2021 07:18 AM UTC
  2. PowerBuilder
  3. # 1

Thanks Chris and Zhaokai,

I have attached the DWO here.

By the way, I have raised a support case: 6084 and wait for engineering's reply.

 

Best Regards,

JX

 

Attachments (1)
Comment
  1. Zhang JX
  2. Thursday, 18 February 2021 13:31 PM UTC
To all,

I suspect issue with this DWO which was migrated from PB2017 >> PB2019V2 >> PB2019V3 >> PB2021 Beta version.

I have re-created this DWO and passed the build & deploy process. Case close for this "illegal path" error.



Thank you.

JX

  1. Helpful
  1. Armeen Mazda @Appeon
  2. Thursday, 18 February 2021 15:46 PM UTC
Great, glad to hear you figured out the issue and thanks for sharing the solution!
  1. Helpful
There are no comments made yet.
Kai Zhao @Appeon Accepted Answer Pending Moderation
  1. Thursday, 18 February 2021 07:03 AM UTC
  2. PowerBuilder
  3. # 2

Hi Zhang,

For the Illegal characters in the path issue, I did not reproduce the issue on our end, it is possible to be caused by the DataWindow object after D_Rep_Do_Invoice_Novmal_A4-Glocom_Chd (in alphabetical order). If it is the root cause, please export and provide it to us for more study, thanks.

For the LOAD libcadp.dll issue, please try copy files below from
C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 19.2.0.2670
to
from C:\Program Files (x86)\Appeon\PowerBuilder 19.0\IDE.

libcrypto-1_1.dll
libcurl.dll
libssl-1_1.dll

If this still doesn't help, let's schedule a remote session to debug it. We would recommend you to make the remote session during our working time which is 9:00 ~ 17:00 (we are in UTC+8 ) thus we can get immediate help from the other team if necessary. Regarding the tool to make the remote session, we usually use GTM or TeamViewer, and TeamViewer is preferred because its response is quicker than GTM during the session, but we can use the other tools that you think better. Anyway, please let us know when you can make the session and which tool you'd like to use for this session.

Regards,
ZhaoKai

Comment
There are no comments made yet.
Zhang JX Accepted Answer Pending Moderation
  1. Tuesday, 16 February 2021 03:05 AM UTC
  2. PowerBuilder
  3. # 3

To add on,

when changing the [Run the app in:]" from "Default Web Browser" to  "Cloud App Launcher...", 

and deploy again, got below error message.

back to [Deployment] page >> "Server Configuration" >> "Test File Path", got below error message: < Failed to load the library "libcap.dll" >

Thank you.

JX

Comment
  1. Chris Pollach @Appeon
  2. Tuesday, 16 February 2021 16:46 PM UTC
Hi Jhang;

Did you use the new "Upload Cloud App Launcher and Runtime" link located in the PB IDE's "tools" menu to both create and upload the Cloud App Launcher to IIS *before* deploying your App?

Regards ... Chris
  1. Helpful
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.