Vault fails to run on Framework 1.1 SP 1

DinoNZ · Post by **DinoNZ** » Mon Aug 30, 2004 8:57 pm

Service Pack 1 was released recently, and after installing it Vault simply doesn't run - the exe shows in task manager, but nothing happens even after several minutes - no errors, no nothing.

I have other VS.Net 2003 projects running, and they all seem to be fine - any suggestions?

DinoNZ · Post by **DinoNZ** » Mon Aug 30, 2004 10:15 pm

Is version 2.0.5, and the Admin tool works fine, just not Vault Client.

Post by **jclausius** » Tue Aug 31, 2004 7:48 am

DinoNZ:

Edited for content. I had erred.

Our internal testing has shown Vault is safe to use with .Net 1.1 SP1.

Post by **jclausius** » Tue Aug 31, 2004 8:16 am

DinoNZ:

Did you use the "Technical Preview"?

The only thing I can find at the MSDN web site is a message that .Net Framework SP1 will be available in September.

Post by **jclausius** » Tue Aug 31, 2004 8:40 am

Update... I found the link to the release, it is located lower on the .Net framework page ( below the tech preview link ).

Dino · Post by **Dino** » Tue Aug 31, 2004 10:43 am

I was able to commit a transaction via Visual Studio, but obviously not via the Vault Client executable.

It appears to be ok though, because at the time a colleague was able to check out files I checked in, modify them and then I got the latest versions and compiled it ok - so do we have to restore the database?

If we do, can I restore it and then check out and merge any files that are reported as renegade?

Post by **jclausius** » Tue Aug 31, 2004 11:06 am

What version of .Net 1.1 SP1 are you using for both client and server (Tech Preview or Release)?

Post by **jclausius** » Tue Aug 31, 2004 11:09 am

Dino wrote:so do we have to restore the database?

No need to just yet. I'll update this when I have more info.

Can I ask you try try something? Try a restart of IIS (iisreset.exe) on the Vault server. Now try to log into the server. Does everything appear to be OK?

Dino · Post by **Dino** » Tue Aug 31, 2004 11:16 am

Am using the release of SP1.

I have uninstalled the framework and reinstalled it, however I would really like to be on SP1 as for the past year I have been using hot fixes that were only made public 1 month ago...

Dino · Post by **Dino** » Tue Aug 31, 2004 11:18 am

jclausius wrote:
Dino wrote:so do we have to restore the database?
No need to just yet. I'll update this when I have more info.

Can I ask you try try something? Try a restart of IIS (iisreset.exe) on the Vault server. Now try to log into the server. Does everything appear to be OK?

At the time I actually uninstalled the server and reinstalled it, as we were upgrading that to 2.0.5 as well as moving the db to another server, but a simple upgrade failed so a full reinstall was done.

The server unfortunately has other live websites on it that prevent me from doing a reset unless absolutely necessary.

Post by **jclausius** » Tue Aug 31, 2004 11:37 am

What .Net Framework is the server running? 1.1 or 1.1 SP1?

Dino · Post by **Dino** » Tue Aug 31, 2004 11:40 am

Just 1.1 at this stage - the hot fixes I am using are for development issues only.

Post by **jclausius** » Tue Aug 31, 2004 11:47 am

OK.

If you've only installed .Net 1.1 SP1 on your client machine, then you definitely don't need to worry about restoring the database for the Vault server, as it will remain unaffected.

CraigNicholson · Post by **CraigNicholson** » Tue Aug 31, 2004 1:57 pm

DinoNZ wrote:Service Pack 1 was released recently, and after installing it Vault simply doesn't run - the exe shows in task manager, but nothing happens even after several minutes - no errors, no nothing.

I have other VS.Net 2003 projects running, and they all seem to be fine - any suggestions?

You might want to try the following two solutions. If you want you could backup the key from the command line with the following command:

Code: Select all

REG EXPORT HKCU\Software\SourceGear\Vault\Client\Settings %TEMP%\VaultClientSettings.reg

1. I found that if I changed the FormMain value under HKEY_CURRENT_USER\Software\SourceGear\Vault\Client\Settings by changing the FormMain.SelectedTabIndex from 2 to 0 (e.g. "(FormMain.SelectedTabIndex,0)") then the client would start up successfully.

2. Delete the key HKEY_CURRENT_USER\Software\SourceGear\Vault\Client\Settings and try start the client. The following will do that for you:

Code: Select all

REG DELETE HKCU\Software\SourceGear\Vault\Client\Settings

I am interested if any of those fix the problem for you as they did for me.

- Craig.

Post by **jclausius** » Tue Aug 31, 2004 2:14 pm

Dino wrote:... however I would really like to be on SP1 as for the past year I have been using hot fixes that were only made public 1 month ago...

Dino:

Just in case you missed it, our internal testing of the 1.1 .Net SP1 framework shows the SP1 causes no known issues with Vault 2.0.5.

If you need to, you should be able to re-apply the SP1 patch.

However, your problem is a bit perplexing. You mentioned you went back to the normal 1.1 .Net framework, and from some of your other posts, it appears the GUI client is working again. Is this correct?

- Did the Vault GUI client start working as soon as you switched back to the original 1.1 .Net framework?

- Is it safe to assume you left the Vault client alone while you re-installed the 1.1 .Net framework?

SourceGear Support

Vault fails to run on Framework 1.1 SP 1

Vault fails to run on Framework 1.1 SP 1

More info...

Re: Vault fails to run on Framework 1.1 SP 1