We were working fine on PB 9.0, and 12.6, using the SCC interface to connect with MKS source control. There were the occasional odd errors popping out here and there, but it was working.
They just upgraded to a new server for MKS, forcing us to uninstall MKS, and reinstall it. After that, some of our machines have been exhibiting odd behavior, with PowerBuilder closing / crashing right after they successfully establish a connection to MKS. No error message, nothing. I turned on the Log All Activity flag in the Source Control tab.
------------------------------
6/18/2015 11:51 Source Management Initialization...
Scc Provider: MKS SCC Integration
User ID:
Project Path: C:\Dev\PowerBuilder\12.6\Test\Archives\project.pj
Aux Project Path: _mks_sanbox_exists
Local Project Path: C:\Dev\PowerBuilder\12.6\Test\Archives
Unable to initialize SCC status cache from backup C:\Dev\PowerBuilder\12.6\Test\Archives\Test_Archives.pbc.
Scc multi-threading defaulting to TRUE
Connection to source control established.
------------------------------
I've tried compatibility settings, desktop settings turning Aero off, and same behavior. The fact a few other machines don't have this problem is just really bizarre. We've tried importing our Sandboxes, recreating our Sandboxes, etc, and just can't figure out what's going on. There were some blogs I found about the PBC file possibly getting corrupt, but at this point, the PBC file doesn't even show up. It's like it connects, and about that time is when it normally would do a refresh of the object states, but instead PowerBuilder just quits. I'm getting the security folks to allow me to disable Symantec temporarily so I can check to see if it's interfering somehow, however I think it's not, but I'll give it a shot to make sure I rule it out. I will say that the machines that it's failing on seem to be newer machines. That would be really odd it was some type of combo about the machine causing the issue. But I've seen other odd things before, like the video card interfering with the ability to add report parameters to a datawindow!
I'm in the process of trying to convince management to allow us to switch to TFS. Otherwise we're faced with going PB Native, and I really do not want to lose version control, rollback, and history storage and comparison abilities to name a few.
Anyone run into this issue before, and fixed it? Again, some machines, it's still working fine. Just very odd. Any drawbacks to going TFS via SCC?
Related Info:
Machines: Windows 7
PowerBuilder 9.0 & 12.6
MKS Info: MKS Integrity Client 2009
Build: 4.10.0.9665
Service Pack: 007-01
Antivirus: Symantec Endpoint Protection
Version 12.1.5 build 5337