This article was previously published under Q159792
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 17065 (6.5)
If a non-system administrator (SA) login creates and runs a CmdExec task ona domain controller, the following error will occur in both the taskhistory and the Application log of Windows NT's Event Viewer:
A problem occurred while attempting to logon as the Windows NT user 'SQLExecutiveCmdExec': Logon failure: unknown user name or bad password.
To work around this problem, do one of the following:
Rename the machine name of the domain controller to match the domain name. Note that this solution will only work for one SQL Server on a domain.
Reinstall Windows NT Server as a server in the domain, instead of as a domain controller.
Run a Transact-SQL task that runs xp_cmdshell after installing Service Pack 5a for Microsoft SQL Server 6.5.
Microsoft has confirmed this to be a problem in Microsoft SQL Serverversion 6.5. We are researching this problem and will post new informationhere in the Microsoft Knowledge Base as it becomes available.
Microsoft SQL Server version 6.5 is not recommended for installation on aprimary domain controller (PDC) or a backup domain controller (BDC),because these computers perform the resource-intensive tasks of maintainingand replicating the domain's security accounts database and performingnetwork login authentications.
If you enable security auditing for logon or logoff failures, you will seeevent 529, indicating a logon failure, for the SQLExecutiveCmdExec account,as in the following example:
Logon Failure: Reason: Unknown user name or bad password User Name: SQLExecutiveCmdExec Domain: NTServerName Logon Type: 4 Logon Process: Advapi Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0 Workstation Name: NTServerName
Additionally, a similar error occurs when xp_cmdshell is run by non-systemadministrator (SA) logins.