"Application has generated an exception" starting

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
amunoz
Posts: 3
Joined: Thu Apr 21, 2005 12:10 pm

"Application has generated an exception" starting

Post by amunoz » Thu Apr 21, 2005 12:30 pm

Vault had been working fine on our "build box" for months (a Win2K Pro workstation). Today we found our free disk space on the box to be just over 200MB. We removed some user profiles and some applications that we did not need on the box (i.e. Microsoft Office 2000, SQL 2000 Server, Win2K admin tools, Adobe Reader 5.0). Then when we tried to run Vault we saw this error message appear and Vault would not start:
VaultGUIClient.exe - Common Language Runtime Debugging Services
Application has generated an exception that could not be handled.
Process id=0x5e8 (1512), Thread id=0x5e0 (1504)

We uninstalled and reinstalled the Vault Client, rebooted the system and ran into the same problem again.
Has anyone ran into a similar issue? Any help would be greatly appreciated.[/i]

amunoz
Posts: 3
Joined: Thu Apr 21, 2005 12:10 pm

Post by amunoz » Thu Apr 21, 2005 12:48 pm

I entered the version number of the Vault client in the subject of the original post, but it looks like the post was truncated. We are using version 2.0.6

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Fri Apr 22, 2005 7:25 am

Is it possible you removed some of Vault's cache files and not others? Vault stores its caches files in the Docs & Settings folder of the user who is logged in while Vault runs.

However, Vault recovers fine if all the cache files are deleted. You may want to try to find and remove all of them and then try it again.

amunoz
Posts: 3
Joined: Thu Apr 21, 2005 12:10 pm

Post by amunoz » Wed Apr 27, 2005 8:13 am

That seems to have been the issue. The first time I logged on to the build box there was not enough space to load my roaming profile, so it created a local profile. After we freed up some space it was able to grab my roaming profile, but Vault displayed the aforementioned error. I simply deleted the local copy of my profile, logged in with a fresh copy of my roaming profile, and it worked just fine.
Thanks!

dstuckey
Posts: 3
Joined: Thu Apr 27, 2006 12:03 pm

Post by dstuckey » Fri Apr 28, 2006 9:03 am

dan wrote:Is it possible you removed some of Vault's cache files and not others? Vault stores its caches files in the Docs & Settings folder of the user who is logged in while Vault runs.

However, Vault recovers fine if all the cache files are deleted. You may want to try to find and remove all of them and then try it again.
I think we're having this same problem, but I am not very familiar with any of this. Are these cache files located under docs&settings-user-local settings-temp? I have files here with the name vault followed by a string of numbers/letters? You're saying by clearing these files did not adversely affect vault and solved your problem?

Post Reply