Article ID: 159792 - View products that this article applies to.
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 on a domain controller, the following error will occur in both the task history 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:
Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
Microsoft SQL Server version 6.5 is not recommended for installation on a primary domain controller (PDC) or a backup domain controller (BDC), because these computers perform the resource-intensive tasks of maintaining and replicating the domain's security accounts database and performing network login authentications.
If you enable security auditing for logon or logoff failures, you will see event 529, indicating a logon failure, for the SQLExecutiveCmdExec account, as in the following example:
Reason: Unknown user name or bad password
User Name: SQLExecutiveCmdExec
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-system administrator (SA) logins.
Article ID: 159792 - Last Review: October 4, 2013 - Revision: 4.0
Contact us for more help
Connect with Answer Desk for expert help.