May 6, 2002 at 7:41 am
I've created a DTS that copies all the object from one server.database to another server.database.
When I create the DTS and use "Windows Authentication" to log onto both databases and run it, everything works great.
The problem occurs when I schedule the DTS. I get the following error
Error string: [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
Why does it allow me to run the DTS manually, but not through a job. I don't want to have to create a user on each end to do the connections
Is there any way to allow Anonymous logon for scheduling a job?
Thanks
May 6, 2002 at 7:54 am
check the login used by the job that executes the dts package.
best regards,
Klaas-Jan Ruyter
May 6, 2002 at 8:47 am
Would that be the owner in the job properties?
If so I've tried several different users, all from sa, domain/username, domain/administrator. All return the same error.
May 6, 2002 at 8:24 pm
Are you touching another machine. As when the DTS package is run as a job it runs in the context of the accout for SQL Server Agent which unless you changed is usually system account. If the packages tries to touch a remote server in the domain then you will need to run Agent in a domain account so it can access remote servers. If these servers are not on the same domain then you will need to most likely try FTP or some other connection where SQL will not need to log on.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
May 6, 2002 at 10:22 pm
Typically we see this error when a double hop has occurred in an NT 4 domain but usually with respect to distributed queries, but I would think this should occur when you try to execute the job manually as well. I don't know if we'd see this in the case of crossing domains with no trust relationship established, I would think an access denied error would come back, but Antares might be right.
With respect to the double hop, take a look at the following Knowledge Base article to see if it applies:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q238477
BTW, the problem with double-hop using Windows NT authentication isn't actually a SQL Server issue. It's behavior by design in the NT authentication model used by NT 4.0 domains (NTLM). Kereberos supports delegation of credentials. However, since SQL Server 7 was built to run under NT 4, it may still have the issue in an AD implementation with Kereberos. SQL Server 2000 will exhibit a similar error under an NT 4 domain, which is why I say it's not a SQL Server issue.
If that's not it, post back and we'll continue to try and help you troubleshoot.
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply