Bulk Insert gives "file does not exist", but it does!

Question

Post reply

Bulk Insert gives "file does not exist", but it does!

henkvisser

Mr or Mrs. 500

Points: 535
More actions
April 10, 2009 at 4:49 am

#130005

I'm running a Bulk Insert script from an AppServer to insert into a DBServer. The filepath for the files is UNC, and it works on both servers if copied in explorer. The AppServer holds the SSIS packages and the files to import, the DBServer holds just the database.
When I use to setup above I get an error "file does not exist"
When I refer to a database on the AppServer itself instead of the DBServer, everything runs fine!
I think I checked all permissions, everything seems to look like it should. Strange thing is that the files that have to be imported are on the same server as the SSIS packages, so right/permissions shouldn't be a problem?
help appreciated!

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Johan Bijnens SSC Guru Points: 135604 More actions · Answer 1

Has the account that launches the ssis package been granted read authority on your UNC path / file ?

(service account of sqlagent or proxy account of the sql jobstep that launches dtexec)

Johan

Learn to play, play to learn !

Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:

- How to post Performance Problems
- How to post data and code to get the best help

- How to prevent a sore throat after hours of presenting ppt

press F1 for solution, press shift+F1 for urgent solution 😀

Who am I ? Sometimes this is me but most of the time this is me

henkvisser Mr or Mrs. 500 Points: 535 More actions · Answer 2

ALZDBA (4/10/2009)
Has the account that launches the ssis package been granted read authority on your UNC path / file ?
(service account of sqlagent or proxy account of the sql jobstep that launches dtexec)

Yes, It has all the necessary authorisations. Also, it's on the same server as the SSIS packages.

Johan Bijnens SSC Guru Points: 135604 More actions · Answer 3

you may want to try it out by logging on to your server that launches the ssis package and using that service account (or proxy).

Then try to use the unc path in explorer and see if it works.