Problem with SSIS and UNC path
-
Hi,
I have an execute process task which runs a .bat file but it doesn't work : the task hangs indefinitely, no instructions in the .bat file are done and no errors are provided..
This .bat file is on a network.
The package is launched from a SQL Agent job with a SSIS proxy which have all rights on the network directory.
I tried to run this package manually from BIDS on the server with the user used by the proxy and it works fine.
I also tried to run the package from the SQL job but with the .bat file on the local disk (C:\) and it works fine too.
The problem seems to come from UNC path but i don't know how to fix that... (i need to use UNC path and not a map network drive).
I tried to change Internet Explorer settings as it is mentioned here : http://social.msdn.microsoft.com/Forums/en/sqlintegrationservices/thread/b9d0f411-4f45-47db-941c-22d57e7dc783
but it doesn't work for me..
Do you have any ideas ? (I use a SQL Server 2005 SP2)
Thank you
-
I think your problem may be that you are trying to run a batch file on a remote computer - and that just doesn't work, as the batch file always tries to execute in the context of wherever it is called from.
If this is the case, check out PSExec from Sysinternals.
-
Hello,
Thank you for your reply.
I don't think so. I know it can works because I did it successfully on my production server in the past.
I'm trying to do it on a new test server which have exactly the same configuration than the production server : same SSIS packages, same SQL Server version, same windows Server version.
I think the problem is related to an odd security issue but i don't know which one.
Rights seems to be ok : I can reach the target .bat and execute it manually without problem if I logon with the user used by the sql proxy.
Unfortunately, it still doesn't work from a SSIS package launched by an SQL agent job with this user.
Regards,
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply