Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Getting "specified procedure could not be found"

0 views
Skip to first unread message

Joel Rieder

unread,
Aug 11, 2003, 6:14:27 PM8/11/03
to
I'm getting a "specified procedure could not be found" when trying to check
out files from VSS using the VS.Net IDE. Does anyone know a fix for this? I
have done a re-install of VS.Net and and VSS and didn't fix the problem.

Thanks for any ideas

Joel


Joe Masters

unread,
Aug 12, 2003, 12:35:07 AM8/12/03
to
Did you also reinstall any of the service packs? VSS is on SP6, available
here:

http://msdn.microsoft.com/ssafe/downloads/sp/default.asp

Joe

"Joel Rieder" <jri...@nospamveer.com> wrote in message
news:O7vpIbFY...@tk2msftngp13.phx.gbl...

Jacob Yang [MSFT]

unread,
Aug 13, 2003, 4:45:43 AM8/13/03
to
Hi Joel,

Please verify that the versions of MDAC components are correct.
Registration of OLEDB32.DLL will fail if these files are out of synch. The
Depends utility will tell you which import DLL's are unresolved. updating
and manually registering the unresolved import DLL will enable succesful
registration of OLEDB32.DLL. Once this is registered restart VS.NET and
the source control menus should function correctly.

Best regards,

Jacob Yang
Microsoft Online Partner Support
<MCSD>
Get Secure! – www.microsoft.com/security
This posting is provided “as is” with no warranties and confers no rights.

0 new messages