That's why I only setup an IPC connection, so that a unc is then valid. It works from the cli, just not the scheduled task. Rather than change the user to the one the scheduled task runs as, I am hoping to use this specific user.
jlc From: Richard Stovall [mailto:[email protected]] Sent: Tuesday, October 13, 2009 9:00 AM To: NT System Admin Issues Subject: RE: SQL Agent Job issue I guess that was possibly a dumb question. If you use UNC paths you'd have to re-authenticate for every command that uses one, huh? From: Richard Stovall [mailto:[email protected]] Sent: Tuesday, October 13, 2009 10:58 AM To: NT System Admin Issues Subject: RE: SQL Agent Job issue Why are you mapping a drive? Do the rest of your batch file commands not support UNC paths? From: Jonathan Link [mailto:[email protected]] Sent: Tuesday, October 13, 2009 8:28 AM To: NT System Admin Issues Subject: Re: SQL Agent Job issue Use domain\user for the username? On Tue, Oct 13, 2009 at 10:14 AM, Joseph L. Casale <[email protected]<mailto:[email protected]>> wrote: I have a job defined with several steps, one is a batch file that maps a drive on a Samba server. To setup the IPC session so the UNC exists, I start the script with: rem Setup IPC$ net use \\Server /USER:user_name password But I get an error in the log: "A specified logon session does not exist. It may already have been terminated." Any ideas, obviously this works at the cli, just not when the job is run as scheduled. Thanks! jlc ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
