DTS Problem

Hi Folks,
I have a two node cluster and I have a DTS package, which transfers data from a text file to the database. The problem is like it runs fine when the cluster is in its base node(Node1) but when ever the cluster fails overs (to node2) the dts job fails saying that the path not found.

1. The drive is a dependent resource to sql server.

2. When I try to run the DTS package itself (from node2) its running fine.

any insights guys?

with smiles
santhoshHow is the file referenced in the DTS package (ie, is it UNC)?

Is there possibly a permissions issue (Log in to Node two as the SQL Service account and attempt to run the DTS package)?

I have a similar set up with a two-node cluster and a DTS package that references a cluster disk. No issues that I am aware of.

Please provide a bit more detail.

Regards,

hmscott

DTS packages in SQL 2005

I see them show up under a node called Legacy in Management Studio. What is
the plan for migration of DTS packages from 2000 to 2005? We have lots of
these that we'll need to migrate that are in use with various SQL jobs.
Thanks,
Johnthere is a migration wizard to help you.
but you'll have a lot of manual job to do to really convert DTS to SSIS. (to
make sure that the upgrade is correct and to use the new features)
but you can continue to execute your DTS packages in 2005.
"John Holmes" <johnsh@.co.skagit.wa.us> wrote in message
news:efrhJH5IGHA.140@.TK2MSFTNGP12.phx.gbl...
>I see them show up under a node called Legacy in Management Studio. What is
>the plan for migration of DTS packages from 2000 to 2005? We have lots of
>these that we'll need to migrate that are in use with various SQL jobs.
> Thanks,
> John
>|||Have you found any documentation about what kind of code or task need manual
job to be migrated? Or should I learn it on the field, one by one'
"Jéjé" wrote:

> there is a migration wizard to help you.
> but you'll have a lot of manual job to do to really convert DTS to SSIS. (
to
> make sure that the upgrade is correct and to use the new features)
> but you can continue to execute your DTS packages in 2005.
> "John Holmes" <johnsh@.co.skagit.wa.us> wrote in message
> news:efrhJH5IGHA.140@.TK2MSFTNGP12.phx.gbl...
>
>

DTS packages in SQL 2005

I see them show up under a node called Legacy in Management Studio. What is
the plan for migration of DTS packages from 2000 to 2005? We have lots of
these that we'll need to migrate that are in use with various SQL jobs.
Thanks,
John
there is a migration wizard to help you.
but you'll have a lot of manual job to do to really convert DTS to SSIS. (to
make sure that the upgrade is correct and to use the new features)
but you can continue to execute your DTS packages in 2005.
"John Holmes" <johnsh@.co.skagit.wa.us> wrote in message
news:efrhJH5IGHA.140@.TK2MSFTNGP12.phx.gbl...
>I see them show up under a node called Legacy in Management Studio. What is
>the plan for migration of DTS packages from 2000 to 2005? We have lots of
>these that we'll need to migrate that are in use with various SQL jobs.
> Thanks,
> John
>
|||Have you found any documentation about what kind of code or task need manual
job to be migrated? Or should I learn it on the field, one by one?
"Jéjé" wrote:

> there is a migration wizard to help you.
> but you'll have a lot of manual job to do to really convert DTS to SSIS. (to
> make sure that the upgrade is correct and to use the new features)
> but you can continue to execute your DTS packages in 2005.
> "John Holmes" <johnsh@.co.skagit.wa.us> wrote in message
> news:efrhJH5IGHA.140@.TK2MSFTNGP12.phx.gbl...
>
>

DTS packages in SQL 2005

I see them show up under a node called Legacy in Management Studio. What is
the plan for migration of DTS packages from 2000 to 2005? We have lots of
these that we'll need to migrate that are in use with various SQL jobs.
Thanks,
Johnthere is a migration wizard to help you.
but you'll have a lot of manual job to do to really convert DTS to SSIS. (to
make sure that the upgrade is correct and to use the new features)
but you can continue to execute your DTS packages in 2005.
"John Holmes" <johnsh@.co.skagit.wa.us> wrote in message
news:efrhJH5IGHA.140@.TK2MSFTNGP12.phx.gbl...
>I see them show up under a node called Legacy in Management Studio. What is
>the plan for migration of DTS packages from 2000 to 2005? We have lots of
>these that we'll need to migrate that are in use with various SQL jobs.
> Thanks,
> John
>|||Have you found any documentation about what kind of code or task need manual
job to be migrated? Or should I learn it on the field, one by one'
"Jéjé" wrote:
> there is a migration wizard to help you.
> but you'll have a lot of manual job to do to really convert DTS to SSIS. (to
> make sure that the upgrade is correct and to use the new features)
> but you can continue to execute your DTS packages in 2005.
> "John Holmes" <johnsh@.co.skagit.wa.us> wrote in message
> news:efrhJH5IGHA.140@.TK2MSFTNGP12.phx.gbl...
> >I see them show up under a node called Legacy in Management Studio. What is
> >the plan for migration of DTS packages from 2000 to 2005? We have lots of
> >these that we'll need to migrate that are in use with various SQL jobs.
> >
> > Thanks,
> >
> > John
> >
>
>