VaultGUIClient.exe Application Error

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

Moderator: SourceGear

Post Reply
shraddha
Posts: 2
Joined: Tue Mar 28, 2006 3:33 pm

VaultGUIClient.exe Application Error

Post by shraddha » Tue Mar 28, 2006 3:36 pm

Hello,
I installed Client for sourcegear vault on my win xp professional machine. I get following error when i try to start the application
" The application failed to initialize properly (0xc0000005). Click on OK to terminate the applicaiton"

It does not even record any error in event viewer so that it can help me trace it

I would highly appreciate your help

Thanks,
Shraddha

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Tue Mar 28, 2006 4:03 pm

Have you tried uninstalling and reinstalling?

What operating system is the client installed on? What version(s) of the .NET Framework are on the Vault Client machine?

Are you having similar problems with any other applications?

I did an Internet search on this error and it's generally related to a problem with the machine -- but there's no one cause. It can be a conflict with a video driver, registry corruption, etc., so it may be hard to pin down.

One person disabled the splash screen for an app and that allowed them to open it. You can try this with Vault.

Find this registry key:
HKEY_CURRENT_USER\Software\SourceGear\Vault\Client\Settings
Set Show Splash to False.
Linda Bauer
SourceGear
Technical Support Manager

shraddha
Posts: 2
Joined: Tue Mar 28, 2006 3:33 pm

Post by shraddha » Tue Mar 28, 2006 4:38 pm

Thanks for prompt response

Yes i did try uninstalling and reinstalling twice but still it does that
and i even tried turning off splash in registry still i get that error.

I had vault running and all of a sudden it stopped this morning

Thanks

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

Post by dan » Wed Mar 29, 2006 1:18 pm

It sounded like this was a new machine installation, but your last note indicates it might not be.

Sometimes when the client doesn't invoke at all, it ends up being a framework issue. You might try re-installing the .Net Framework. Which version are you currently running?

Post Reply