This is cracked. If you have this issue and use SSMS 17 install these updates in this order: KB3022398, KB3165756, KB4336999. *mic drop*
Here's what I've attempted:
* Upgrading from SSMS 17.9.0 to SSMS 17.9.1, reboot, patch still required and fails.
* Uninstall SSMS 17.9.1, reboot, patch still required and fails.
* Install SSMS 18 Preview 6, reboot, patch still required and fails.
* Manually install VS 2015 Update 3 (which completes), reboot, patch still required and fails.
This issue sucks and has caused many an in-place upgrade to fail. Having to alter the backup location of every instance to a local folder, then back again after upgrade, is a PITA.
FYI I have gone back and been unable to reproduce the failed login problem using the test I built so I'm unsure if there was user error here like mixed mode not being enabled?
However ConnectionContext does still leak passwords by extracting them from the SqlCredential and keeping them in plain text. So I'll leave the topic open.
Thanks so much for commenting with that. At least now I know I'm not going crazy and where I don't use SqlCredential I can show that explanation to justify why.Cody Konior shared this idea ·