Check-In with VSTS2005/VSS2005 - Unexpected error encountered.

Here's the rest of the error.

It is recommended that you restart the application as soon as possible.

Error: The specified procedure cannot be found.

File: vsee\internal\inc\vscomptr.inl

Line number: 618

I've uninstalled VSS 2005 and reinstalled with no change. An MSDN Forums search turned up a recommendation to reinstall Windows Script (http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=183874&SiteID=1) but that didn't change things either. Moreover, a search of my system says that the file vscomptr.inl doesn't exist at all.

What ever is going on

Sean

Answer this question

Check-In with VSTS2005/VSS2005 - Unexpected error encountered.

SQL_Menace

I am sure started getting this error after uninstalling "firefly compare" product for SQL Server...,

Registering OleDB32.dll (Regsvr32 "full path\OleDB32.dll") solves the problem for me too...
Matt Morehead

Registering OleDB32.dll (Regsvr32 "full path\OleDB32.dll") solves the problem. I am not sure but I think I started getting this error after uninstalling Visual studio 6.

Manoj
msumption
Hi,

The vsee\internal\inc\vscomptr.inl is a path in VS2005 sources; you don't have the vscomptr.inl file on your disk. The information is displayed for debugging purposes, to help us pinpoint the problems in Vsee codebase.

In particular, the error from line 618 means a failure to co-create the OleDB Conversion Library (C8B522D1-5CF3-11CE-ADE5-00AA0044773D). This error message means that you have a problem with the OLEDB installation on your machine.

The OleDB Conversion Library should be normally registered by "C:\Program Files\Common Files\System\Ole DB\oledb32.dll". I have no idea what is the relation between WindowsScriptingHost and OleDB, but it looks that in some cases reinstalling WSH fixes the problem.

If that doesn't work, I'd try re-registering the the OLEDB dlls (by using "regsvr32 oledb32.dll", hopefully the dll is the right version), or I'd try reinstalling OLEDB (and that should update the right version of dlls and register them correctly).

Alin
pelicanous
Reregistering the oledb worked for me too. Pretty sure installation of the Crystal Reports V9 Toolkit broke it in the first place. Thanks for the info.
Michael_001

Thanks

I also had this problem when trying to open from sourcecontrol in VS2005, reregistering oledb32.dll has solved this for me. But no clues what caused the problem I'm afraid.

Ken
Ronald Wessels
I experienced the same problem, and I could fix it (following your clues) by reinstalling the JET 4 package (Windows2000-KB829558-x86-FRA.exe for french users) AND by re-regstring MANUALLY the OLEDB dll (regsvr32 "C:\Program Files\$(CommonFiles folder)\System\Ole DB\oledb32.dll")

I think the problem came from the uninstall of a "bad installed" or "bad packaged" IBM database access component.

thx++
shikwai
Problem Solved… [I was getting this Error with TFS on http]

1> Remove TFS server from Team Explorer

2> Restart the Visual Studio

3> Reconnect/Add the TFS Server….

And the problem is solved.
Anshul Tandon
Same thing happend on my machine after uninstalling Firefly Data Compare Tool. re-registering the dll as noted above solved the problem.
Check-In with VSTS2005/VSS2005 - Unexpected error encountered.

Answer this question