Home Dashboard Directory Help

SSMS 2008 fails to import SQL Instances registered in SSMS 2005 by Kurt Moskal


 as Won't Fix Help for as Won't Fix

Sign in
to vote
Type: Bug
ID: 366121
Opened: 9/4/2008 1:03:49 PM
Access Restriction: Public
User(s) can reproduce this bug


I installed the SQL Server 2008 client tools on my Windows XP workstation – I did a side-by side install. When I open SSMS 2008 it prompts me with the following messagebox:

TITLE: Microsoft SQL Server Management Studio
There are SQL Server 2005 Management Studio registered servers on this system. Do you want to add them into Microsoft SQL Server Management Studio? Adding the server registration information has no effect on the servers themselves.

I press the yes button and I get the following error:

TITLE: Previously Registered Servers
The operation 'Upgrade' failed. (Microsoft.SqlServer.Management.RegisteredServers)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.0.1600.22+((SQL_PreRelease).080709-1414+)&LinkId=20476
Key not valid for use in specified state.
Sign in to post a comment.
Posted by Maassql on 8/5/2010 at 8:50 AM
Seriously, why would one want / expect as part of the import of an xml file that every server one has access to be contacted? Isn't the feature primarily for large lists of servers? In my case, all are behind a firewall. Poor design. If you have to keep the 'test connection' part in, at the very least, skip to the next server
Posted by DaveMac on 5/25/2010 at 10:03 AM
"not a common enough customer scenario"?? I had no idea MSFT ignored errors simply because it doesn't affect enough people. Well it's affecting me too. I had at least 30 registered servers organized neatly in several folders under SQL 2005 and now my Dev Edition SQL 2008 won't recognize them. This is disasterious! I am on Vista. PLEASE HELP! It's been a couple of years since this problem was reported, there must be a solution?
Posted by Microsoft on 6/30/2009 at 2:52 PM
Hello Kmoskal,

Unfortunately, this issue was triaged as "won't fix" since this is not a common enough customer scenario. If this issue critically affects your usage of registered servers, then please reopen the bug.

Posted by CharissaJB123 on 11/4/2008 at 12:12 PM
I notice in the error above (SQL_PreRelease). I am not using a PreRelease. I am using SQL Server 2008 Developers Edition.
Posted by CharissaJB123 on 11/4/2008 at 12:09 PM
I am having same error but on a Vista system. Checked all my registrations in 2005 and they are valid.
Posted by Microsoft on 9/5/2008 at 5:32 PM
Hello Kmoskal,

Thank you for reporting this problem. Can you check if the data connection information you have mentioned for the Registered Server in SSMS 2005 are still valid? From the error message it looks like some db connection(s) may be stale.


Program Manager | SQL Server
Sign in to post a workaround.
Posted by swh1 on 7/17/2009 at 3:11 AM

Before attempting to export from MSSMS 2005, go through all of your Registered Servers and ensure that they all connect; delete any that don't.

Posted by mkincaid on 1/30/2009 at 11:45 AM
I had this issue and noticed that SSMS 2008 imported most of my servers up to a certain point. I went into SSMS 2005 at the point where SSMS 2008 failed and sure enough, the next server wasn't properly registered. It is in a seperate domain and needs SQL Auth and I don't connect to this particular instance very often so I hadn't setup the SQL user/pass since I imported it into SSMS 2005.

I went into the properties for that server, entered the proper credentials and saved it. I then went back to SSMS 2008, right clicked on Local Server Groups, Tasks, Previsouly Registered Servers, and clicked Yes on the box asking to import the server registrations and it worked! Now all of my server registrations are in SSMS 2008.

So find the last server that registered server in SSMS 2008, then check the next one in SSMS 2005. In the example below, SERVER04 isn't registered properly, so SSMS 2008 won't get to SERVER05-SERVER08, even if they are registered properly.

SSMS 2005        SSMS 2008
---------        ---------
SERVER01        SERVER01
SERVER02        SERVER02
SERVER03        SERVER03

Hope this helps.