Post reply

Problem importing 2000 registrations

  • April 20, 2006 at 11:26 am

    #90887

    I know that you can import SQL 2000 server registrations into the 2005 mgmt studio by clicking "previously registered servers" under Database Engine.  But when I try that I get "failed to import servers registered by sql server 2000". 

    I can't find any information about that.

    I do have many servers registered in 2000 and I can see the registrations with Regedit.  Thanks for any ideas.

    Ken

  • April 20, 2006 at 2:12 pm

    #633366

    I know this is no help, but maybe it provides some solice to know that you're not the only one.  I have the same problem and I've been waiting for several days for someone to respond to me!  I even put a post on the MSDN forums and haven't gotten any response. 
      In addition to the error you mentioned, I have get the following
    "...
    Additional information:
    Attempted to read or write protected memory.  This is often an indication that other memory is corrupt. (ConnectionDlg)"
     
    Boy, that's encouraging!
     

  • April 21, 2006 at 5:32 am

    #633462

    I wonder if something went wrong in my installation.  I'm using the evaluation version.  I installed it on my laptop, uninstalled it, then 2000 enterprise mgr quit working so I reinstalled 2000 then reinstalled 2005.  Maybe something got wacky in the middle of all that.

    Have you installed 2005 SP1? 

    This must be a pretty rare problem - I can't find anything about it on the web or inside the Microsoft site.  Thanks

  • May 3, 2006 at 12:36 pm

    #635742

    I have the same problem doing the import of the SQL 2000 Registered servers.

  • May 3, 2006 at 12:43 pm

    #635745

    I still haven't figured it out.  I have now uninstalled the evaluation edition and installed the standard 2005 edition.  I still get the same error.  Since the error seems to come from the .net framework, I reinstalled that but I still get the error.

  • May 5, 2006 at 4:26 pm

    #636387

    darn it.  I forget to check this after uninstalling SQLExpress and installing the SQL 2005 Developer edtion (from VS2005).  But... I can report that after installing SP1 it worked!!  maybe they fixed it?  (I'm not uninstalling SP1 to find out! )
     
     

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply