How this problem affects applications
When the "NO_SUCH_USER" status code is received, domain member computers and domain controllers do not establish a new security channel to 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: <Computer name>
Description:
An attempt to connect to <SQL server name> SQL Server database on server <Server name> failed with error: "Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.".
Event Type: Error
Event Source: BizTalk Server 2006
Event ID: 5410
User: N/A
Computer: <Computer name>
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: <Server name>
Windows service name: <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
The 0xC0000064 error 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 "NO_SUCH_USER (0xC0000064)" 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 was 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 <Domain name> \<User account> from CALLER (via <DC or member server>) Entered
MM/DD HH:MM:SS [LOGON] CORP-DOMAIN: SamLogon: Transitive Network logon of <Domain name> \<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
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
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684
Description of the standard terminology that is used to describe Microsoft software updates