Source Control - Unable to Access Database

davecourt · Post by **davecourt** » Mon Jan 09, 2006 9:03 am

Hi

We are getting the following error when trying to load a project which is under source control in Vault.

Source Control - Unable to Access Database

The associated source control plug-in is not installed or could not be intialized

We are running:

Vault 3.1.6
Visual Studio 2005

Would it be possible to give a likely reason for this happening?

Thanks

DC

lbauer · Post by **lbauer** » Mon Jan 09, 2006 9:05 am

Is this happening just for a particular project, or any project?

Can you connect to the same repository with the Vault GUI Client?

davecourt · Post by **davecourt** » Mon Jan 09, 2006 9:09 am

Thanks for the quick response.

This is not occurring when accessing via the GUI client and we are unable to determine whether other projects are affected because this is the first VS 2005 project he is accessing.

Thanks

Post by **Tonya** » Mon Jan 09, 2006 10:42 am

Dave,

It's possible that your source code control provider has been changed from within VS 2005. I have experienced this issue myself without manually changing it, I believe it's a bug within VS 2005. The first thing to check is Tools - Options - Source Control - Current source control plug-in. Verify that this is set to "SourceGear Vault Client".

Please let me know if this is the case.

Thanks,

Tonya Nunn
SourceGear

davecourt · Post by **davecourt** » Mon Jan 09, 2006 10:57 am

Hi Tonya

It is set to Vault already therefore not resolving the issue.

Post by **Tonya** » Mon Jan 09, 2006 11:06 am

Very interesting!

Could you tell me what you see under Hkey_local_machine, Software, SourceCodeControlProvider, InstalledSCCProviders from within your registry editor?

Thanks,

Tonya

davecourt · Post by **davecourt** » Tue Jan 10, 2006 4:52 am

Hi Tonya

We have:

(Default) REG_SZ (value not set)
SourceGear Vault REG_SZ (SOFTWARE\SourceGear\Vault Client)

Thanks

Dave[/img]

Post by **Tonya** » Tue Jan 10, 2006 10:31 am

The next suggestion that I have is to close VS 2005, open your Vault Client, set your default scc provider to Vault (Tools - Options - General - Make Vault your default SCC provider) and close the Vault Client. Reopen VS 2005 and verify that Vault is set as your primary scc provider.

Attempt to open your project again. If the problem still exists, please give me steps that you are taking to open the project from source code control.

Tonya

davecourt · Post by **davecourt** » Tue Jan 10, 2006 11:18 am

Hi Tonya

We did all of that with no luck.

All we are doing is opening a Visual Studio solution by using the File -> Open -> Project.

The project has already been bound by someone else using Visual Studio 2005 and they are able to open it fine.

Thanks

Post by **Tonya** » Tue Jan 10, 2006 11:29 am

Dave,

Regardless if the project has already been bound to source code control, you will need to open the project by using File, SourceControl, Open from source control the very first time that you open a project. From this point on, you can continue to open the project using File - Open.

If you are the person adding the project to scc, you wouldn't have to use the open from source control option because the project already exists on your machine, which why they're not having the problem.

I would reccommend clearing out your working folder before opening the project again.

Tonya

davecourt · Post by **davecourt** » Wed Jan 11, 2006 2:56 am

Thanks Tonya,

This did solve the problem for us.

Thanks again

Dave