Application has generated an exception that could not be

[mTab]

I have a user who is currently receiving the following error whenever he opens the Vault Client:

VaultGUIClient.exe – Common Language Runtime Debugging Service
Application has generated an exception that could not be handled
Process id=0xc14 (3092), Thread id=0x968 (2408)

We are currently running version 3.1.6 on the client and the server.

The problem started to occur out of the blue and the strange thing is that he can still work (check-in, check-out etc…) from within Visual Studio 2005 Team Suite.

Please Advise

[Beth]

Check out this post and see if it can apply to your situation as well: http://support.sourcegear.com/viewtopic.php?t=3665 and here's one more that received a similar error: http://support.sourcegear.com/viewtopic.php?p=16820

If neither of those fit, I'll need to know more about your set-up such as the server OS, client OS, .NET framework, etc. I'd also recommend setting up Client Side Logging.

[mTab]

I should have mentioned that I already searched the SourceGear forums and found both of those posts. The first one sort of applied only because we are running the client on XP Pro but it has 8GB of free space. I tried to delete the cache anyway to no avail.

Here are the specs you requested:

Server OS = W2K3 Standard Edition w/ SP1
Client OS = XP Pro Version 2002 w/ SP2
Server .Net Framework Versions = v1.0.3705, v1.1.4322, v2.0.50727
Client .Net Framework Versions = v1.0.3705, v1.1.4322, v2.0.50727

We turned on logging and found that it was not even getting to the point where the app would generate a log.

We loaded SysInternal's Filemon and a lightbulb went off as we were looking through the trace. This developer added an entry in his 1.1.4322 machine.config file for other .net development and that caused the problem. For completeness, the entry was as follows:

<runtime>
<developmentMode developerInstallation="true"></developmentMode>
</runtime>

Thanks, problem solved.

[Beth]

Thanks for posting your final results.

[M Wickardt]

Hi, I had the same symptoms, and this post pointed me in the right direction.

Reinstalling .NET 1.1 (dotnetRunTime11.exe, dotnetfx.exe, NDP1.1sp1-KB867460-X86.exe) did not fix the problem.

However, after reading this post, I renamed C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\config\machine.config to C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\config\machine.config.sav , and then ran only dotnetRunTime11.exe, and the problem was fixed.

Thanks, M Wickardt

[Beth]

Thanks for the update.