SSIS and SQLAgent problems saving file to mapped drive when run as job
-
I have a package saved in msdb which needs to copy a file to a location on another server which is accessed via network mapped drive.
When executing the package through BIDS, or from Integration Services this works fine (this is run under a windows account UserX). When we try to run the packages as a SQLAgent job, it fails.
The jobstep is set to run as a proxy, whose credential points to UserX, so as I understand it, the jobstep should be run under the exact same permissions as it would under UserX, only it doesn't appear to be doing so. The error received is ""Could not find a part of the path "V:\myfilename.xls"
What else can I try?
Thanks for any pointers
-
First you should check if all permissions are set up correctly.
Second I'd dump the mapped drive (does it exist on the server) and use a real UNC path.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP -
As da-zero said you should not use mapped drives, but specify the complete share path instead. The mapped drives setup is associated with the settings of the user account and it will never work under SQL Job Agent because:
1. The SQL Job Agent is running under different user account.
2. Using the same user account with the mapped drive will still not work because the user account is lightweight. This means that not all user account settings are loaded when executing.
---
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/
-
mazzz (11/26/2010)
... and we have lift-off!Many thanks again
No problem. I'm glad it all worked out.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply