Vault fails to run on Framework 1.1 SP 1

Dino · Post by **Dino** » Tue Aug 31, 2004 2:18 pm

jclausius wrote: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.

My testing would indicate otherwise...

jclausius wrote: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?

Correct.

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

Yes

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

No - I believe I installed SP1, then upgraded to 2.0.5.

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

Dino wrote:
jclausius wrote:Is it safe to assume you left the Vault client alone while you re-installed the 1.1 .Net framework?
No - I believe I installed SP1, then upgraded to 2.0.5.

So what is the state of your client at this point in time?

Vault 2.0.5 client installed?
1.1 .Net Framework installed?
1.1 .Net SP1 Framework installed?

This might be a red-herring, but what did you install for SP1?
( Our testing was done with NDP1.1sp1-KB867460-X86.exe )

Dino · Post by **Dino** » Tue Aug 31, 2004 2:33 pm

jclausius wrote:So what is the state of your client at this point in time?

Vault 2.0.5 client installed?
1.1 .Net Framework installed?
1.1 .Net SP1 Framework installed?

Vault 2.0.5 client
1.1 .Net Framework

It works... now in about 2 minutes, I will have SP1 again and will try the previous suggestions as well.

jclausius wrote: This might be a red-herring, but what did you install for SP1?
( Our testing was done with NDP1.1sp1-KB867460-X86.exe )

Same one...

Dino · Post by **Dino** » Tue Aug 31, 2004 2:44 pm

Dino wrote:It works... now in about 2 minutes, I will have SP1 again and will try the previous suggestions as well.

And wouldn't you know it. Works fine now with SP1.

Who knows what was happening before then... very weird. I had other applications that use web services, remoting over HTTP etc all running fine.

All is ok now - thanx.

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

Glad to see you are up and running.

endever · Post by **endever** » Thu Sep 02, 2004 5:11 am

Server v2.0.5 (.Net v1.1)
Client v2.0.5 (.Net v1.1 SP1)

I have also just installed SP1 for the .Net Framework (NDP1.1sp1-KB867460-X86.exe) I am getting the same problems described by the previous poster.

My vault client fails to show, the process is running in Task manager but nothing shows.

I have used the Work around shown in this thread (FormMain.SelectedTabIndex,0) in the registry, but this gets reverted back to (FormMain.SelectedTabIndex,2) everytime the client is started.

I have to merge a modified registry file with the registry every time I want to run Vault otherwise nothng shows.

Is this a recognised problem?

dan · Post by **dan** » Thu Sep 02, 2004 9:07 am

We are investigating this right now. It looks like if the status search pane doesn't draw correctly and if it was the active pane when you exit, Vault doesn't come up correctly until you remove the relevant registry key.

Shaw will have more info after we figure out what exactly is going on. Until then, remove the registry key and you should be able to use the client.

Don Thimsen · Post by **Don Thimsen** » Fri Sep 03, 2004 3:53 am

Using Windows Update on my WinXP Pro SP2 system now shows .net SP1 as a high-priority update. I'd guess that by tomorrow, most of our users will have . net SP1 installed on their Vault clients (I think most have automatic updates setup for "automatic installation").

I just installed SP1 on my vault client (2.0.5) machine, and have the same problem others have reported. I'll announce the registry workaround to make sure I only hear grumbles and not screaming...

Don

CraigNicholson · Post by **CraigNicholson** » Fri Sep 03, 2004 6:09 am

Don Thimsen wrote:Using Windows Update on my WinXP Pro SP2 system now shows .net SP1 as a high-priority update. I'd guess that by tomorrow, most of our users will have . net SP1 installed on their Vault clients (I think most have automatic updates setup for "automatic installation").

I can confirm that the updates were pushed to SUS (Software Update Service) servers in the last 24 hours. Lots of corporates will be upgrading by the end of next week for sure.

I'm corncerned with the solution for this problem as the 2 development builds of 2.0.6 that I received from Shaw do not seem to have resulted in any positive solutions. As a note, I'm still awaiting feedback from Shaw in this regard.

For now I am holding back the .NET Framework 1.1 SP1 from deploying in my office as I am concerned how the rest of the client and/or server components will be affected. If my development teams can't use source control effectively, we will need to switch source control systems so as not to put our development in any jeopardy.

dan · Post by **dan** » Fri Sep 03, 2004 8:10 am

We will have a 2.0.6 available very soon that addresses the problem. For some reason, SP1 is choking on rendering the checkbox in the status search pane, which then causes the app to lock up.

Until 2.0.6 is released, don't use the status search pane if you are using SP1

If you already used it, change HKEY_CURRENT_USER\Software\SourceGear\Vault\Client\Settings\FormMain.SelectedTabIndex to 0, as described above to get back up and running.

Note that this is a display problem with SP1, and that no server side data or client side settings are affected by it.

SourceGear Support

Vault fails to run on Framework 1.1 SP 1

Re: Vault fails to run on Framework 1.1 SP 1