LKBEN10674: Howto prevent the id 1054 and 1000 in the eventlog. Could not execute script... and domain controller could not be located...


This article has not been checked!

LKB | Created: 02/04/2020 | Version: 0 | Language: EN | Rating: 0 | Outdated: False | Marked for deletion: False

Author: Wim Peeters - Keskon GmbH & Co. KG


Symptom

You can change the GpNetworkStartTimeoutPolicyValue registry value to prevent such errors

Cause

The startup time of some network drivers can cause these errors

Solution

Please note that changing this DWORD value will not always help. You need to change the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

GpNetworkStartTimeoutPolicyValue DWORD 60

The value 60 is a good start, you can set it higher if your problem persists. I do not recommend to set it higher as 120, in this case

you should look for another solution.

With a command line:

reg add "\\HH00-05-PC003\hklm\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v GpNetworkStartTimeoutPolicyValue /t REG_DWORD

/d 60

For more information you can search in the Microsoft Knowledgebase.

About the Author

Wim Peeters is electronics engineer with an additional master in IT and over 30 years of experience including time spent in support, development, consulting, training and database administration. Wim has worked with SQL Server since version 6.5. He has developed in C/C++, Java and C# on Windows and Linux in different European countries and different European languages. He writes knowledge base articles to solve IT problems and publishes them on the Lubby Knowledge Platform where he is one of the most important contributors and the main developer.

Disclaimer:

The information provided in this document is intended for your information only. Lubby makes no claims to the validity of this information. Use of this information is at own risk!