Microsoft KB Archive/942636

= Windows Server 2003-based domain controllers may incorrectly return the &quot;NO_SUCH_USER (0xc0000064)&quot; status code in response to logon requests =

Article ID: 942636

Article Last Modified on 10/8/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Web Edition
 * Microsoft Windows Server 2003, Enterprise Edition
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard x64 Edition
 * Microsoft Windows Server 2003, Enterprise x64 Edition
 * Microsoft Windows Server 2003, Datacenter x64 Edition
 * Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
 * Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems

-



SYMPTOMS
Windows Server 2003-based domain controllers may incorrectly return the &quot;NO_SUCH_USER (0xc0000064)&quot; status code in response to logon requests. This behavior occurs when the authenticating domain controller is shutting down or restarting.

The status code may be returned to one of the following computers:
 * The domain member computer that originated the logon request
 * An application server
 * A domain controller that forwarded the logon request to the authenticating domain controller by using pass-through authentication

The incorrect status code may cause the application that originated the logon request to fail or to time out.



CAUSE
This problem occurs because the Net Logon service incorrectly manages the returned status.



RESOLUTION
To resolve this problem, you must apply a hotfix on the domain controllers and on the domain clients. After you apply this hotfix, the domain controllers will return a &quot;STATUS_INVALID_SERVER_STATE (0xc00000dc)&quot; status code during the shutdown process. Then, the client can contact other domain controllers if the client receives this status code.

Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
To apply this hotfix, you must have Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2) installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100 How to obtain the latest service pack for Windows Server 2003

Restart requirement
You must restart the computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003 with SP2, x64-based versions


WORKAROUND
To work around this problem, manually stop the Net Logon service before you shut down the domain controller.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



How this problem affects applications
When the &quot;NO_SUCH_USER&quot; status code is received, domain member computers and domain controllers do not establish a new security channel with another domain controller that is running correctly. Therefore, the logon requests that are sent by users or by applications may time out. The application that originated the logon requests may time out or may fail unless the application has failover logic or retry logic.

You may have enabled authentication in Microsoft Internet Security and Acceleration (ISA) Server to filter network traffic. Or, you may have enabled authentication in Internet Information Services to authenticate access to a Web site. When a domain controller is shutting down, users may be denied access to the proxy server or to the Web site.

Additionally, this problem prevents Microsoft BizTalk Server from working correctly. The BizTalk services stop unexpectedly every time that a domain controller is restarted. You have to manually restart the BizTalk services.

In this scenario, the following errors are logged in the Application log on the server that hosts BizTalk Server:

Event ID 6913
Event Type: Error

Event Source: BizTalk Server 2006

Event Category: BizTalk Server 2006

Event ID: 6913

User: N/A

Computer: 

Description:

An attempt to connect to  SQL Server database on server  failed with error: &quot;Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.&quot;.

Event ID 5410
Event Type: Error

Event Source: BizTalk Server 2006

Event ID: 5410

User: N/A

Computer: 

Description:

An error occurred that requires the BizTalk service to terminate. The most common causes are the following:

1) An unexpected out of memory error. OR

2) An inability to connect or a loss of connectivity to one of the BizTalk databases. The service will shutdown and auto-restart in 1 minute. If the problematic database remains unavailable, this cycle will repeat.

Error message: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.

Error source: BizTalk

host name: 

Windows service name: 

To work around this scenario, you can use a script in Service Control Manager to start the BizTalk services if the services are stopped.

Debugging information
If you have enabled logging for the Net Logon service, the status code for the logon request is logged in the following file:

%systemroot%\Debug\Netlogon.log

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

109626 Enabling debug logging for the Net Logon service

The 0xC0000064 status code may be logged in the Netlogon.log file on the following computers:
 * The computer that originated the logon request
 * The domain controller that responded to the logon request
 * An application server or domain controller that forwards the request to the authenticating domain controller

Note The &quot;NO_SUCH_USER (0xC0000064)&quot; status code is a valid return code if the user account to be authenticated does not exist. This situation may occur if one of the following conditions is true:
 * The user account has not replicated to the authenticating domain.
 * The user account has been deleted from the Active Directory directory service.
 * The user account in the authentication request is formatted incorrectly by the user or by the application.

When a domain controller responds to a logon request that is received by using pass-through authentication, the Netlogon.log file on the domain controller logs information that resembles the following:

MM/DD HH:MM:SS [LOGON] CORP-DOMAIN: SamLogon: Transitive Network logon of  \ from CALLER (via ) Entered

MM/DD HH:MM:SS [LOGON] CORP-DOMAIN: SamLogon: Transitive Network logon of  \<User account> from CALLER (via <DC or member server>) Returns 0xC0000064

When the authenticating domain controller responds to a logon request that is received directly from a domain member computer in the same domain, the Netlogon.log file on the domain controller logs information that resembles the following:

MM/DD HH:MM:SS [LOGON] Samlogon: Network logon of <Domain name>\<User account> from CALLER Entered

MM/DD HH:MM:SS [CRITICAL] NlPrintRpcDebug: Couldn't get EEInfo for I_NetLogonSamLogonEx: 1761 (may be legitimate for 0xc0000064)

MM/DD HH:MM:SS [LOGON] Samlogon: Network logon of <Domain name>\<User account> from CALLER Returns 0xC0000064

<div class="references_section">