?
Solved

Calling xp_cmdshell from st.proc. in QA - Error 'Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'

Posted on 2004-09-21
7
Medium Priority
?
809 Views
Last Modified: 2008-01-09
I get an error running xp_cmdshell from a stored procedure in Query Analyzer:
'Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
 
I have tried  running the sproc from Query Analyzer:
exec master..xp_cmdshell 'dtsrun /S<server1> /Ncopy_control /E'  (the way we usually do it)
and
exec master..xp_cmdshell 'dtsrun /S<server1> /Ncopy_control /Usa /Ppassword'  (which looks like it should work)

sa IS in the sysadmin role.  copy_control is a DTS package on <server1> that copies records to <server2>.
Could the error be due to fact I'm accessing 2 servers w/the same login?  sa has same password on both servers.

This T-SQL script actually gets executed in a DTS package, but I want to run it from Query Analyzer.
What am I missing???
0
Comment
Question by:kerickson0328
4 Comments
 
LVL 10

Accepted Solution

by:
AustinSeven earned 500 total points
ID: 12113630
Try changing the account to a suitable Windows account instead of a SQL Login.  

AustinSeven
0
 
LVL 9

Assisted Solution

by:miron
miron earned 500 total points
ID: 12113868
hmmm... you probably can ask how this proc was run in the past...

-- cheers
0
 
LVL 43

Assisted Solution

by:Eugene Z
Eugene Z earned 500 total points
ID: 12114535
did you login on QA as 'sa'?
0
 
LVL 3

Assisted Solution

by:mAjKoL
mAjKoL earned 500 total points
ID: 12118285
It looks like your server has NT AUTHORITY\ANONYMOUS LOGON identity. You can add NT AUTHORITY\ANONYMOUS LOGON to your server logins and assign as low permisions as possible to get this done.

HTH
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

An alternative to the "For XML" way of pivoting and concatenating result sets into strings, and an easy introduction to "common table expressions" (CTEs). Being someone who is always looking for alternatives to "work your data", I came across this …
This month, Experts Exchange sat down with resident SQL expert, Jim Horn, for an in-depth look into the makings of a successful career in SQL.
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
Stellar Phoenix SQL Database Repair software easily fixes the suspect mode issue of SQL Server database. It is a simple process to bring the database from suspect mode to normal mode. Check out the video and fix the SQL database suspect mode problem.

599 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question