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

Resolved Problems with Source Control

  1. Issue
0
Votes
Undo
  1. Roland Smith
    Roland Smith
  2. PowerBuilder
  3. Wednesday, 1 November 2017 14:03 PM UTC

One of my customers is having trouble with source control object status using PB 12.5 and PB 2017.

Some but not all objects show as out of date when they have not been changed by any user. The version number shown in the library painter is '1' which matches the value in the source control system. In fact all objects are version '1' because they just did the 'Add to Source Control' and haven't done any check-outs yet.

If they do a GLV the out of date icon goes away. If they exit PowerBuilder and go back in, the out of date icon comes back.

I've had them delete the .pbc file and even looked at the .pbl in a hex editor and verified the version number is actually '1'.

They are using my WizSource source control system and I had them turn it's detailed debug logging and everything appears to be working correctly from that end.

I talked to someone else who had this happen in the past using TFS but he doesn't remember how they cleared the issue.

Does anyone have a suggestion or should I have them submit a bug report?

 

Herramienta para Mejorar interfaz de usuario
Connect to MS SQL Server Database in the applicati...
Responses (4)
Ronnie Po
Ronnie Po Accepted Answer Pending Moderation
  1. Wednesday, 1 November 2017 19:12 PM UTC
  2. PowerBuilder
  3. # 1

I've had the same type of thing happen more than once. In my case, I just wanted to know whether there were any changes, and I wasn't concerned about version numbers. I was able to get around the issues by adding the following to the Library section of the pb.ini file:

[Library]
SccDiffStrategy=08

 

Comment
Roland Smith
  1. Roland Smith
  2. Thursday, 2 November 2017 12:52 PM UTC
Thanks! I think that will help. What is even stranger is that only one of the four developers is having the issue.

  1. Helpful
Ronnie Po
  1. Ronnie Po
  2. Thursday, 2 November 2017 16:17 PM UTC
I hope it works! I could never nail down the exact cause either...

  1. Helpful
There are no comments made yet.
Govinda Lopez @Appeon
Govinda Lopez @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 1 November 2017 16:24 PM UTC
  2. PowerBuilder
  3. # 2

Hi Roland,

 

I've had these types of issues before. There could be some multiple reasons for this to happen. One of them could be that generated local files are Read Only. Other is that you might have to run an analysis tool on the database of the SC. I remember VSS used to do this all the time but after running the tool it got fixed. The file might have been recovered from a deletion in the SC software and it might not be updating the status accordingly. Also look into the support documentation of your SC software and please let us know of the outcomes.

I hope this was useful for you!

 

Regards,

Comment
There are no comments made yet.
Govinda Lopez @Appeon
Govinda Lopez @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 1 November 2017 16:23 PM UTC
  2. PowerBuilder
  3. # 3

Hi Roland,

 

I've had this type of issues before. There could be some multiple reasons for this to happen. One of them could be that generated local files are Read Only. Other is that you might have to run an analysis tool on the database of the SC. I remember VSS used to do this all the time but after running the tool it got fixed. The file might have been recovered from a deletion in the SC software and it might not be updating the status accordingly. Also look into the support documentation of your SC software and please let us know of the outcomes.

I hope this was useful for you!

 

Regards,

Comment
There are no comments made yet.
Patrick Therrien
Patrick Therrien Accepted Answer Pending Moderation
  1. Wednesday, 1 November 2017 14:56 PM UTC
  2. PowerBuilder
  3. # 4

Hi,

I already had this issues with TFS and i resolved it with GetLatest Version on target Select All items and in the advanced options checked the Overwrite writable files and Force Get of file version already in workspace.

This action refresh status between PB avec with source controller and your are sure after that your local source = server source.

I hope helps.

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.