Error during 4.0 installation

pproost · Post by **pproost** » Tue Jun 05, 2007 3:01 am

Hi, I just downloaded the 4.0 client and server setup files for testing because we are currently evaluating vault and thinking about buying it . When installing the client I get the following error (see attachement)
I previously had 3.5.2 installed which I uninstalled before installing 4.0
The pc is a xp prof SP2 it has als got VS2005 prof SP1 installed.
The 3.5.2 version installed without errors.

Best Regards

Peter

pproost · Post by **pproost** » Tue Jun 05, 2007 7:28 am

I don't know if this is caused buy the install not working perfect. But if I select the "SourceGear Vault Visual Studio 2005 Client" as source control plug-in in Visual Studio I can't save any projects (new and existing). I can repoduce this behaviour on multiple computers.

Peter

Beth · Post by **Beth** » Tue Jun 05, 2007 7:40 am

When you received the error, which option had you checked?

Try registering the file manually:
RegSvr32 filename

pproost · Post by **pproost** » Tue Jun 05, 2007 8:17 am

Hi, first thanks for the answer. I have just, before reading your post, restored one of my test computers to the state just after when visual studio 2005 was installed, so before any of the vault software or virusscanner was installed. Now when I run the vault 4.0 installer I get the same error. When I try to register the dll myself I get the following error (attachment)
What I also forgot to mention in my previous post is that when I choose the 2003 client in visual studio, projects get saved ok. When using the 2005 client a new project that wasn't even added to a repository wouldn't save locally. My repository also is completely empty. There were no projects added via an older vault version.

Best regards

Peter

Beth · Post by **Beth** » Tue Jun 05, 2007 10:11 am

First, I need to make sure Vault is even installing correctly without having Visual Studio in the mix. Let's just look at the server first because you mentioned installing that. What OS did you install the server on? What version of SQL server?

Beth · Post by **Beth** » Tue Jun 05, 2007 12:36 pm

For registering that component, open up a command line and go to the directory that Vault is in. You should be able to run the registration of that component from there.

pproost · Post by **pproost** » Wed Jun 06, 2007 12:44 am

Hi, sorry for the late reply but I'm in Belgium and 10 am your time is 7 pm here.

To answer your question the vault server installed correctly without problems on windows server 2003 standard edition SP2, the sql server is 2005 which I'm upgrading to sp2 today. I could access the admin website without problems and add users and stuff.
The vault GUI client on my pc also seems to work ok.
I tried registering the VaultPkg.dll from
c:\program files\sourcegear\vault client\vs2003_client\
but I keep getting the same error. I also tried installing the client on a normal pc without .net or and previous vault clients and it worked just fine.

pproost · Post by **pproost** » Wed Jun 06, 2007 2:49 am

Hi, just to keep you up to date. I used dependency walker to see what dll's VaultPkg.dll needs and it showed me that msvcr71.dll was missing. When I copied it from the .net framework folder and pasted it in the c:\program files\sourcegear\vault client\vs2003_client\ the VaultPkg.dll does register ok.

However I still can't save a project if I select "SourceGear Vault Visual Studio 2005 Client" in the visual studio Source Control/Options dialog
The save dialog (attachment) just keeps popping up but nothing gets saved. There are only 2 folders created in the folder where I choose to save the project. For example if I choose to save porject1 to c:\ the following folders get created c:\project1 and c:\project1\project1

If I choose the "SourceGear Vault VS2003 Compatible Client" everything works fine after restarting Visual Studio.

I'm now formatting one of my test pc's and doing a fresh install of Visual Studio 2005 (sp1) and then I'll install vault 4.0 to see if it works.

Regards, Peter

Post by **jeremy_sg** » Wed Jun 06, 2007 4:57 am

Peter,

Our investigation has turned up the cause for this error, which turned out to be that the installer shouldn't even been trying to register this dll as a service at all. We've corrected the installer, and as of 4.0.1, noone should see the error that you're seeing at install time.

However, I think that the install error is a "red herring" that and instead of concentrating on that, we should concentrate on your inability to save a project. Can you reproduce the problem with Vault client logging enabled for the Visual Studio 2005 client? We haven't had any other reports of Save project not working, so I want to track this down for you, to understand what's going on.

If you email me your phone number using the button below this post, I'll call you as early as I can (even before regular work hours here, since time zones are an issue).

pproost · Post by **pproost** » Wed Jun 06, 2007 6:00 am

Hi, thanks for your answers.

I've enabled logging an attached is the log file.
I'll describe the steps I did while logging was on:

1) Open vs2005
2) Create new project
3) Click the "save all files" button
4) The saveproject dialog stays on the screen, clicked cancel
5) Closed .net when closing it asks me if I want to save the project or not. I clicked discard

While typing this post. I had an other idea. I have tried turning the "save new projects when created" setting on and this seems to solve the problem of saving the projects. This setting is by default turned off when you choose the vb.net environment settings when you start visual studio 2005 for the very first time. (see attachment for the option dialog)

I hope this is of any help. Now I'm going to test vault 4.0 further to see if I've got everything working.

Thanks again for your time and support

Post by **jeremy_sg** » Wed Jun 06, 2007 4:24 pm

Peter,

Thank you for the hard work to track down the cause of this. We've reproduced the bug, and have a simple fix. We're still working to get a true fix for this, so I hope that you can be patient. Thanks again.

pproost · Post by **pproost** » Thu Jun 07, 2007 12:54 am

You're welcome.

Greetings Peter

evega · Post by **evega** » Wed Jun 13, 2007 6:30 am

I am having this exact same problem on my Vista Enterprise box. I havent experienced this on any of our XP SP2 boxes. Thought I would let someone know, b/c our devs who run Vista are down. Luckly we all have XP VPCs we are now working off of.