SSIS Package behaves differently under different user names
Hi there,
I have a basic SSIS package that loops through a file of a specific search term on one server and for each file matching the requirements moves it to another server location on a network path.
Now when I run the package on the production server as a stand alone DSTX package (via a bat file) it works fine. However, when my colleague tries to run the same package in the same way using the admin account on the server it does not move the file but the package reports no errors.
I really have no idea apart from guessing it has something to do with the user but even then I don't know how to begin to approach it.
Thanks,
OS
-ps diagram below
I have a basic SSIS package that loops through a file of a specific search term on one server and for each file matching the requirements moves it to another server location on a network path.
Now when I run the package on the production server as a stand alone DSTX package (via a bat file) it works fine. However, when my colleague tries to run the same package in the same way using the admin account on the server it does not move the file but the package reports no errors.
I really have no idea apart from guessing it has something to do with the user but even then I don't know how to begin to approach it.
Thanks,
OS
-ps diagram below
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes it was somewhat of a permissions issue with my colleagues account. He didn't have access to the server which the package was trying to access to get the files.
I sorted it out with my network admin and now it's fine.
Thanks