IWODCMD.EXE is not a Win32 Application Error

Hello,

I am getting: "iwodcmd.exe is not a Win32 application." and the file size of iwodcmd.exe is 0 (zero).

Not sure how it happened? Any idea?
Kindly suggest.

Thanks in Advance,
John

Find more posts tagged with

Comments

Ambuj

Hello,

I am getting: "iwodcmd.exe is not a Win32 application." and the file size of iwodcmd.exe is 0 (zero).

Not sure how it happened? Any idea?
Kindly suggest.

Thanks in Advance,
John

Please check whether this file exists or not?
It may be deleted by mistake.

nipper

Hello,

I am getting: "iwodcmd.exe is not a Win32 application." and the file size of iwodcmd.exe is 0 (zero).

Not sure how it happened? Any idea?
Kindly suggest.

Thanks in Advance,
John

load from backup or reinstall OD.

This can happen if someone tries some Unix style redirection incorrectly, i.e. cat file > $odhome/bin/iwodcmd start

Check the timestamp on the file, that will tell you when it happened.

jstephan

Thank you for all your response.

File exist with 0 file size and the time stamp of the file was today (the time when it started to show this error) and other files time stamps are old. It wasn't deleted or moved.

The iwodcmd.exe was called from workflow only. When the deployment failed, i tried to run the deployment command in command line and it failed with this message and the return value is ACCESS DENIED.

I restored the iwodcmd.exe with the backup and its working good now. But any idea of why and how it happened? Please suggest.

GeoffD

Did you ever figure out how this happened? This just happened to our server and I have no idea what modified the file.

nipper

Did you ever figure out how this happened? This just happened to our server and I have no idea what modified the file.

I have seen this happen to iwodcmd as well as iwperl, it has been assumed that there was a Unix style redirection that overwrote the file (see my previous post). I do not know that there has ever been a definitive answer.

Check the timestamp on the file and see if you can determine what was going on when that happened. Check your workflow logs or any logs at that time.