VS2005 Adding solution to Vault.

john.clark · Post by **john.clark** » Wed Apr 23, 2008 4:49 am

We've got a newly installed vault running on SQL Server 2005.

Every time I try and add a solution to the vault, Visual Studio 2005 (all latest service packs) simply crashes and dies. I thought that this was perhaps down to security issues on the database, but I am a sysadmin on the db server and can manually manipulate data from my workstation with no problems at all. I also tried as the Vault admin user with the same results......

I know it's a little vague, but any ideas on what's going on here???

Thanks,

John Clark

ian_sg · Post by **ian_sg** » Wed Apr 23, 2008 7:29 am

We'll need some more information:

What version of Vault are you running?

Are you using the enhanced or classic client?

Can you add files to your repository using the stand-alone client?

Do you see any error message in Visual Studio, when adding the solution?

john.clark · Post by **john.clark** » Wed Apr 23, 2008 7:45 am

Running 4.0.0 of Vault.

No error messages at all, just a Visual Studio has stopped responding.

The solution I'm trying to add was previously in a Source Safe db, but has had all binding removed. I would have carried out an import of the VSS db into vault, but we're having major problems with that as well:

http://support.sourcegear.com/viewtopic.php?t=10127

Yes, I can add things using the local client with no apparent issues...

Thanks,

JC

ian_sg · Post by **ian_sg** » Wed Apr 23, 2008 7:56 am

I'd highly recommend that you upgrade to the latest version, 4.1.1, on both your server and clients.

Your other post, regarding the import, indicates a version mismatch between client and server. 4.0.x clients only work with 4.0.x servers.

After you get your client and server versions in sync, if you still have trouble, let us know.

john.clark · Post by **john.clark** » Wed Apr 23, 2008 8:38 am

Attempting to install the 4.1.1 client onto Vista Ultimate returns an error code of: 2738.

I'm a local admin on the client.

mskrobul · Post by **mskrobul** » Wed Apr 23, 2008 8:43 am

That error means VBScript isn't enabled.

The installer needs VBScript enabled on the machine in order to run and it sometimes isn't installed on Vista "out of the box".

Open a command prompt (as Administrator) then cd to wherever vbscript is on your machine. Usually it is %windir%\System32. Then run regsvr32 vbscript.dll.

cd %windir%\System32

regsvr32 vbscript.dll

Then try running the client installer.