Hi, I have a number of SSIS packages, that work fine on one environment, but as soon as they more to another, they hang when they reach an execute process task, that is calling a command line .exe Basically, there are no errors in any SQL or Windows log on either machine, and it does not stop running, it just sits there for ever doing nothing. Logging in the package shows it starts to pre-execute the task, then does nothing. I have asked this question on the forums before and not solved it. This has been on-goin for nearly a year, and I just can't get to the bottom of it! Configuration - DB Engine and Server Agent on a Cluster Package and .exe, etc stored on a seperate server Things already tried - Adding SSIS Server to Local Intranet Zone Turning on Allow Unsafe Files Using "God Account" to run job Using "God Account" to Run As on the execute process Making the owner of the .exe the same account as the execution context of the process Disable attachment manager I am sure that this is less a problem with SSIS and more an OS level config setting, as the packages DO WORK in one of our environments, but nobody can seem to work out what is different. Any suggestions greatly appreciated! Thanks, PetePeter Carter-Greenan http://sqlserverdownanddirty.blogspot.com/