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

Resolved Source control status not restored

  1. Issue
0
Votes
Undo
  1. Gordon Weil
    Gordon Weil
  2. PowerBuilder
  3. Friday, 27 December 2019 18:14 PM UTC

I have a relatively new installation of PB 2017 and I am having a number of issues with source control. I am using PB 2017 R3 build 1858 on Windows 10 with Version Manager 8.2.

The source control status is never saved. Everything looks like it is not under source control. I can add things to source control and then the source control status is correctly indicated by the icon to the left of the object, but the status goes away if I leave PowerBuilder and go back in. Then I need to add the item back into source control to see the correct source control status.

When I check out something I get an error: Access to SCC Provider failed during SccAdd. The error seems to apply to the pbg file. However the object I want to edit gets checked out. I can edit the object and check it back in normally.

When I run everything on my old machine everything still works the way it is supposed to. Source control status is indicated correctly every time I open PowerBuilder.

  1. Versioning
Does the general release of PB2019 contain the enh...
"Old-style" join syntax
Accepted Answer
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 27 December 2019 20:28 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi Gord;

  Looks like you are using the PERFORCE SCM software and therefore the SCCAPI connection route from the PB IDE (I presume).

  In that case, please try ...

1) Locate your working PB.ini file (as per the PB IDE's "System Options" dialogue - General Tab)

2) Close your PB IDE

3) Add the following to the PB.INI

[JavaVM]
CreateJavaVM=0

4) Restart your PB IDE and retry the SCC process

Regards ... Chris

 

 

Comment
There are no comments made yet.
Responses (4)
Gordon Weil
Gordon Weil Accepted Answer Pending Moderation
  1. Friday, 27 December 2019 21:55 PM UTC
  2. PowerBuilder
  3. # 1

Chris's solution worked! Although I am going to go with Armeen's suggestion and switch from Version Manager to Git.

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 27 December 2019 22:00 PM UTC
Hi Gordon ... that is great news! Thank you for letting us know.
  1. Helpful
There are no comments made yet.
Gordon Weil
Gordon Weil Accepted Answer Pending Moderation
  1. Friday, 27 December 2019 18:58 PM UTC
  2. PowerBuilder
  3. # 2

As I understand, the new native interface is available in PB 2019. If I were using PB 2019 then I would use Git. Since I am still using PB 2017 and cannot for the time being move to PB 2019, I am using the MS-SCC API with Serena Version Manager. We have used Serena Version Manager for many years now. I just cannot get Serena Version Manager working right on my new computer.

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 27 December 2019 19:09 PM UTC
PB 2017 R3 also has native interface to Git and SVN... it is not necessary to upgrade to PB 2019 to get this feature. Please see release history: https://www.appeon.com/developers/powerbuilder-release-history.html

Do you think you can switch from Serena to Git?

If not, are you able to consistently replicate this problem across multiple machines or it is only happening on one machine?
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Friday, 27 December 2019 18:45 PM UTC
  2. PowerBuilder
  3. # 3

Which source control system are you using?  If you are using Git or SVN, are you using the new native interface instead of legacy MS-SCC API?

Comment
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.