- Remove From My Forums
-
Вопрос
-
На сервере терминалов Windows Server 2012 появляется ошибка в журнале событий:
Источник: Winlogon
ID: 4005
Не найдено описание для события с кодом ( 4005 ) в источнике ( Winlogon ).
При этом пользователь при подключении видит черный экран. Помогает только перезагрузка сервера. Что может быть?
Ответы
-
Разобрался. На одном из DNS серверов стоял неправильный адрес пересылки. Исправил. После этого все работает отлично.
-
Помечено в качестве ответа
16 марта 2013 г. 16:19
-
Помечено в качестве ответа
-
-
Предложено в качестве ответа
Petko KrushevMicrosoft contingent staff, Moderator
15 марта 2013 г. 11:51 -
Помечено в качестве ответа
Черепко Валерий
15 марта 2013 г. 23:58
-
Предложено в качестве ответа
- Remove From My Forums
-
Question
-
This is a Windows 2012 Server Datacenter that hosts VMs (Hyper-V) for a development environment. Since a while RDP sessions do not work. the RDP client connects fine, a black screen appears and than closes. At the same time the event id 4005 is logged «winlogon
terminated unexpectedly».
I went through the main sources that appear on a google search nothing applies or works.
The machine is also a domain controller.Any advise?
Gerhard Waterkamp ACSLA Inc.
-
Edited by
Monday, March 10, 2014 6:52 PM
-
Edited by
Answers
-
-
Marked as answer by
Dharmesh SMicrosoft employee
Friday, March 21, 2014 7:25 AM
-
Marked as answer by
We have this issue on many 2012 RDS session hosts. The issue has been seen at different clients with different set ups, some have a simple 1 session host RDS server, some have 4 or 5 session hosts in a load balanced farm with RD gateway, connection brokers, RDWeb, ect. The problem in simplest explanation:
A user will call the help desk saying they cannot access the server. They will get an error when RDP is trying to connect.
We check the session hosts, and will find many errors:
«Event ID 4005 — The Windows logon process has unexpectedly terminated»
At that point in time, users who are currently logged in may be able to still work, or their session may lock up (it is not consistent).
Regardless of the current users logged; after the logon process crashes, it continues to crash upon every user attempt to log on. It will happen indefinitely until the server is rebooted. We can not log in, not even via console until the server is rebooted.
Then, everything works fine for some amount of time (not consistent) it may be a couple of days, or it may be weeks, or a month even.
We have had the case open with Microsoft for about two months and they cannot determine what is wrong.
I believe I may have found a possible cause; Webroot Secure Anywhere antivirus. Since we have tried everything from moving from roaming profiles to local profiles, removing all printers, blocking inheritance of GP, fresh server builds with minimal software, ect — it has to be something that is consistent across the board on all servers.
The only thing I can find consistent across the board is the Antivirus; Webroot.
I am curious if anyone else is having this issue? I would like to pin point this to something but it is so intermittent and we cannot force replicate the problem.
Перейти к содержимому
В итоге помогло следующее:
1. Удалить KB3172614, перезагрузка
2. Если есть, удалить KB3197875, перезагрузка
3. Установка KB3197875, перезагрузка
4. Установка KB4012213 + KB4012216, перезазгрузка
Проблема ушла после этих шаманств с установкой-удалением и перезагруками
Мне лично помог 1 шаг.