|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Get "...is not a valid Win32 application." when trying to run Python script
Hi,
VBP 8.0 x64 Windows 7 ultimate host I'm trying to run a new Python script through a Batch File step and the step is immediately failing with the error "... is not a valid Win32 application." The script pushes files from the localhost up to a remote linux server. When I run the script from the command line, it works as expected. No error, all files go where I expect. I've got several other python scripts used for things like checking file sizes, parsing logs, and moving files that all work fine through VBP without issue. I've tried this script on a couple of different windows hosts all with the same results; script runs fine from command line, but dies immediately in VBP. Any thoughts? |
#2
|
|||
|
|||
Turns out that this issue was caused by attempting to re-use/re-purpose a VBP step.
I previously had a Batch File step that executed a .bat script to push files to a remote server. I later created a .py script to replace the batch script and just updated the VBP step with the new file.py. When I attempted to execute the step with the changed .py script, it failed with the error I noted above. Dragging a new Batch File step into the project and configuring it to execute the .py script allowed it to work as expected. This seems like a bug to me, but the workaround is a viable resolution. |
#3
|
|||
|
|||
There must be some difference between the 2 Batch File steps that would account for the difference in behavior?
|
#4
|
|||
|
|||
The only difference was the type of script being run:
c:\heres\my\path\script.bat became c:\heres\my\path\script.py. Everything else was the same. No user params, everything is local. |
#5
|
|||
|
|||
I guess that difference matters? If you can post a .bld file demonstrating the two steps, that might help. Thanks.
|
#6
|
|||
|
|||
Right, which is why I feel it's a bug. I should not have to recreate a step from scratch just to change the file it's pointing to. The current behavior is confusing, to say the least.
|
#7
|
|||
|
|||
All of the step properties can be modified, so I don't follow why would you need to create the step from scratch to change the file it's pointing to. Again, if you can post a .bld file with both steps, it might help.
|
|
|