• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3261
  • Last Modified:

procedure=xp_cmdshell text=An error occurred during the execution of xp_cmdshell

we are occasionally getting

Server message number=15121 severity=16 state=200 line=1 server=MARILYN procedure=xp_cmdshell text=An error occurred during the execution of xp_cmdshell. A call to 'LogonUserW' failed with error code: '1909'.

and this seems to fix it, albeit temporarily!?

Exec sp_xp_cmdshell_proxy_account NULL
Exec sp_xp_cmdshell_proxy_account 'domain\account', 'therightpassword'

any ideas why this may be happening?
this is fully patched w2k3 server R2 SP2 x64; sql2005 SP3 - Microsoft SQL Server 2005 9.00.4053.00 (X64)
0
gddl630
Asked:
gddl630
  • 3
  • 2
1 Solution
 
gothamiteCommented:
Could it be the account is getting locked out due to some policy about maximum concurrent (NT) sessions or something? Can you have a look in the Windows Event Log (Security) for any errors associated with the account?
0
 
gddl630Author Commented:
not sure I've never had to do anything to limit maximum concurrent (NT) sessions - how do I check that?
as for the event log I can see entries like this one although no specific account is being mentioned
Event Type:	Failure Audit
Event Source:	Security
Event Category:	Logon/Logoff 
Event ID:	529
Date:		10/04/2010
Time:		05:39:23
User:		NT AUTHORITY\SYSTEM
Computer:	MARILYN
Description:
Logon Failure:
 	Reason:		Unknown user name or bad password
 	User Name:	
 	Domain:		
 	Logon Type:	3
 	Logon Process:	Kerberos
 	Authentication Package:	Kerberos
 	Workstation Name:	-
 	Caller User Name:	-
 	Caller Domain:	-
 	Caller Logon ID:	-
 	Caller Process ID:	-
 	Transited Services:	-
 	Source Network Address:	-
 	Source Port:	-


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Open in new window

0
 
gothamiteCommented:
You could look at the Resultant-Set-of-Policy for the user to see if there's anything weird going on with policies. Here's a Microsoft KB on how to do this:

http://support.microsoft.com/kb/323276
0
 
gddl630Author Commented:
thanks

I couldn't see anything unusual, but to point out again executing this fixes it:
Exec sp_xp_cmdshell_proxy_account NULL
Exec sp_xp_cmdshell_proxy_account 'domain\account', 'therightpassword'
0
 
gddl630Author Commented:
used ALTools.exe to discover the server and process locking the account. it turned out the account was used on another machine and the password was mistyped
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now