"The specified procedure could not be found." when checking out in VS.NET

[Jeff Key]

Hello,

First, I apologize for the crosspost; I'm not sure to which of the three VSS
groups this should be addressed.

I'm getting an error when I try to check out that says "The specified
procedure could not be found.". I'm then presented with the usual checkout
box, but with only the "Items below solution xxx" and "Files below project
xxx" items available; both checked. If I press OK, then only the file I
wanted to check out is checked out.

I get the same behavior when trying to check in.

I've been using VS.NET + VSS full time since beta 1 on over a dozen machine
and never had this problem before. There are a couple of things that I
believe may have led to this (which I outline below), but I'm not sure how
to debug this situation (ie. find out what exactly is causing the error). I
recall seeing a reference somewhere long ago about starting DEVENV in debug
mode, but I can't figure out how to go about it.

I had installed the C# Refactory plug in and that worked for a while, but
then started causing random IDE error dialogs, but only upon right-clicking
nodes in the Solution Explorer tree. I uninstalled it, but it left remnants
of menus scattered throughout the context menus. No problems with source
control, though.

Then, a few weeks after that, I upgraded my eval version of XP Pro SP1 to
full version of slipstreamed SP1. This is when the problems started
happening. (Note that I had only used this eval version for a month or
so..all of my past experience was on XP beta prior to release and XP RTM
after release.)

I tried uninstalling and reinstalling VSS from the VS.NET 2002 kit w/o luck.
Tried installing VS.NET 6.0d and that didn't help. I uninstalled that and
VS.NET 2002. Reinstalled VS.NET 2002 + VSS 6.0c. Problem persists.

I'm afraid that if I can't get this resolved I'll need to reinstall the OS
and I'd really like to avoid that as I'm short on time. If someone can tell
me how to get more verbose error messages perhaps I could figure this out
myself.

Thanks
jk

[Jeff Tilly]

"Jeff Key" <sp...@sliver.com> wrote ...

> I'm getting an error when I try to check out that says "The specified
> procedure could not be found.".

I am having the *exact* same problem. Just started having it today. I
can't really recall doing anything exciting. I have a good number of
apps running when I started the operationb: VMWare, Outlook, Outlook
Express, a ton of IEs, etc. I started a recursive check-in on a large
solution and at some point during it -- after some projects had been
checked-in without any problems -- I received the same "The specified
procedure could not be found" error popup. I also have the same
problem you described if I perform a source control operation that
would display the select file dialog, like Undo Checkout, whereby I
get the same error popup 1st and then a list of files and the files I
selected are excluded.

SourceSafe operations still work but I could easily screw something up
if I can't see the file list in the operations that present a list of
files.

I rebooted and the problem persists. I could add a new project to
SourceSafe within VS.NET and this worked flawlessly. Then if I
performed any additional source control operations I get the same
errors.

VS.NET 2002 7.0.9492
Framework 1.0.3705

[M Schultz]

We are having the same problem on one machine here. We've
uninstalled/reinstalled SS and VS and it still doesn't work. Has anyone
found a solution to this yet?

"Jeff Tilly" <jtil...@hotmail.com> wrote in message
news:4d01abb1.03043...@posting.google.com...

[Matt Rolak [MSFT]]

Okay.. I think I may have found a 'fix' to this issue.

I've found another report of this issue and the problem seems to be a
registration/version issue for MSDART.DLL. On the effected systems it
seems the wrong version of this dll is being registered from
\Windows\System32.

If you can find a working machine, try to copy that machines version of
this DLL over to the bbroken machine. Once copied, try registering
oledb32.dll again (found at Program Files\Common Files\System\OLE
DB\oledb32.dll).

Essentially, if you want to be sure ahead of time, use the Dependency
walker on the oledb32.dll and see what version of MSDART.dll it is looking
for and try to replace the local version of that file with the 'right' one.

I'm trying to get a clearer set of fix-up instructions but hopefully this
can at least get some people started. As always, when replacing DLLs like
this make sure you create a backup copy in case the 'new' version is
actually worse than the old one. Please let me know if this fixes the
problem for you. Thanks!

Matt Rolak
VS Core Team
--
Help us be more effective by sending feedback about our posts.

From 1 to 5, how helpful was this posting?

5: Best : mailto:vsc...@microsoft.com?subject=5
4: : mailto:vsc...@microsoft.com?subject=4
3: : mailto:vsc...@microsoft.com?subject=3
2: : mailto:vsc...@microsoft.com?subject=2
1: Worst : mailto:vsc...@microsoft.com?subject=1
---

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
>From: "M Schultz" <mikesdne...@hotmail.com>
>References: <eX4D#Dh$CHA....@TK2MSFTNGP11.phx.gbl>
<4d01abb1.03043...@posting.google.com>
>Subject: Re: "The specified procedure could not be found." when checking
out in VS.NET
>Date: Thu, 19 Jun 2003 10:49:35 -0500
>Lines: 35
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
>Message-ID: <#Lxz3qnN...@TK2MSFTNGP11.phx.gbl>
>Newsgroups:
microsoft.public.sourcesafe,microsoft.public.visual.sourcesafe,microsoft.pub
lic.vstudio.sourcesafe
>NNTP-Posting-Host: 66.231.0.100
>Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
>Xref: cpmsftngxa06.phx.gbl microsoft.public.visual.sourcesafe:1807
microsoft.public.vstudio.sourcesafe:4087 microsoft.public.sourcesafe:3763
>X-Tomcat-NG: microsoft.public.visual.sourcesafe