1. Miguel Alzate
  2. PowerServer 2020 or older (Obsolete)
  3. Wednesday, 22 May 2019 14:36 PM UTC

Hi all,

Getting this error when debbuging the Web app: "03502: PBL files have been changed. Please re-deploy the application under the debug mode."

I re-deployed as suggested but error persists.

App configuration:

I did Full build in Powerbuilder and Full deployment in Toolkit. Then debug again. Error continues.

Note: Debugging was working fine until some weeks ago.

My software:

PowerBuilder 2017 R3 Build 1858

Powerserver Toolkit 2017 R3 Build 1858

PowerServer (PB Edition) 2017 R3 Build 1858

MS Script Debugger and SDK correctly installed (remember note above).

 

Any ideas?

 

 

Accepted Answer
Marco Meoni Accepted Answer Pending Moderation
  1. Wednesday, 22 May 2019 16:42 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # Permalink

Hi Miguel,

have you selected the right server profiles (and deployment profiles) ?

When you start debugging an application, you must have selected the PowerServer instance where the app is deployed to.

Best,

.m

Comment
  1. Miguel Alzate
  2. Wednesday, 22 May 2019 17:23 PM UTC
Hi Marco. Thanks for replying.



I chose "Local Deployment " as the "Deployment profile" in "Deployment Wizard" dialog box. Local Deployment profile points to local Powerserver and local Web server. However, these servers were not marked as "Default". So I marked local servers as default and, it worked!



Thanks again for your indications. Question resolved!



  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 22 May 2019 17:24 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hi Miguel;

  FWIW: It might be worth deleting your Web App in PowerServer (aka IIS), rebooting, then perform a full deployment again - just to make sure that the PS Toolkit is not looking at some older settings. ASs Marco also mentions, check your PS Toolkit's project settings and where the Web app is being deployed to.

Regards ... Chris

Comment
  1. Miguel Alzate
  2. Wednesday, 22 May 2019 18:08 PM UTC
Thanks Chris.



In effect, the deployment was pointing to the wrong server.
  1. Helpful
  1. Chris Pollach @Appeon
  2. Wednesday, 22 May 2019 19:17 PM UTC
Yep .. that's a definite issue. Glad that you found the problem!
  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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.