Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, March 8, 2017 8:54 AM
Hi,
after days and weeks of no issues the message "please wait for the system Event Notification service" is displayed when logging off from an RDP session to Windows Server 2012 R2. Due to the issue it is not possible to logon/logoff anymore.
The Server is a VM running on Microsoft Azure but I think this is a native Windows issue. When searching the internet then is looks like the issue is there for yearsalready and different versions of Windows Server are affected. Some described workarounds like killing the SENS process are mentioned, but not a real fix of the root cause. It happened the second time now and the only way to solve was a hard reset of the Server.
Any hint to solve this issue is very much appreciated.
Regards
All replies (10)
Wednesday, November 1, 2017 9:28 AM âś…Answered
Yes, the issue with this was related to SSMS trying to send telemtry data back to Microsoft, this was hanging and causing the process not to exit. The solution we went with was to disable the sending of telemetry all together using this registry key:
[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\Telemetry]
Name = DisableSqmUploader
Type = REG_DWORD
Data = 00000001
Sam Cogan Microsoft Azure MVP
Blog | Twitter
Thursday, March 9, 2017 8:55 AM
Create a Technical Support Ticket as our engineers would need to work with you on the issue and would require more details like on the issue to find the root cause of the issue.
https://azure.microsoft.com/en-us/support/options/
Thursday, March 9, 2017 9:07 AM
Are you running SQL Server Management Studio on the machine? We've seen some issues with SENS related to this and have an open ticket to investigate. A workaround for this is to kill the SSMS process in task manager, then SENS starts working again.
Sam Cogan Microsoft Azure MVP
Blog | Twitter
Tuesday, October 24, 2017 4:27 PM
Hi Sam,
Have you heard anything new on this? We are experiencing this issue and killing the SSMS process allowed the users to log on/off normally.
Thursday, October 26, 2017 5:32 PM
Can you look at the following:
1) Machine up to date with windows updates
2) Any antivirus software running?
3) If looking at the System logs do we see any services hanging? Same with Application logs.
4) Are they aware of any recent changes made to the system?
-Micah
Thursday, March 22, 2018 10:24 AM
Hi,
I'm still not sure how to fix it but I've a work around to solve it without a hard reset.
Another User who is still able to Login to the affected server should kill the process: svchost.exe (Command Line: C:\Window\system32.svchost.exe -k netsvcs
After killing this process I was able to Login again.
Regards
Hiro
Thursday, March 29, 2018 5:51 PM
Thank you sharing the information.
Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other com
munity members
Thursday, August 2, 2018 8:53 AM
is this safe? Isn't it an important system service? Will this affect other logged on users when we kill this? What then when you do it, does it start again or you have to start it?
Monday, August 6, 2018 11:37 AM
No, you don't really want to Kill <g class="gr_ gr_38 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling" data-gr-id="38" id="38">svchost</g>. You should be able to implement the registry key as I mentioned and resolve this issue.
Sam Cogan Microsoft Azure MVP
Blog | Twitter
Thursday, October 24, 2019 3:17 PM
This registry edit is the only solution I have seen for this problem - and it does not work for me. I have pushed out the edit via a GPO and verified it has applied to all users. However, this issue persists. It is absolutely related to either SSMS or VS.