RDC Connection to Server 2012 causes program crashes
Recently every time I used RDC to access my server SSMS crashed with the following error -
Problem Event Name: CLR20r3
Problem Signature 01: Ssms.exe
Problem Signature 02: 2017.140.17119.0
Problem Signature 03: 591bcf8a
Problem Signature 04: PresentationCore
Problem Signature 05: 4.7.2053.0
Problem Signature 06: 58fa7405
Problem Signature 07: 149e
Problem Signature 08: 40
Problem Signature 09: System.DllNotFoundExceptio
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 5129
Additional Information 1: 5861
Additional Information 2: 5861822e1919d7c014bbb064c6
Additional Information 3: 5f25
Additional Information 4: 5f2531ae070278f893fa99352d
A suggested fix was to install v17 but that has the same problem.
I recently wanted to leave a powershell script running and when I logged in again both Powershell and SSMS crashed. A suggested fix was to repair .Net but doing that made no difference.
I can start them, close the session and open it again and both have the error. What update has Microsoft done to cause this?
Problem Event Name: CLR20r3
Problem Signature 01: Ssms.exe
Problem Signature 02: 2017.140.17119.0
Problem Signature 03: 591bcf8a
Problem Signature 04: PresentationCore
Problem Signature 05: 4.7.2053.0
Problem Signature 06: 58fa7405
Problem Signature 07: 149e
Problem Signature 08: 40
Problem Signature 09: System.DllNotFoundExceptio
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 5129
Additional Information 1: 5861
Additional Information 2: 5861822e1919d7c014bbb064c6
Additional Information 3: 5f25
Additional Information 4: 5f2531ae070278f893fa99352d
A suggested fix was to install v17 but that has the same problem.
I recently wanted to leave a powershell script running and when I logged in again both Powershell and SSMS crashed. A suggested fix was to repair .Net but doing that made no difference.
I can start them, close the session and open it again and both have the error. What update has Microsoft done to cause this?
Ben Personick (Previously QCubed)
This has got to be an issue with SSMS.
To clairify: You can open SSMS or PowerShell fine using RDP, but when reconnecting to that RDP session see that error?
Is this Windows Server 2012 or 2012 R2?
Is the reconnect to the RDP happening from the same workstation or a different workstation using a different resolution?
Do you actually see the crash on screen or is it only from the event viewer that one can confirm the crash (trying to figure out when does the crash happen - during the disconnect or reconnect)?
Also, can you please share the references that suggested installation of the latest SSMS (v17) as the fix?
Is the reconnect to the RDP happening from the same workstation or a different workstation using a different resolution?
Do you actually see the crash on screen or is it only from the event viewer that one can confirm the crash (trying to figure out when does the crash happen - during the disconnect or reconnect)?
Also, can you please share the references that suggested installation of the latest SSMS (v17) as the fix?
ASKER
Nakui,
It is the same workstation. Open an RDP session, I can start SSMS or Powershell. Close the Session and open it again immediately. I see SSMS is open and working and then the error message attached pops up on the screen.
This only started happening about a month ago and happens every time I connect.
The reference to installing the new version - https://community.spiceworks.com/topic/1974138-smss-sql-server-management-studio-has-stopped-working.
ScreenHunter_473-Jul.-09-09.02.png
It is the same workstation. Open an RDP session, I can start SSMS or Powershell. Close the Session and open it again immediately. I see SSMS is open and working and then the error message attached pops up on the screen.
This only started happening about a month ago and happens every time I connect.
The reference to installing the new version - https://community.spiceworks.com/topic/1974138-smss-sql-server-management-studio-has-stopped-working.
ScreenHunter_473-Jul.-09-09.02.png
In your RDP options, disable Printer Redirection. There are some issues with RDP printer sharing, in particular if no driver is installed on the server end, causing strange effects.
I agree. It could be a printer redirection, a path that is no longer accessible or a remote process that SSMS was linked to/using (maybe a 3rd party tool) which can't handle "suspending" the UI states. Did you (or your IT team) install any 3rd party tools on this server a month ago? Do you see any other errors in the same time-frame in the event viewer besides the SSMS crash?
ASKER
No other errors and I had switched off the printer support. I also tried setting up another account on the server that had the same problem. I then installed the VPN onto another PC in the office and used RDP and did not have the problem. So the issue is with my laptop. I will have to look into that further.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Nice Find!
ASKER
It solved the problem