November 19, 2024 at 9:25 am
We still have a couple of dino's.
What should I check to re-enable access to ye good old SQL 2005 on Windows 2003 for my SSMS 20.2?
I have already accepted "use server certificate" and "optional encryption"
Still doesn't work;
"SSL Connection forcebly closed by server"
btw: When using SSMS 18.12.1 it works fine
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
November 19, 2024 at 4:06 pm
Use an older version instead unfortunately.
As per the documentation, 20.2 is only tested on 2014 and above.
November 20, 2024 at 7:00 am
The stange thing is, on Windows 10 with SSMS 20.2, this still works.
What is different with Windows 11 ?
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
November 20, 2024 at 8:39 am
Probably allows the use of old legacy ciphers / algorithms, but just clutching at straws there, unsure of the internals.
We can only go on what the public documentation says.
Might be worth a ticket to MSFT, but they will probably tell you the same, it's to old upgrade or to use an older version of SSMS.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply