 | |
NEWBIE - can't run SSIS package in SQL server agent scheduled job?
microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts
 |
| | Thread Tools | Display Modes |
#11
 
| |||
| |||
|
Re: NEWBIE - can't run SSIS package in SQL server agent scheduled job? -
07-01-2008
, 10:22 AM
|
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 (AT) plumasnt (DOT) com> wrote in message news:eMd%23zQu1IHA.3920 (AT) TK2MSFTNGP02 (DOT) phx.gbl... 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 |
#12
| |||
| |||
|
|
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 (AT) plumasnt (DOT) com> wrote in message news:eMd%23zQu1IHA.3920 (AT) TK2MSFTNGP02 (DOT) phx.gbl... 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 |
#13
| |||
| |||
|
|
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 (AT) plumasnt (DOT) com> wrote in message news:eMd%23zQu1IHA.3920 (AT) TK2MSFTNGP02 (DOT) phx.gbl... 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 |
#14
| |||
| |||
|
|
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 (AT) plumasnt (DOT) com> wrote in message news:eMd%23zQu1IHA.3920 (AT) TK2MSFTNGP02 (DOT) phx.gbl... 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 |
#15
| |||
| |||
|
|
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 (AT) plumasnt (DOT) com> wrote in message news:eMd%23zQu1IHA.3920 (AT) TK2MSFTNGP02 (DOT) phx.gbl... 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 |
#16
| |||
| |||
|
|
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 (AT) plumasnt (DOT) com> wrote in message news:eMd%23zQu1IHA.3920 (AT) TK2MSFTNGP02 (DOT) phx.gbl... 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 |
#17
| |||
| |||
|
|
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 (AT) plumasnt (DOT) com> wrote in message news:eMd%23zQu1IHA.3920 (AT) TK2MSFTNGP02 (DOT) phx.gbl... 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 |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.