Windows server 2012 r2 код 20499
Вопрос
We recently did a migration of our RDS Server to a brand new Windows 2012 R2 server.
All was working fine but we started to have this messages in the RemoteConnectionManager event log:
Log Name: Microsoft-Windows-TerminalServices-RemoteConnectionManager/Admin
Source: Microsoft-Windows-TerminalServices-RemoteConnectionManager
Date: 9/14/2016 8:42:53 AM
Event ID: 20499
Task Category: None
Level: Warning
Keywords:
User: NETWORK SERVICE
Computer: XXXXX.com
Description:
Remote Desktop Services has taken too long to load the user configuration from server \\xxxxx for user xxxx
Event Xml:
20499
0
3
0
0
0x4000000000000000
388
Microsoft-Windows-TerminalServices-RemoteConnectionManager/Admin
XXXX.com
\\XXXXX
agranados
Everytime this error message is logged the user gets disconnected from their RDS session.
So far we tried the following:
— Validate AD health (sites,subnet,replication, sysvol)
— We changed the DisableTaskOffload option as suggested in other posts
— We verified the group policy settings applied
Unfortunately we still haven’t found what the root cause of this issue is.
Any suggestion of similar previous experience is welcome.
Thanks in advance!
Regards. Cristian V.
Все ответы
Everytime this error message is logged the user gets disconnected from their RDS session.
So far we tried the following:
— We changed the DisableTCPOffload option as suggested in other posts
>>>How did you change the key DisableTCPOffload or the key DisableTaskOffload?
Based on my experience, to fix the problem, you need add a new DWORD (32-bit) Value in registry, name it as “ DisableTaskOffload ” and set value data to 1 on below mention path.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Sorry for the mistype,I wrote the wrong name.
As a matter of fact, I’ve changed the DisableTaskOffload parameter.
I ran the command Set-NetOffloadGlobalSetting -TaskOffload disable.
I’ve verified that the DisableTaskOffload DWORD key was correctly created.
What else do you think we can verify?
Thanks in advance.
Regards. Cristian V.
For event ID 20499, it means that it took longer than 5ms (milliseconds) reading the RDS user config from a domain controller, during the login process 5ms is nothing. Esentially LOAD_USERCONFIG_FROM_DC_TIMEOUT is reached in termserv.dll and the event is thrown. the timeout is hardcoded in the dll and cannot be adjusted AT ALL.
So , I suggest you try to find logs related with disconnect in Event Viewer under the path below, and post it to us for further research.
Application and services Logs\Microsoft\windows\Remote desktop service OR terminal service
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Thank you very much for the explanaition.
I’ve continue digging into the eventlog to find more details, under TerminalServices-LocalSessionManager I found the following informational events that seem to be related:
Log Name: Microsoft-Windows-TerminalServices-LocalSessionManager/Operational
Source: Microsoft-Windows-TerminalServices-LocalSessionManager
Date: 9/20/2016 9:36:44 AM
Event ID: 42
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: XXXX.com
Description:
End session arbitration:
User: XXXX\user
Session ID: 17
Windows server 2012 r2 код 20499
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Asked by:
Question
We recently did a migration of our RDS Server to a brand new Windows 2012 R2 server.
All was working fine but we started to have this messages in the RemoteConnectionManager event log:
Log Name: Microsoft-Windows-TerminalServices-RemoteConnectionManager/Admin
Source: Microsoft-Windows-TerminalServices-RemoteConnectionManager
Date: 9/14/2016 8:42:53 AM
Event ID: 20499
Task Category: None
Level: Warning
Keywords:
User: NETWORK SERVICE
Computer: XXXXX.com
Description:
Remote Desktop Services has taken too long to load the user configuration from server \\xxxxx for user xxxx
Event Xml:
20499
0
3
0
0
0x4000000000000000
388
Microsoft-Windows-TerminalServices-RemoteConnectionManager/Admin
XXXX.com
\\XXXXX
agranados
Everytime this error message is logged the user gets disconnected from their RDS session.
So far we tried the following:
— Validate AD health (sites,subnet,replication, sysvol)
— We changed the DisableTaskOffload option as suggested in other posts
— We verified the group policy settings applied
Unfortunately we still haven’t found what the root cause of this issue is.
Any suggestion of similar previous experience is welcome.
Thanks in advance!
Regards. Cristian V.
All replies
Everytime this error message is logged the user gets disconnected from their RDS session.
So far we tried the following:
— We changed the DisableTCPOffload option as suggested in other posts
>>>How did you change the key DisableTCPOffload or the key DisableTaskOffload?
Based on my experience, to fix the problem, you need add a new DWORD (32-bit) Value in registry, name it as “ DisableTaskOffload ” and set value data to 1 on below mention path.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Sorry for the mistype,I wrote the wrong name.
As a matter of fact, I’ve changed the DisableTaskOffload parameter.
I ran the command Set-NetOffloadGlobalSetting -TaskOffload disable.
I’ve verified that the DisableTaskOffload DWORD key was correctly created.
What else do you think we can verify?
Thanks in advance.
Regards. Cristian V.
For event ID 20499, it means that it took longer than 5ms (milliseconds) reading the RDS user config from a domain controller, during the login process 5ms is nothing. Esentially LOAD_USERCONFIG_FROM_DC_TIMEOUT is reached in termserv.dll and the event is thrown. the timeout is hardcoded in the dll and cannot be adjusted AT ALL.
So , I suggest you try to find logs related with disconnect in Event Viewer under the path below, and post it to us for further research.
Application and services Logs\Microsoft\windows\Remote desktop service OR terminal service
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Thank you very much for the explanaition.
I’ve continue digging into the eventlog to find more details, under TerminalServices-LocalSessionManager I found the following informational events that seem to be related:
Log Name: Microsoft-Windows-TerminalServices-LocalSessionManager/Operational
Source: Microsoft-Windows-TerminalServices-LocalSessionManager
Date: 9/20/2016 9:36:44 AM
Event ID: 42
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: XXXX.com
Description:
End session arbitration:
User: XXXX\user
Session ID: 17
Windows server 2012 r2 код 20499
Вопрос
На Server 2012 R2 в службе удаленных рабочих столов при подключении любого пользователя, получаю предупреждение 20499 — Службы удаленных рабочих столов затратили слишком много времени на загрузку пользовательской конфигурации с сервера server для пользователя администратор — по каким причинам получаю такое предупреждение и как его решить?
Ответы
В большинстве случаев это связано с функцией Large Send Offload (LSO) сoвременных Ethernet адаптеров который включен по умолчанию.
- Предложено в качестве ответа Petko Krushev Microsoft contingent staff, Moderator 25 февраля 2014 г. 7:04
- Помечено в качестве ответа Petko Krushev Microsoft contingent staff, Moderator 26 февраля 2014 г. 12:29
Все ответы
В большинстве случаев это связано с функцией Large Send Offload (LSO) сoвременных Ethernet адаптеров который включен по умолчанию.
- Предложено в качестве ответа Petko Krushev Microsoft contingent staff, Moderator 25 февраля 2014 г. 7:04
- Помечено в качестве ответа Petko Krushev Microsoft contingent staff, Moderator 26 февраля 2014 г. 12:29
На сервере 2012r2 с ролью hyper-v проверил все варианты лечений которые есть в инете ничего не помогает
отключал Large Send Offload (LSO) а также другие параметры tcp,
поставил в hyper-v чистую винду никакие роли не подымал только включил удаленное администрирование и сразу пошли предупреждения в логах при каждом подключении-
это проблема 2012r2 надо исправлять а не считать пользователей за идиотов.
также есть проблема с новыми интел процессорами спамят лог с ошибкой WHEA-Logger 19
msistat 0x90000040000f000, если в hyper-v запущена 32bit операционка.
5. Согластно спецификации от интел такие ошибки не являются ошибкой и отображать их не нужно. в линуксах уже исправили, куда писать в мс не знаю чтоб сделали патч для WHEA-Logger.
Windows server 2012 r2 код 20499
Question
На Server 2012 R2 в службе удаленных рабочих столов при подключении любого пользователя, получаю предупреждение 20499 — Службы удаленных рабочих столов затратили слишком много времени на загрузку пользовательской конфигурации с сервера server для пользователя администратор — по каким причинам получаю такое предупреждение и как его решить?
Answers
В большинстве случаев это связано с функцией Large Send Offload (LSO) сoвременных Ethernet адаптеров который включен по умолчанию.
- Proposed as answer by Petko Krushev Microsoft contingent staff, Moderator Tuesday, February 25, 2014 7:04 AM
- Marked as answer by Petko Krushev Microsoft contingent staff, Moderator Wednesday, February 26, 2014 12:29 PM
All replies
В большинстве случаев это связано с функцией Large Send Offload (LSO) сoвременных Ethernet адаптеров который включен по умолчанию.
- Proposed as answer by Petko Krushev Microsoft contingent staff, Moderator Tuesday, February 25, 2014 7:04 AM
- Marked as answer by Petko Krushev Microsoft contingent staff, Moderator Wednesday, February 26, 2014 12:29 PM
На сервере 2012r2 с ролью hyper-v проверил все варианты лечений которые есть в инете ничего не помогает
отключал Large Send Offload (LSO) а также другие параметры tcp,
поставил в hyper-v чистую винду никакие роли не подымал только включил удаленное администрирование и сразу пошли предупреждения в логах при каждом подключении-
это проблема 2012r2 надо исправлять а не считать пользователей за идиотов.
также есть проблема с новыми интел процессорами спамят лог с ошибкой WHEA-Logger 19
msistat 0x90000040000f000, если в hyper-v запущена 32bit операционка.
5. Согластно спецификации от интел такие ошибки не являются ошибкой и отображать их не нужно. в линуксах уже исправили, куда писать в мс не знаю чтоб сделали патч для WHEA-Logger.