Errors using UNC paths with SSIS

I have an SSIS package that works if run manually but when put into a job fails with the following message.

"Description: The file name "\\fileprint\ITDepartment\ToExport\PriceChanges\Pricechanges.csv" specified in the connection was not valid."

However I have a drive mapped where G: is equal to \\fileprint\ITDepartment (i.e. G:\ToExport\PriceChanges\Pricechanges.csv) and it works OK.  Is there a trick to using a UNC path with SSIS?

Thanks for the ideas
jdr0606Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
>when put into a job fails with the following message.
If you're deploying it to a server, then any paths need to be valid on that server.

>Is there a trick to using a UNC path with SSIS?
Nope, although it may be a deal where if you start up the server and run a job with that path, it fails, whereas if you click on the path in Windows Explorer and it works, then run the job and the job works.  No idea why that's happening.
0
John_VidmarCommented:
I suspect one of the following:

1.

Put \\fileprint\ITDepartment\ToExport\PriceChanges into Windows-Explorer, are you able to see the file Pricechanges.csv?  I like to use *cough*DOS*cough* to tell me exactly what are my drive mappings by issuing net use.

2.

Which credentials are running your SSIS-package?  If you are using a SQL Server only-user then it cannot see any file-system except the server where it resides.  If you mapped a SQL Server user to an active-directory service-account then that service-account must have access to that folder structure.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jdr0606Author Commented:
I was related to credentials and access to the folder on the network. The error which was thrown by the SSIS package noting that it could not find the file was simply because it didn't have permissions to the folder where the file was located.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.