Error accessing Source Code Control system VC6

[peterbrown05]

Hi,
I have receintly reinstalled WindowsXP and VC6 in a VirtualMachine (Im now running win7).
I cannot get the Vault source code integration to work.

Ive seen your article on vb6, but is there an equivalent HowTo Guide for VC6?
I think what is missing is the 'launch vault' on startup macro but I cannot find it anywhere...

Vault IS configured to be the default source code provider. and I CAN log in to vault from my virtual machine.
Just VC6 doesnt load or try to connect to vault, and just reports
"---------------------------
Microsoft Visual C++
---------------------------
Error accessing Source Code Control system.
Check installation.
"

please help!
kind regards
peteB

[Beth]

Do you have the key HKEY_USERS\S-1-5-21-746137067-507921405-725345543-1003\Software\Microsoft\DevStudio\6.0\Source Control? HKEY_CURRENT_USER\Software\Microsoft\VisualStudio is there just an entry for 6.0?

[peterbrown05]

I have the key:

HKEY_USERS\S-1-5-21-1401002954-949184468-70227957-1259\Software\Microsoft\DevStudio\6.0\Source Control

but thats different to the one you mention.


i also have the key: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0
but nothing else under VisualStudio in HKEY_CURRENT_USER

I also have HKEY_CURRENT_USER\Software\Microsoft\DevStudio\6.0\Source Control

[Beth]

Open your registry and go to [HKEY_USERS\.DEFAULT\Software\Microsoft]. Do you have an entry for Visual Studio under there? If not, make a new key called Visual Studio. Under Visual Studio make a key called 8.0, and under that make a key called CurrentSourceControlProvider. Then create a new string value. The name of the string should be ProviderRegKey and the data entry should be SOFTWARE\\SourceGear\\Vault Client. Then create another new string value where the name is @ and the data entry should be {53544C4D-FFD5-48A9-B04A-0700CCD31070}.

Then restart your VC6 and see if there are any changes. Try first just one, such as an Open Workspace and let me know the results. I found that sometimes in this particular setup that it sometimes took a minute for the login page to come up.

[peterbrown05]

hi beth
Ive made those changes (yes there was a VisualStudio branch, but it had a 9.0 subkey. I created the 8.0 as requested).

Unfortunately I still have the same problem.

Interestingly (maybe) I tried changing teh option in Vault from "Make Vault my default SCC provider" to dont make it default, and on loading VC6 it asked me for my SourceSafe logon details...
so, i know vault is interacting with VisualStudio some way.

Does the installation order for Visual Studio vs Vault matter? I think Vault may have been installed prior to VStudio....

any suggestions?

[Beth]

The order does make a difference. Vault must be installed after Visual Studio. You might try an uninstall and reinstall of Vault.

[peterbrown05]

i uninstalled
rebooted the VM
reinstalled Vault
checked options where for "make vault default SCC provider"

...but still same problem. "Error accessing Source Code Control system"

Is this known to work in a Windows 7 Virtual Machine XP installation connected to vc6?

or, am I fighting a loosing battle?

cheers
pete

[Beth]

The quickest "trick" I can think of that might put what's not being seen in place would be to install an older version of Vault, then uninstall it and put in your newer version. Would you be willing to try that? If so, then download the Vault 3.1.9 client from here, http://download-us.sourcegear.com/files ... _3_1_9.msi. Uninstall your current version of Vault, install Vault 3.1.9. Then check to see if it shows up in VC6. Then uninstall Vault 3.1.9, and install your current version of Vault. How does it look now?

I know there are some issues when trying to write to a Windows 7 registry, but since you are in a VM, and that VM is running Windows XP, I am assuming that it's able to write to the registry for the virtual OS.

[peterbrown05]

i will try this in the morning,
but yes - it CAN write to the registry without needing to be run as an administrator.

i can see this is so as changing the "make vault my default scc provider" option changes the dialog box when vc6 loads a workspace,

cheers
peteB

[Beth]

Do you have the 1.1 .NET framework installed? It is one of the requirements for the Vault Classic Client. Otherwise, you will need to use a ide_name_here.exe.config file.

[peterbrown05]

yes - you cant install vault without it.
but, the VM in windows7 bundles with WinXP with SP3 which comes with the latest .net framework.

i will try the older vault version tomorrow and see how it goes.
cheers
pb

[Beth]

Ok. You won't be able to connect with the old version. This is just to see if it shows up. I'm still digging for better solutions than this, but this might get you going while I'm looking.

[peterbrown05]

sorry, the install of the old version didnt solvet he problem.

[Beth]

Can you show me what the following areas of your registry look like?
1) HKLM\Software\SourceCodeControlProvider
2) HKLM\Software\SourceCodeControlProvider\InstalledSCCProviders
3) HKCU\Software\Microsoft\VisualStudio

[peterbrown05]

ive attached the areas you asked for zipped up.