# PSEXEC Multiple Instances - Only One Instance Succeeds - (Complete Information Provided) **URL:** https://www.finalbuilder.com/forums/t/psexec-multiple-instances-only-one-instance-succeeds-complete-information-provided/2112 **Category:** Discussion **Created:** [April 8, 2013, 7:52am UTC](https://www.finalbuilder.com/forums/t/psexec-multiple-instances-only-one-instance-succeeds-complete-information-provided/2112 "2013-04-08T07:52:14Z") **Posts on this page:** 2 **Page:** 1
### Author: ![babu\_2082](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/b/d07c76/32.png) [@babu\_2082](https://www.finalbuilder.com/forums/u/babu_2082) #### Post date: [April 8, 2013, 7:52am UTC](https://www.finalbuilder.com/forums/t/psexec-multiple-instances-only-one-instance-succeeds-complete-information-provided/2112/1 "2013-04-08T07:52:14Z")
**Environment Detials** Final Builder Version - 7.0.0.2056 PSTOOLS Version - 1.98 Windows Server 2008 R2 - Service Pack 1 64 Bit Operating System. **My Problem** I have configured 5 final builder projects, which will execute the batch file in 5 different remote machines. I have used the PSEXEC for this. If I run one project at a times, it succeeds. No issues on it. But If I run the 5 final builder projects at the same time, only one project succeeds, while the other projects returns the error code 1 (I mean through creating multiple instances of PSTOOLS at the same time) Can you guide me to solve the above issue ? If that is the limitation in PSTOOLS, let me know the alternative way to achieve this.           ---
### Author: ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent) #### Post date: [April 8, 2013, 8:20am UTC](https://www.finalbuilder.com/forums/t/psexec-multiple-instances-only-one-instance-succeeds-complete-information-provided/2112/2 "2013-04-08T08:20:25Z")
I can reproduce this here, it appears to be a limitation of PSExec, it’s creating a temporary file with the same name each time. In my testing, if I set the Async group action’s thread start delay to 1 second, that allowed all instances of psexec to work. Please not that starting multiple threads about the same issue will not get the issue resolved any quicker.