Could not run...

TS 5.5.2 WIN2K

Workflows were working fine then all of a sudden during an external unlock.ipl task the WF does not transition properly. I'm getting this in the logs.

[Thu Jun 12 10:19:32 2003] Could not run

\PROGRA~1\INTERW~1\TeamSite/iw-perl/bin/iwperl

\PROGRA~1\INTERW~1\TeamSite/local/bin/unlock.ipl for task 36610; retrying in 1 minute.

…and it doesn't have to do with unlock.ipl because I transitioned the task manually through the command line. Then after a CGI task of approving metadata in then hangs on another external iwsend_mail.ipl task.
I get this…
[Wed Jun 11 19:16:30 2003] Could not run

\PROGRA~1\INTERW~1\TeamSite\iw-perl\bin\iwperl

\PROGRA~1\INTERW~1\TeamSite\bin\iwsend_mail.ipl -t WUCMS01\ccallison,WUCMS01\jriedberg,WUCMS01\malexis for task 36455; retrying in 1 minute

I tried rebooting the server several times but no soap.
Helpppppppppp...and thank you in advanced.

The Professor-

Find more posts tagged with

Comments

JonathonG

Just a guess....does iwperl still exist in the path

\PROGRA~1\INTERW~1\TeamSite/iw-perl/bin ? What happens if you try to run

\PROGRA~1\INTERW~1\TeamSite/iw-perl/bin/iwperl -v from a command prompt on the server?

Only reason I guess this is because it was two different scripts that failed. The path to perl is the only thing I see in common.

Jonathon
Interwoven Architecture Consultant

ProfessorX

It's always good to check in every log...In the trace I found...
ERROR: CreateProcess failure - 193

This directed me to

Knowledge Base Article: 49784

Synopsis
If the above mentioned error shows up in iwtrace.log and the externaltask is stuck without transitioning to the next task try modifying the workflow template (wft).
Details

In the externaltask for the workflow file(wft, if the command does not have a .exe for the perl executable the above mentioned error might be logged in the iwtrace.log file.

Error 193 means ERROR_BAD_EXE_FORMAT %1 is not a valid Windows-based application

Ex:- If there was

<command v='c:\\iw-home\\iw-perl\\bin\\iwperl c:\\iw-home\\bin\\iwsend_mail.ipl '/>

change it to

<command v='c:\\iw-home\\iw-perl\\bin\\iwperl.exe c:\\iw-home\\bin\\iwsend_mail.ipl '/>

------------------------------

Changing this command line in the WF pushed the external task through.

Now would you like to go for "Double Jeopardy" were the questions get really hard.

What about my 50 plus workflows that have already been instantiated?

Can I change those that are in the store that have <command v='c:\\iw-home\\iw-perl\\bin\\iwperl c:\\iw-home\\bin\\iwsend_mail.ipl '/>
to <command v='c:\\iw-home\\iw-perl\\bin\\iwperl.exe c:\\iw-home\\bin\\iwsend_mail.ipl '/>
or am I S%@T out of luck?

The Professor-

Adam Stoller

I'd agree with JonathanG - it is most likely a case where Windows - in its infinite wisdom has managed to create a different "short-name" for the path to IWHOME and yet a reference to the original short-name remains.

I'd try using: dir /x from the DOS prompt - to verfiy paths / short-names

--fish
(Interwoven Senior Technical Consultant)

Adam Stoller

Interesting - I've never had any problems using "path/iwperl path/script.ipl" - rather than using "path/iwperl.exe path/script.ipl"

What OS are you on? NT or W2K or something else (XP?)

Is there a system PATHEXT environment variable set? Does it have .exe listed within it?

--fish
(Interwoven Senior Technical Consultant)

nipper

Could there be a file called $iw-home\iw-perl\bin\iwperl (with no extension) ?

just a guess

Andy

Errors.doc

ProfessorX

"Bob, Tell us the prizes that you have for Ghoti and Nipper"

Thank you so much both

Doing a dir /x gave me No short name for iwperl.exe but it did give me this...
-------------------------------
06/11/2003 05:31p 0 iwperl
02/24/2000 05:38a 3,072 iwperl.exe

How did an iwperl with no extension and zero length get created.........hmm well im not sure but......

I was testing out this command in the WF at the time....
__INSERT__( iw_get_mail_cmd('iwsend_mail','', "-t WUCMS01\ccallison,WUCMS01\jriedberg,WUCMS01\malexis"));
which burbed because it needed to be
__INSERT__( iw_get_mail_cmd('iwsend_mail','', "-t WUCMS01\\ccallison,WUCMS01\\jriedberg,WUCMS01\\malexis"));
at the time the file was created
I don't know how this could of created an empty iwperl file in I ran the WF process through. Can I point the finger at Teamsite?

Thanks again......WIN2K Server, 5.5.2

The Professor-

Adam Stoller

The 'dir /x' would have been for looking at the directory paths leading up to iwperl:

c:\> dir /x | find "Prog"
c:\> dir /x "Program Files" | find "Int"

06/11/2003 05:31p 0 iwperl
...
Can I point the finger at Teamsite?
If it makes you happy - yes, but my guess is it was something you (or someone else) did or tried to do that ended up causing a redirection into iwperl (...> iwperl) at around 17:31 last night...

--fish
(Interwoven Senior Technical Consultant)

aces

I tried adding .exe at the end but it didn't work. Any other clues?

Adam Stoller

You tried adding .exe at the end for what?
Since you weren't part of the original thread - it would help if you provided a bit more context in your post about what you are attempting to do, how you are attempting to do it, and the environment in which you are attempting to do it.

--fish
(Interwoven Senior Technical Consultant)