"The operation could not be completed" error when using VSS.

I have VS 2002 installed with VSS 6 which used to work fine until installing VS 2003. Now when I check something in/out of VSS in VS 2002 I get an error saying "The operation could not be completed", although I get this error the item is checked in/out ok.

I haven't been able to try this in VS 2003 to see if I get the error because we currently don't have any 2003 projects.

Could someone let me know what's causing this error and how to fix it please

Thanks!


Answer this question

"The operation could not be completed" error when using VSS.

  • deo1979

    Does it provide any more information besides 'The operation could not be completed'



  • Jonas.Lewin

    No, that is all it says, there is only an OK button. That's it.

    I have also noticed that I now get "Unknown Error: 8007007F" when trying to return all rows from a SQL server table/view. This happens on both my locally installed MSDE (8.00.384 SP1) as well as the SQL server installations (8.00.760 SP3, 8.00.842) we have.

    I'm running w2k SP4 with MDAC 2.8 RTM installed. I have checked the oledb32.dll (in c:\program files\common files\system\ole db) and it's at version 2.71.9030.0.

  • Rick Walker

    To make matters worse, in SQL Enterprise Manager I now don't have the option to run the SQL Query Analyzer from the Tools menu, it is greyed out, as is SQL Profiler, although they both work from the start menu..

  • Thithi32

    Possibly
    PRB: "Operation Could Not Be Completed" Error Message During Project ID: 320860 http://support.microsoft.com/ id=320860

    You might also check to see if the project is bound to the correct location under the menu
    file | Source control | change Source control

    If ration Clearcase is installed or some other 3rd party Source Code control there could be problems in the registry. Make sure the complete path to the 3rd party installed products sourceSafe integration dll (e.g ssccc.dll) is included.

  • A.M.Khan

    I have solved the problem, after much googling...

    Use Component Checker to see what version of dll's you have, more specifically what version on oledb32.dll (c:\program files\common files\system\ole db\).

    Although Component Checker said I had MDAC 2.8 RTM installed the version of oledb32.dll was 2.71, and so were quite a few other dll. Infact only about 4 dlls were actually 2.80, I had dll's from MDAC 2.5 on my machine.

    Get the MDAC_TYP.EXE, copy it to you c drive, unpack the exe by running this:

    C:\mdac_typ.exe /c /t:c:\MDACSetup

    You can then try running "C:\MDACSetup\Setup.exe /gc C:\Mdaclog.txt" from start > run, but this didn't work for me, didn't even create an empty log file, I can only assume that since it said I already had v2.8 it didn't actually install anything but I would have still expected a log file to say that!

    If you're unlucky enough for that not to work
    , unpack (winzip, power archiver etc) the cab file called "mdacxpak.cab" to C:\MDACSetup\mdacxpak\

    Then navigate to C:\winnt\inf\ and find mdacxpak.inf, right click and click install. When prompted browse to C:\MDACSetup\mdacxpak and click the "Retry" button. This should install the dll in that folder.

    Run Component Checker again and the oledb32.dll should be at 2.8, as should a lot of other dll's. When I ran Component Checker after doing this I only it still said v2.8 RTM but in the File Details section I now only have "MDAC 2.8 RTM".

    I've tried out SQL and I can now return all rows and checking in/out of VSS via VS2002 works perfectly.

    Below are links to info I found.

    http://msauer.mvps.org/images/error.pdf
    http://support.microsoft.com/default.aspx scid=kb;en-us;232060

    If you don't want to upgrade only part of the MDAC installation, try uninstalling MDAC completely (or right click, install on MDAC.inf which will install the OS version) then reinstall v2.8.

  • vbnetcoder

    We are having the same problem, but with Beta 1 of VS and VSS 6.0d.  I haved noticed when you are opening a somewhat large solution, that sometimes it lookes like while it is opening all the projects and files related to that solution, that for a little while everything is checked, as if you had checked them all out.  Once it has completely opened that solution and is ready again, it no longer looks like you have those things checked out.  This error message ("The operation could not be completed") seems to occur whenever someone has something checked out.  I dunno, I think Source Safe, when integrated with Visual Studio, has a lot of problems.


  • "The operation could not be completed" error when using VSS.