Hi.

We have two SQL Servers.

Currently, we have been successfully transfering flat files to the 1st SQL
Server, loading the DTS Package via VB.Net, changing the location of the
source file and executing the package. This seems to work a treat.

We now need to introduce a second server. As far as I am concerned, I have
matched everything identically. The file is tranfered to the server's D:\
drive (which is a local hard-drive, not a mapped network drive). However,
when I change the path of the flat file and execute the package, I get this
error message:

Microsoft Data Transformation Services Flat File Rowset ProviderDescription:
Error opening datafile: The device is not ready.

What does this mean? Why does it work on our 1st SQL Server and not our 2nd.
I have taken some time to ensure that they are set up in the same way but
there is obviously a problem. Any ideas?

--
welcome to the mooon !

Hello m00nm0nkey,

Device not ready would make me think that the location in which I am looking
or have pointed my package is invalid. You see this if you point to the
Floppy drive and there is no disk in there or a USB drive.

Could this be the issue?

Allan

Ok, explain this:

D:\CDR_Files\transfer\ errors, but if I use
\\cwmc-cdr-2\transfer\, this works!

Bare in mind, CWMC-CDR-2 is the actual SQL Server, so the question is, why
doesn't SQL Server think the D:\ drive exists??

--
welcome to the mooon !


"Allan Mitchell" wrote:

Just to clarify, the D:\ drive is a secondary, local hard drive, not a USB
device or mapped network drive.
--
welcome to the mooon !

Hello m00nm0nkey,

I would make sure the location you think the file is going to is the one
it actually is
I would then go to the server itself and log on to the server itself as the
suer executing the package and try to go to the D:\ drive.
Is it possible perms to the local drive are different to that on the share?

Allan