Recreate IssueIn the RegSrvr.xml, you will have the following entries for every server you have attached to SQL Server Management Studio or SSMS.
ConnectionStringWithEncryptedPassword
These are the encrypted passwords for your SQL Server instances in SSMS.
Resolve IssueThis article describes two methods for doing the same thing.
Option #1 was added on 4/30/2023 in correspondence with a video that will soon be uploaded to our YouTube channel. (Link will be posted shortly.) and is the quicker way of performing this action.
Some changes have also been made to the original instructions as well.)
There are two locations where the RegSrvr.xml file will be.
[Option #1][Location #1:]C:\Users\{user}\AppData\Roaming\Microsoft\SQL Server Management Studio\RegSrvr.xml Open the file in Notepad, Notepad++, or another editor.
Perform a search and remove the lined sections containing the worded phrase [ConnectionStringWithEncryptedPassword] from location #1 above.
(Do not edit the copy in location #2 as it is a template for location #1)
[Location #2: ]C:\Users\{user}\AppData\Roaming\Microsoft\Microsoft SQL Server\140\Tools\Shell\RegSrvr.xml [Option #2]Close SSMS
In Location #1, change the name of the file.
Leave the file in Location #2, as it is a template for the file in Location #1.
Load SSMS again after changing the #1 file, and a new file will be created.
- Choose [View]
- Then choose [Registered Servers]
- Expand [Database Engine]
- Then Expand [Local Server Groups]
- Next, Right-click on each of the Servers and select [Properties]
- When the Dialog opens, type in the Username and Password.
Next, click on [Test]
If the connection is good, you will receive the following message.
Edit Server Registration Properties
The connection was tested successfully.
After receiving the above message, click the check box beside [Remember password].
Then click [Save]
Perform the above on each Registered Server until you have completed your list.
At the moment, there is no other workaround.
I read and tested what one person on Stack Exchange stated by creating a new password, copying it, and pasting it in place of the old passwords that are the same. Unfortunately, this information was FALSE. I tested it and received the same error described in this KB article.