Fix Export/Import of Registered Servers WITH Passwords
I just did an Export of Registered Servers from one machine, running SSMS 17.5, followed by an IMPORT of that file in a machine running SSMS 17.6. Upon exporting, I left the check box blank for "Do not include user names and passwords in the export file". Yes, I am aware that it is a security risk, but I don't want to have to re-enter all my passwords again.
Upon import, I got about a dozen errors stating "Key not valid for use in specified state." (I'm in Connecticut. Does it only work in Washington state?)
Then it says, "Import successful." BUT A) ALL passwords are missing, and B) Half the registered servers are missing under sub-folders.
THIS IS ****. It's as bad as the Export/import of Edge Favorites.
Come ON. AND, I get those SAME 14 Errors EVERY TIME I open SSMS.
Am I going to have to fix them all manually?
I DELETE ALL Registered Servers on the new machine, EVEN the ones that used Windows Integrated Authority in order to make the errors stop.
Step 3: Export WITHOUT saving passwords. That got all entries, so now I just have to go lookup all those Usernames and passwords.
Craig Balsillie commented
this has been under review for more than a year..
Has their been any progress with it?
Has anyone been able to suss out a workaround?
Slobodan Popovic commented
Currently, this feature literally has no use whatsoever.
If I cannot save and import the registered servers to a colleague's computer or even mine after reinstalling the system, what is actually the point of it?
I sincerely hope they will address this in some manner.
Tim Wappat commented
Same here - "Key not valid for use in specified state" errors and imported servers are a mess. SSMS 17.9.1
Aldo Gonzalez commented
Agreed with Todd on encrypt with password. The ability to export locally registered servers (including passwords) is a needed feature. We got our PC's replace because of corporate hardware refresh, and now must expend all that time to collect and enter passwords for the SQL Server Authenticated logins.
I couldn't even delete mine, they do not show up
Same problem as described above, only I have one error not 14. I have tried several things, but nothing seems to solve this issue. I may have to delete each entry and add them back in one at a time. I agree with the comment on 10/4/2018 about encrypts a file with a key... Hope they have a solution for this.
Todd Chittenden commented
It encrypts the file with a key from the MACHINE? Who does THAT? Why is that piece of information not given to the user upon attempting this operation?
How about this: If you try to EXPORT your registered server and want to INCLUDE saved passwords, THEN it should REQUIRE a password to encrypt the export file.
Simple, useful, self-explanatory to the user!
Kevin Bernard commented
It appears that it will only import with the passwords on the same machine so if you have to uninstall and reinstall, export first. In our corporate environment, we all have unique machine names and that seems to be the key that tries to decrypt the passwords. If it's not on the same machine, they fail.
Same issue. There goes several hours of my time...
Todd Chittenden commented
Oh, and upon IMPORT, it switched all the SQL Server Authentication entries to Windows Authentication.
What an EPIC FAILURE. Do they TEST this stuff before they release it?