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/

Have you tried running the packages interactively on the server using BIDS or DTEXECUI? Perhaps the exe is prompting due to some environmental difference. Dan Guzman, SQL Server MVP, http://weblogs.sqlteam.com/dang/

Hi Dan, Yes, they run interactivly, or from Windows scheduled tasks, with the same security context, etc. The only time they don't work is through this specific scenario. Run from server agent, against the package store on a seperate server. In any other scenario, there is no issue.Peter Carter-Greenan http://sqlserverdownanddirty.blogspot.com/

Try to run the commandline .exe on the server which hang. I remember the same problem a few weeks ago and the reason was a security setting on the server, which differed from the other server.

Hi Christa, What do you want me to run in the command line? I don't suppose you remember the setting? I am positive it is a Windows setting, I just need to know which one!! :)Peter Carter-Greenan http://sqlserverdownanddirty.blogspot.com/

I startet a big search for the fixing ;-) and found this: we use a bat to call the exe and the admin added thies line before calling the exe: SET SEE_MASK_NOZONECHECKS=1

Cool, thanks Christa, I'll give this a try and post back.Peter Carter-Greenan http://sqlserverdownanddirty.blogspot.com/

Christa, Finally craked it! Thanks so much for your help! PetePeter Carter http://sqlserverdownanddirty.blogspot.com/

I have the execute process task that calls an executable which programatically builds and runs a .dtsx. This executable is a C# console app that does will run in back ground. I used batch file to run the program and the program seems to run finally now. However, now the issue is that the execute process task returns success (turns green) as soon as the .exe is initiated and a new iteration (for each loop) starts. Ideally I would want the task to not return success until the .exe is completely run and closed. Any suggestions? Thanks.