# Visual Studio: Failed to load resource DLL ... c:\Program Files\Common Files\system\Ole\OLEDB32R.DLL

I am new to using Visual Studio 2005.  While attempting to use Visual Source Safe I am getting errors about failure to load a DLL.  AFAIK, nothing new was installed.  Though an old project (not connected to source safe)  was deleted.

I have searched on this error but have not found out how to resolve it.  Can anyone tell me the possible causes and how to fix it?

Error:
- Visual Studio: Failed to load resource DLL ... c:\Program Files\Common Files\system\Ole\OLEDB32R.DLL

Clicking okay yields another error:
- Unexpected error encountered.  It is recommended that you restart the application as soon as possible.

Error: A Dyanmic link library (DLL) inititalization routine failed.
File:  vsee\internal\inc\vscomptr.inl
Line number: 618
LVL 53
###### Who is Participating?

Commented:
This seems like an obvious question (that I'm sure you've already thought of), but...     Have you checked to see if the file is there?
On my WinXP SP3 box, I've got: C:\Program Files\Common Files\System\Ole DB\oledb32r.dll (Version 2.81.1132.0)
0

Commented:
Go to c:\Program Files\Common Files\system\Ole\    is OLEDB32R.DLL there?

0

Author Commented:
Thanks for the responses.  Yes, I checked and the file is there.  Do you know how I can check the dll version on XP?
0

Commented:
Just do a right-click... Properties.   There should be  Version tab accross the top
0

Author Commented:
Whoops, I think I have temporarily lost my brain cells on this one.

Yes, the file is there and it the same version: 2.81.1132.0
0

Commented:
Show us the line in the *.vbroj file that uses that reference... (just use notepad to open the file...)
0

Author Commented:
The error occurs while trying to retrieve the sources from source safe. So I don't actually have the locally yet.
0

Commented:
I don't use Visual SourceSafe... but I just assumed you could "check out" a file without lanuching the build process
0

Author Commented:
Yes, you can.  It is the check out process itself that is throwing the error.

Anyway, I am not sure what happened, but rebooting and un-registering/re-registering the DLL seems to have fixed the problem.  Thanks for the assist!

0

Author Commented:
It was a problem with the DLL after all.  So thanks for pointing me in the right direction.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.