Error Initializing Vault in ComInit():

Sylvain Martel · Post by **Sylvain Martel** » Wed Feb 13, 2008 2:14 pm

Hi ,

I have the following error on one of my programmer`s computer.

Error Initializing Vault in ComInit():
File or assembly name ohlq8hex.dll, or one of its dependencies, was not found.

I have recently upgraded to version 4.0.6 and everything went well except for that computer.

Try many time to re-install but each time I have the error but with a different DLL.

Search for that file on a computer that is OK and was not able to find it.

Please help me !

Thanks

lbauer · Post by **lbauer** » Wed Feb 13, 2008 2:59 pm

Can other users access Vault with no problems?

At what point does the user get this error? Is he/she using the Vault Client or Visual Studio?

If you log in as another user from this machine, do you still get the error?

Sylvain Martel · Post by **Sylvain Martel** » Wed Feb 13, 2008 4:04 pm

Hi, I have many other users that connect with Vault on different computers and everything is OK.

The problem seems to be on that specific machine. Tried with 2 different user accounts and I still get the error.

I can login directly to Vault Client but having problem from VS 2003 IDE.

Thanks.

P.S. I will be back at the office on friday so don't worry for late reply.

Sylvain Martel · Post by **Sylvain Martel** » Tue Mar 11, 2008 11:35 am

Hi , I wonder why I did not get any response from you yet.

Meanwhile, I tried a few things like clearing the cache, uninstalling the product + deleting all cach folders, re-installing but nothing new still getting an error message with a different DLL each time I try to open a project from VS 2003 that is under SourceGear control.

A prompt response would be appreciate.

Thanks

lbauer · Post by **lbauer** » Tue Mar 11, 2008 12:43 pm

I apologize for the delay in getting back to you.

We've seen this error on the Vault Server machine before, but not on a client machine. It appears to be a problem with the .NET Framework. We'd suggest uninstalling and re-installing the .NET Framework on the client machine as a first step.

Sylvain Martel · Post by **Sylvain Martel** » Mon Mar 17, 2008 11:23 am

I,

we did tried to uninstall and re-install DotNet Framework 2.0 -- Nothing has changed.

I also tried to uninstall the client, install 3.5.1 version and upgrade to 4.0.6. but also it did nothing.

So now, what's next ?

Thanks

Terence · Post by **Terence** » Mon Mar 17, 2008 2:15 pm

I have a few questions please.

Is this a problem with any project or a specific one?

If you create a brand new project and add it to Vault (from the problem machine), can you successfully open that one?

Can the same user successfully open projects from a different machine, with the same Vault login?

Sylvain Martel · Post by **Sylvain Martel** » Mon Mar 17, 2008 2:36 pm

Ok,

here are the answers.

The problem occurs for any existing project and also for all users on that computer.

I have created a new project but the error occured when trying to add it to Vault.

And yes the user is able to work with vault under is account on other computers.

Thanks

Terence · Post by **Terence** » Mon Mar 17, 2008 3:02 pm

Usually when this happens, there is some sort of anti-virus or other such process that's running in the background and interfering with Vault.

Can you please disable all anti-virus, spyware, malware software that's running on the machine please?

Sylvain Martel · Post by **Sylvain Martel** » Wed Mar 19, 2008 8:18 am

Hi

The only thing on that machine is Symantec Anti-Virus Corporate client.

I disabled it and the problem remains.

Thanks

Terence · Post by **Terence** » Wed Mar 19, 2008 9:03 am

Can you tell me what happens, if you switch to our Enhanced plugin?

Sylvain Martel · Post by **Sylvain Martel** » Wed Mar 19, 2008 11:32 am

What is the enhanced plug-in ?

Terence · Post by **Terence** » Wed Mar 19, 2008 11:48 am

I'm sorry. I misread your earlier posts. I understand now, that you're using Visual Studio 2003. There is no enhanced client for VS 2003, so please disregard my previous post.

Well, I'm not sure what would cause these issues on the machine in question. If you're positive that there aren't any anti-virus, malware, spyware processes running in the background, I have one more suggestion, but I need to know a few things first.

What is the OS on the machine?
Is it a 64-bit machine with a 64bit OS?
Do you have any other SourceGear products installed on it?

Sylvain Martel · Post by **Sylvain Martel** » Wed Mar 19, 2008 12:13 pm

Hi

OS is Win 2000 Pro English

And no there is no other SourceGear product on that machine.

Thanks

Terence · Post by **Terence** » Wed Mar 19, 2008 12:33 pm

Uninstall Vault completely, and after you uninstall, go here and download the Windows Installer Clean Up Utility from Microsoft.

Then run that tool and remove all traces of SourceGear products from your registry.

Next, reinstall SourceGear Vault.