Hi All,
I created a SQL Server DTS package when connecting to the SQL server on my
machine. We have a batch file created which was scheduled to run every Tue.
night on the server where SQL server really sits. In the batch file, we use
dtsrun to call this package. It has been running well. I shut my computer
down this Tue. after work. I got an error message from running the package.
Step Error Source: Microsoft JET Database Engine
Step Error Description:'I:\68\data_from_county' is not a valid path. Make
sure that the path name is spelled correctly and that you are connected to
the server on which the file resides.
Step Error code: 80004005
Step Error Help File:
Step Error Help Context ID:5003044
Should the package be run on the server? It should have nothing to do with
my computer, right? I got very confused. Any help will be greatly
appreciated.
CindyDTS is a client side software. When invoked from Enterprise Manager on a
client, the package actually runs on the client PC. When invoked from a job,
it runs on the server side.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Cindy" <cindyhe@.bonestroo.com> wrote in message
news:uIkoZNshEHA.3988@.tk2msftngp13.phx.gbl...
Hi All,
I created a SQL Server DTS package when connecting to the SQL server on my
machine. We have a batch file created which was scheduled to run every Tue.
night on the server where SQL server really sits. In the batch file, we use
dtsrun to call this package. It has been running well. I shut my computer
down this Tue. after work. I got an error message from running the package.
Step Error Source: Microsoft JET Database Engine
Step Error Description:'I:\68\data_from_county' is not a valid path. Make
sure that the path name is spelled correctly and that you are connected to
the server on which the file resides.
Step Error code: 80004005
Step Error Help File:
Step Error Help Context ID:5003044
Should the package be run on the server? It should have nothing to do with
my computer, right? I got very confused. Any help will be greatly
appreciated.
Cindy|||Thanks for the quick response.
We have a batch file which calls to run this package on the server. Should
it run on the server side as you said? If so, it should have nothing with my
computer, right?
Cindy
"Narayana Vyas Kondreddi" <answer_me@.hotmail.com> wrote in message
news:uvn14PshEHA.632@.TK2MSFTNGP12.phx.gbl...
> DTS is a client side software. When invoked from Enterprise Manager on a
> client, the package actually runs on the client PC. When invoked from a
job,
> it runs on the server side.
> --
> HTH,
> Vyas, MVP (SQL Server)
> http://vyaskn.tripod.com/
>
> "Cindy" <cindyhe@.bonestroo.com> wrote in message
> news:uIkoZNshEHA.3988@.tk2msftngp13.phx.gbl...
> Hi All,
> I created a SQL Server DTS package when connecting to the SQL server on my
> machine. We have a batch file created which was scheduled to run every
Tue.
> night on the server where SQL server really sits. In the batch file, we
use
> dtsrun to call this package. It has been running well. I shut my computer
> down this Tue. after work. I got an error message from running the
package.
> Step Error Source: Microsoft JET Database Engine
> Step Error Description:'I:\68\data_from_county' is not a valid path. Make
> sure that the path name is spelled correctly and that you are connected to
> the server on which the file resides.
> Step Error code: 80004005
> Step Error Help File:
> Step Error Help Context ID:5003044
> Should the package be run on the server? It should have nothing to do with
> my computer, right? I got very confused. Any help will be greatly
> appreciated.
> Cindy
>
>
>|||If u call it from a batch file, and the batch file is on your machine, then
the package will run on your machine, not server.
To make sure the package runs on the server, schedule it using an SQL Agent
job.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Cindy" <cindyhe@.bonestroo.com> wrote in message
news:O2O12YshEHA.1276@.TK2MSFTNGP09.phx.gbl...
Thanks for the quick response.
We have a batch file which calls to run this package on the server. Should
it run on the server side as you said? If so, it should have nothing with my
computer, right?
Cindy
"Narayana Vyas Kondreddi" <answer_me@.hotmail.com> wrote in message
news:uvn14PshEHA.632@.TK2MSFTNGP12.phx.gbl...
> DTS is a client side software. When invoked from Enterprise Manager on a
> client, the package actually runs on the client PC. When invoked from a
job,
> it runs on the server side.
> --
> HTH,
> Vyas, MVP (SQL Server)
> http://vyaskn.tripod.com/
>
> "Cindy" <cindyhe@.bonestroo.com> wrote in message
> news:uIkoZNshEHA.3988@.tk2msftngp13.phx.gbl...
> Hi All,
> I created a SQL Server DTS package when connecting to the SQL server on my
> machine. We have a batch file created which was scheduled to run every
Tue.
> night on the server where SQL server really sits. In the batch file, we
use
> dtsrun to call this package. It has been running well. I shut my computer
> down this Tue. after work. I got an error message from running the
package.
> Step Error Source: Microsoft JET Database Engine
> Step Error Description:'I:\68\data_from_county' is not a valid path. Make
> sure that the path name is spelled correctly and that you are connected to
> the server on which the file resides.
> Step Error code: 80004005
> Step Error Help File:
> Step Error Help Context ID:5003044
> Should the package be run on the server? It should have nothing to do with
> my computer, right? I got very confused. Any help will be greatly
> appreciated.
> Cindy
>
>
>|||> To make sure the package runs on the server, schedule it using an SQL
Agent
> job.
Or, a windows scheduled task *on the server* calling a batch file *on the
server*...
The advantage this /could/ have is that the scheduled task could be run as a
different user than the SQL Agent service account...
A|||We have a windows scheduled task on the server calling a batch file on the
server. This is exactly what you mentioned here.
Will who owns this package make any difference or is it an issue that we
should take into account? Should I change the package owner to dbo?
Cindy
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:eGP93gshEHA.4064@.TK2MSFTNGP12.phx.gbl...
> > To make sure the package runs on the server, schedule it using an SQL
> Agent
> > job.
> Or, a windows scheduled task *on the server* calling a batch file *on the
> server*...
> The advantage this /could/ have is that the scheduled task could be run as
a
> different user than the SQL Agent service account...
> A
>
No comments:
Post a Comment