May 14, 2007 at 6:56 am
Hi,
I have an SSIS package which takes data from a SQL 2005 database and outputs an Excel file onto a network drive.
The package runs fine with Visual Studio and produces the expected file.
I can run the package from within SSIS on the local machine and again produces the expected file.
However, when I run as a SQL Job using the SQL Agent Service Account, it states the job has run successfully, yet no output file has been produced?
I've tried using both mapped drive pathnames and UNC pathnames with no joy.
I've also tried running the package on 2 different servers. One server was setup with a local account for the SQL Server Agent Service (not sure why it was setup like this) and another server had a domain account.
Has anyone any ideas what the problem might be?
Logging of the package also only produced a log file when running the package from within SSIS on the local machine, yet no log file was generated when running as a SQL Job.
Thanks for any help
May 15, 2007 at 8:22 am
I've now resolved this matter. It was the local account running the SQL Server Agent service that was the culprit. Once this was changed to a domain account with appropriate privilages and a UNC pathname was being used, all worked as it should.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply