1. Faisal Hayat
  2. PowerBuilder
  3. Tuesday, 26 September 2017 16:19 PM UTC


We are moving from PowerBuilder 12.5 to PB2017. We are using PVCS (Serena) version control for PB12.5 and we intend to use same repository for PB2017. We are successful in establishing a connection between PVCS reposoitory and PB2017 code (which is just an upgraded version of PB12.5) BUT it doesn;t support any check in/out. It looks like that we are connected to the repository but PB2017 is unable to link the local objects and PVCS repository objects.


Can someone please help us in it. Thanks in advance.

Mark Lee @Appeon Accepted Answer Pending Moderation
  1. Friday, 29 September 2017 08:21 AM UTC
  2. PowerBuilder
  3. # 1

Hi Faisal,


Based on your description, it seems to be a bug of PB 2017.

As there's no such issue reported before, we'd be appreciated if you could submit a bug with a reproducible test case in http://www.appeon.com/standardsupport.



Mark Lee


  1. Boris Kern
  2. Friday, 16 November 2018 18:51 PM UTC
We have a similar issue. We migrated our applications from 12.5 to 2017 R2 and testing them in Windows 7 and 10.

PB 2017 R2 works fine with Serena PVCS on Windows 7, but on Windows 10 we can connect to PVCS, can add new objects, but cannot check in/out.

I installed today 2017 R3 on another Windows 7 workstation and got the same issue as R2 on Win 10 above.

We'll try figure out from PVCS side, but it might be PB issue.
  1. Helpful
  1. Boris Kern
  2. Friday, 16 November 2018 21:45 PM UTC
I fixed the issue in Windows 7 for 2017 R3 and PVCS. Usually when we opened PB we clicked OK on "Connect to Source Control (Online) option and had the issue after that. I selected "Do not connect to Source Control (offline)" and connected to Source Control from Properties of Workspace. After the connection the issue was resolved.

It might be a PB issue that needs to be fixed.

We still have an issue in Win 10, but found a workaround.

  1. Helpful
  1. Mark Lee @Appeon
  2. Monday, 19 November 2018 05:07 AM UTC
Hi Boris,

Probably we might have found the resolution.

Please refer to the ticket 454 & 462 and set the following in pb.ini and see if you can resolve the PVCS problem.



Take special note that you need to update both "pb.ini" files. The one in the application's installed directory, where the ".exe" resides, but with Windows 10, you also need to update the copy in the following location: "C:\Users\UserId\AppData\Local\Appeon\PowerBuilder 17.0" This copy is created in this location the 1st time you execute the "PB170.exe" and used from that point forward.

Also see ticket #462 ...


Also see ticket #413 ...



Mark Lee

  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.