When the job fails, does it just not run or does it attempt to run and then fail? What does the job history tell you. Make sure the job write to the event log and check the event log, as well as the sql server error logs, for any hint as to why it is failing.
I am betting it is a permissions issue on the share/folder you are trying to write to.
Also, is the share that you are performing the file manipulations on the same server as SQL Server or is it a remote share on another server?
The share is on the same server ie D:\
as the error message says it can't file the specified file yet I have put the full path in. and they work because itexecutes it just doesn't work when it gets scheduled
I've had this same problem, namtab. Like JayKusch says it was a permissions problem. When I ran the DTS package from the Designer it was running under the context of my own network user login, but when I scheduled the package it was running under the context of the SQL Server network user login. The SQL Server network user login needs to have correct permissions on all directories and shares the DTS package is trying to access.
Im having a look at my permission at the moment. The only thing is I have set the agent to run under my account so I would imagine it has my security. I have loggen on the Server as myself so when I execute the package it works with my permissions and sqlagent has my Service Startup account yet still fails.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.