Re: NEWBIE - can't run SSIS package in SQL server agent scheduled job?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Further update.
The package will run if I log into the server under the given account and right click on the job and chose "run".
But it won't run at the scheduled time, by itself.

Any ideas?

Dennis

"Irvine, Dennis" <dennis.irvine@xxxxxxxxxxxx> wrote in message news:%23QanAVx1IHA.5832@xxxxxxxxxxxxxxxxxxxxxxx
Further update.

It is almost definitely a network drive mapping issue.
I added a "step" to the job that ran an operating system command to map the necessary drive prior to running the main package and it worked.

Don't know why I need to map the drive, as it is normally mapped for that computer under that account.
But at least it worked.

Dennis

"Irvine, Dennis" <dennis.irvine@xxxxxxxxxxxx> wrote in message news:eMd%23zQu1IHA.3920@xxxxxxxxxxxxxxxxxxxxxxx
I have a SSIS package that runs fine in Visual Studio. But if I put it in a scheduled job in SQL Server agent, it won't run.

Both VS and SA use the same account to run.

The error I get in the logs is an ODBC error.
The package does have an ODBC connection in it.
The connection uses a SYSTEM DSN connection to get data from another source on another machine.
I am simply using Windows authentication and VS is running under account "x".
the SQL Server Agent service is also set up to run under account "x".

Yet the error message says the driver cannot be loaded.

Is there perhaps and environment variable problem???
I believe the actual ODBC driver for this is on a network drive. Perhaps the network drive is not "mapped" within the SQL Server Agent service????

Anyone have any suggestions?
Thanks




.

Relevant Pages

  • Re: Error running DTS package on a schedule (only!)
    ... Also, if you are using ODBC, create System DSN, and delete User DSN. ... > | When I try to schedule a job for this DTS package under SQL Server Agent ... > security connection is made using the account you used to start SQL Agent ...
    (microsoft.public.sqlserver.dts)
  • RE: SSIS Problem
    ... If SQL Agent is running under Local Account ... When I execute the package in the Execute Package ... when I run this package under the SQL Server agent (the step ...
    (microsoft.public.sqlserver.tools)
  • Re: Error running DTS package on a schedule (only!)
    ... |I created a DTS package & CAN run it from Enterprise Manager ... | When I try to schedule a job for this DTS package under SQL Server Agent ... the credentials of the currently logged-in Windows NT account ...
    (microsoft.public.sqlserver.dts)
  • RE: Date Format not working
    ... Compare the OS date format for the user who runs the package from ... Enterprise Manager and the NT account that SQL Server Agent runs under. ...
    (microsoft.public.sqlserver.dts)
  • Re: Browsing for Publication error message
    ... what is going on with the description you gave previously but I would guess that the subscriber SQL Server Agent service account was somehow added to the publication access list of the publication on the DMZ. ... select from the MSpublication_access table in the distribution database and see if the account for your Subscriber's SQL Server Agent service account shows up. ...
    (microsoft.public.sqlserver.replication)