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

Resolved Migration Error From PB 12.5

  1. Issue
0
Votes
Undo
  1. Richard Keller
    Richard Keller
  2. PowerBuilder
  3. Friday, 30 June 2017 14:38 PM UTC

Error on trying to update pbwsclient. Exact message is outdated files detected    pbsoapclient/pbejbclient/pbdom/pbwsclient   Please migrate to 170.     I replaced the PBDOM to the 17 version not sure where to set or migrate. 

  1. Migration
How to turn the 30 day trial version into a subscr...
Migrate powerbuilder 11.5 Application to powerbuil...
Responses (1)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 30 June 2017 14:42 PM UTC
  2. PowerBuilder
  3. # 1

Hi Richard;

  After replacing the PBL with the PB 2017 version - please use the RHMB on your App's TARGET and choose the "Migrate" option again. After the migration is OK - I would then do a RHMB again on the target & perform a full build to be on the "safe" side. Hopefully, that should get your App all set for PB 2017!

HTH

Regards ... Chris

Comment
Richard Keller
  1. Richard Keller
  2. Friday, 30 June 2017 16:34 PM UTC
Using PB 12.5 I removed the PBL that had the Soap/WS PBX imported and moved objects to new PBL,  I couldn't find a way to edit PBX extensions in PB 12.5 anywhere.   Documentation said that PBX should be in system tree but I never saw it.    Also removed PBDOM125.pbd prior to error and replaced with PBDOM17.pbd for anyone else migrating webservices proxies.  

  1. Helpful
Martin Heigl
  1. Martin Heigl
  2. Monday, 3 July 2017 09:06 AM UTC
Hello,



reason is the PBX File...

migrate this with pbx2pbd.exe and then it's working fine.



Current i've only a problem with n_pbniserv. Working on it



regards MArtin
  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.