Bug 792

SCC MSSCCI works in R1, not R2 13 January, 2021

Jeff Wayt
15 February, 2018
Product: PowerBuilder Category: PowerBuilder IDE
Version: 2017 R2 Build:
Classification: Publishing: Public
Priority: P3
Status: Closed Reason: NO RESPONSE
armando herrera @Appeon 13 January, 2021
#18
Hi Jeff, 

Based on our policy we have made 3 different attempts to contact you and determine if this ticket has been solved or not. Unfortunately, we did not get any response and we proceed to close it.  

If you consider this issue is still not fixed please, contact us. 


Regards!
armando herrera @Appeon 23 December, 2020
#17
Hi Jeff,  

We have been trying to keep in touch with you to find out about the resolution of this issue,  according to our internal help support policy we are in the need to close it in the next 3 working days. 

Please remember you can always open a new ticket in case you need it.
    
Regards!
armando herrera @Appeon 03 December, 2020
#16
Hi Jeff,

Is there any update on this case, do you need any further help from our side? 

Regards!
armando herrera @Appeon 28 September, 2020
#15
Hi Jeff,

This ticket has been stopped for a lack of information.

Since we were not able to reproduce this case and you are not on the project anymore would you mind if we close this ticket and open a new one in case you or one of your colleagues find it later on? 

Regards!
Ken Guo @Appeon 17 March, 2020
#14
Hi Jeff,

Due to that we are not able to reproduce it locally all the time and John Strano can’t provide a VM for us, we still can’t further analyze this issue.
Could you please provide a VM that could replicate this issue for us for further analysis?


Regards,
Ken
Jeff Wayt 16 March, 2020
#13
I'm not on the project anymore, using 2017 R3, and not working in TFS. I don't know if the issue persists and won't try to test a fix until there is further demand.
armando herrera @Appeon 16 March, 2020
#12
Hi Jeff,

Has been a while since heard from you!. 

Are you still facing this problem?. 
Is there anything we can do to keep helping on this issue? 

Regards!
armando herrera @Appeon 16 March, 2020
#11
Hi Jeff,

Has been a while since heard from you!. 

Are you still facing this problem?. 
Is there anything we can do to keep helping on this issue? 

Regards!
Ken Guo @Appeon 12 March, 2018
#10
Hi Jeff,

As we can’t duplicate the issue on our side, I am asking John Strano for a VM that can reproduce the issue.
Please understand that we can’t do further analysis until we can reproduce the issue.  

Regards,
Ken
Jeff Wayt 10 March, 2018
#9
I don't have another machine to reproduce this. I might have said it was my machine environment until John Strano reproduced it on his VM. I haven't loaded VMware yet.

It would be nice to know what R2 does differently in the registry or disk folders that UNinstall leaves there.

VS 2013 continues to work with TFS correctly.
Ken Guo @Appeon 26 February, 2018
#8
TFS

Hi Jeff,

We’ve been testing TFS with PB 2017 R2 on multiple machines recently and found that it works fine on all these machines (you may see the attachment for reference). 
So probably the issue is related to the environment. Are you able to reproduce this issue on all other machines? 
After installing VS 2013, did you have the VS Workspace correctly configured? And after configuring the VS workspace, did you click the Project … button of the Source Control in PB? 
If the problem is still there after trying all above, could please provide us a VM of your machine (that has PB and TFS installed but cannot connect to Source Control)so we can further investigate the problem? 
You may upload it to our FTP server with the below credentials: 
FTP site: ftp.appeon.com 
User: guest
Password: guest
Many thanks in advance.

Regards,
Ken
Jeff Wayt 21 February, 2018
#7
Ken, what is a "clean PC?" My PC was clean enough to work with VS 2013, MSSCCI and R1+MR1. Once I installed R2, it have me errors trying to initialize Source Control. I have since reinstalled all 3 but the residue (dirt) remains, so the uninstall failed to undo R2 completely. 

John Strano, who also reported the bug, installed on a virtual machine, so that was pretty clean. He was able to discard that VM, so any issue R2 introduced was isolated.
Ken Guo @Appeon 20 February, 2018
#6
Hi Jeff,

I want to know if you use a new clean PC and install Visual Studio Community 2013, MSSCCI and PB 2017 R2 and installed the whole lot, does it work?

Regards,
Ken
Ken Guo @Appeon 20 February, 2018
#5
Hi Jeff,

Thanks for reporting the problem. We are currently on holiday for the Chinese New Year holiday with limited access to the resources needed and will further look into this issue and get back to you when we get back to the office on Feb. 22, 2018. 
We appreciate your patience and understanding.

Regards,
Ken
Govinda Lopez @Appeon 20 February, 2018
#4
Hi Jeff,

I will transfer this ticket to our Engineering team for further analysis. We will keep you posted of the results here.


Regards,
Jeff Wayt 20 February, 2018
#3
I un-installed R2 and reinstalled the GA release of PB2017 (w/MR1) and now the bug remains. I uninstalled Visual Studio Community 2013, MSSCCI and PB and installed the whole lot. Still getting the bug. Is this another bug in the installshield config?

Is there a registry entry I need to fix?
Govinda Lopez @Appeon 16 February, 2018
#2
*** Bug 797 has been marked as a duplicate of this bug. ***
Govinda Lopez @Appeon 15 February, 2018
#1
Hi Jeff,

I'm working on reproducing your case. I will keep you posted of the results here.


Regards,
Jeff Wayt 15 February, 2018
*Phenomenon: Connect to Source Control, messagebox: "Critical error of Source Control Provider. Please restart IDE." PB Default output: Nonspecific Error performing SccOpenProject.
Source control is in offline mode.
Restoring SCC Offline Status Cache from last backup.
253 entries restored to SCC offline status cache.
Initialization of Microsoft Team Foundation Server MSSCCI Provider Failed

*Reproduce Steps: Install Appeon 2017 and first patch. Set up workspace for Team Foundation Server 2013 MSSCCI Provider. Connect to source control.
Uninstall PB2017. Install PB2017 R2. Reboot. Open workspace, connect to source control.

Remark: Upgrade to R2 and Team Foundation Server Source Control no longer works, worked in R1. John Strano has reproduced the bug on his machine, too
OS:
Windows 7
Platform:
64-bit
Database Type:
MySQL
Database Version:
Team Foundation Server 2013