1. JOHN THOMAS
  2. PowerBuilder
  3. Wednesday, 28 November 2018

All - curious if anyone has these same problems as we're having with source control connections via the workspace object, see two attached shots. 

1 - we have a consistent blowup with the TFSMsscciSvr.exe when trying to make a connection to Visual Studio Team Foundation Server, which is only happening on one of our boxes, not others.  Have tried resetting the compatibility settings on the TFSMsscciSvr.exe per other internet recommendations, for current service pack, but no help.

2- on a different box than the above, we see no TFS option at all, or any other source control options other than PB Native (never used). Curious if this is Visual Studio install deficiency (and if so, what?) or something additionally needed in the PB install. 

Both of these are major problems for us right now as we can do no builds anywhere until we get one of these installs able to connect to source control ok.  Thanks as always. 

Attachments (2)
JOHN THOMAS Accepted Answer Pending Moderation
0
Votes
Undo

Excuse me Roland, it was the SourcecontrolProvider entries, see my two shots attached, you're right. The one box has them the other doesn't. Thanks!

Attachments (2)
Comment
great, thanks
  1. JOHN THOMAS
  2. Wednesday, 28 November 2018
There are no comments made yet.
  1. Wednesday, 28 November 2018
  2. PowerBuilder
  3. # 1
JOHN THOMAS Accepted Answer Pending Moderation
0
Votes
Undo

Roland / all -  I looked at our registry keys as per your shots. Two shots attached here show regedit from a box where PB was showing (and connecting) to multiple other vendor options, TFS particularly.   Shots do not show any addl interfaces for TFS/Vis Studio though, they have only the same Native SCC key for the PBNAT125.DLL as your shots.  Has to be some other setup to be done.  Vendor lists in \vendor folder ( my #3 shot attached) are the same between box with conn options and box without.  Thanks. 

Attachments (2)
Comment
The Vendors folder is the list of database interfaces, not the source control interfaces.
  1. Roland Smith
  2. Wednesday, 28 November 2018
right, gotcha, makes sense, thx
  1. JOHN THOMAS
  2. Wednesday, 28 November 2018
There are no comments made yet.
  1. Wednesday, 28 November 2018
  2. PowerBuilder
  3. # 2
JOHN THOMAS Accepted Answer Pending Moderation
0
Votes
Undo

Thanks Roland, this looks like it's for my #2 issue (totally missing providers in s.c. options). we'll give it a try and report. 

Comment
There are no comments made yet.
  1. Wednesday, 28 November 2018
  2. PowerBuilder
  3. # 3
Roland Smith Accepted Answer Pending Moderation
0
Votes
Undo

See the attached images from Regedit. They show where source control registry settings are found.

The list of providers is located here:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SourceCodeControlProvider

TFS doesn't natively support the SCC API. You have to install a separate interface.

 

Attachments (2)
Comment
There are no comments made yet.
  1. Wednesday, 28 November 2018
  2. PowerBuilder
  3. # 4
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.