I just updated my version of Teststand 2016(32 bit)/Windows 7 to Teststand 2017(64 bit) Windows 10 and the "call executable" step type fails for a python script->

[SetecTestDept]

Everything was working fine, then I switched versions (see subject) and am no longer to run an executable...

Here's the message:

Run-Time Error
    Details: "C:\Users\.....\Android_Tablet_Interface.py" cmd=sequence_PowerUp_Unlock is not a valid Win32 application
Error Code:
    -17100; Incorrect file format.
Location:
    Step 'Call Executable' of sequence 'Main sequence' in 'template.seq'

Something must be up with Windows because I can run it fine on Windows7 with Teststand 2017 (64 bit)

... I've checked the path environment variable.

I'm running 32bit python3. Could that be the source of my application?

[SetecTestDept]

It does work on a Windows 7 + Teststand 2017(64 bit) combination too...

[ybalam]

I'd suspect that this has something to do with the versioning of Windows. Are you able to run your code when you don't call it from Python? 

[SetecTestDept]

Yes!

py Android_Tablet_Interface.py cmd=swipe_Unlock

Android_Tablet_Interface.py cmd=swipe_Unlock

... is the function that I am testing.

Both of these work...

[SetecTestDept · Accepted solution]

So my workaround is that I can call an executable using LabVIEW through the "system exec" vi.

This seems to work now.

From internet research the problem seems to be centered around the way Windows handles 32 and 64 bit applications with a 64 bit processor, different namespaces etc...

Here is a good article: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019L4VSAU