Error using Visual Studio 6

andreypir · Post by **andreypir** » Thu Feb 28, 2008 6:26 pm

Vault Client 4.1.0 (16216) is installed. Visual Studio 6.0 with SP6 is unable (was never able) to connect to the server. Error message is:

Error accessing Source Code Control system.
Check installation.

Visual Studio 2005 works fine. The flag "Make Vault your default SCC Provider" in the Vault client is selected. Problem found both on Windows XP and Windows Vista machines.

lbauer · Post by **lbauer** » Fri Feb 29, 2008 9:38 am

Thanks for the report. We'll investigate this.

paul-shed · Post by **paul-shed** » Mon Mar 10, 2008 6:26 am

I too and having the same problem but with 4.0.6 (15954).

I have the integration with VC6 working fine on one machine but on another I cannot get it to work. It always comes up with this dialog.

I have tried reinstalling VC6 and Vault but the problem is still there. When I run up VC6 the "source control" menu is available under projects. I can launch Vault from the VC6 menu. But when I try to create a new project and then add it to vault this dialog pops up. Also whenever I load a project which is in Vault I get the dialog. From then on SCC integration is disabled.

Have you managed to find out what the problem is?

Regards,

Paul

Terence · Post by **Terence** » Mon Mar 10, 2008 8:04 am

Can someone post a screenshot of the dialog?

paul-shed · Post by **paul-shed** » Mon Mar 10, 2008 9:31 am

Sorry I can't, it's started working ok.

I installed some software which upgraded the .NET version to 1.1. This seems to have fixed the problem.

Now unfortunately I don't know what the previous version of .NET was. But those experiencing a problem could try and install .NET 1.1.

Regards,

paul-shed

andreypir · Post by **andreypir** » Tue Mar 11, 2008 7:41 pm

Image of error message is attached.

I installed .Net 1.1 and this fixed the problem. I had VS 2005 and therefore .Net 2.0 installed on my computer before I installed SourceGear, probably this is why .Net 1.1 did not get installed automatically.

lbauer · Post by **lbauer** » Tue Mar 11, 2008 9:52 pm

Thanks for the update. I'm not sure why installing .NET 1.1 would fix the problem, though, since Vault 4.x uses the .NET Framework 2.0.