Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

command exec job not working

Status
Not open for further replies.

nuct

Programmer
Sep 5, 2001
103
Hi, I have a command exec job which copies a file from a mapped network drive (which is on a unix machine) and when it runs it says "access is denied" in the job history. However when I log in on the SQL Server machine using the same account used by sql server agent and try the command it works ok.

One thing I noticed is that agent and server are running under different accounts.

I'm sorry for cross posting by the way, i think that I put this question in the wrong place first time.

Any ideas.

Simon
 
It is advisable that you start both services using the same account. And even better if the account is a domain user account with enough rights to read\write remote folders. Now as for the UNIX part I am not sure how that works...You might need something in the middle like Samba that makes your UNIX files available to Windows.

What seems to happen is that the first user, the one logged onto the PC doesn't have enough rights to access that UNIX folder; he seems to be a local system user. If it's not against your security policies I would advise that you give that user the same rights as the account starting SQL Srv Agent. Or start the PC with the Agent's starting account. It's a server, it should not be a problem.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top