We are on a 64 bit VM and have the need to run 32bit powershell executables. Is there a configuration change that Visual Cron allows for the execution path?

Currently we are implementing by using the execute and adding the entire powershell path with the argument being the powershell script.

Thanks,
Jim

It appears that Visual Cron is running 32 bit VisualCron as the VisualCronService.exe does not have a *32 to the right of the name.

VisualCron is running in 64 bit mode on 64 bit machines. When using the Powershell Task we use the 64 bit powershell host. There is no special setting to force the powershell host to run in 32 bit mode.

One thing we have thought about is to offer 32 bit execution mode for Execute Task. This way you could launch powershell in 32 bit mode and pass arguments to it.

---

A possible workaround in the meantime is to use the start-job trick outlined here .