![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I'm migrated a set of DTS packages from a Windows 2000 server running SQL server 2000 onto a Windows 2003 server running SQL server. I have a DTS package that exports to a text file whose target is a mapped network driver. The W2K server works fine both running the DTS packages and when it is scheduled. Teh W2003 sever will run the DTS package but fails when scheduled with an error "The system cannot find the path specified." If think this is a network security problem. I've used NBTSAT -A to determine the network account that the servers are using so I can confirm secuirity access to the mapped drive. The 2003 server does not appear to report back the network account. Both servers have been set up the same and are using the same accounts within SQL. Has any one got any ideas. Thanks |
#3
| |||
| |||
|
|
Have you found a solution to this problem? I am experincing the same symptoms, but am trying to read in a file rather than write one out. Same set of conditions too. Any info would be appreciated. "paul" <paul.garrad (AT) bt (DOT) com> wrote I'm migrated a set of DTS packages from a Windows 2000 server running SQL server 2000 onto a Windows 2003 server running SQL server. I have a DTS package that exports to a text file whose target is a mapped network driver. The W2K server works fine both running the DTS packages and when it is scheduled. Teh W2003 sever will run the DTS package but fails when scheduled with an error "The system cannot find the path specified." If think this is a network security problem. I've used NBTSAT -A to determine the network account that the servers are using so I can confirm secuirity access to the mapped drive. The 2003 server does not appear to report back the network account. Both servers have been set up the same and are using the same accounts within SQL. Has any one got any ideas. Thanks |
![]() |
| Thread Tools | |
| Display Modes | |
| |