nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ERROR: CreateProcess failure - 206

Reji Varghese

Hello there,

Since one month, i been noticing that iwtrace.log has countless number of the following entry :

ERROR: CreateProcess failure - 206

In KB 58181, its mentioned that some of the files which are invoked by an External Task has a long file name or extension not supported by the OS.

Is there a way to identify which External Task or which file is causing this error ?

Thanks in Advance.

Find more posts tagged with

Comments

nipper

If this is part of a workflow, then you may have hung jobs.

Go to TS and view all jobs, how many do you see ?

If it is the problem you mentioned, go to iwhome/iw-perl/bin/ and look for 2 files called iwperl, one is iwperl. and the other iwperl.exe

That is for DOS only. You can remove the iwperl.

Andy

Reji Varghese

If this is part of a workflow, then you may have hung jobs.

Go to TS and view all jobs, how many do you see ?

If it is the problem you mentioned, go to iwhome/iw-perl/bin/ and look for 2 files called iwperl, one is iwperl. and the other iwperl.exe

That is for DOS only. You can remove the iwperl.

Andy

Thanks Andy for the reply.

The workflow lists thousands of jobs but couldnt identify any job that is hung coz of this.

Also, there is no such file called "iwperl" inside iw-home/iw-perl/bin folder.

Adam Stoller

The workflow lists thousands of jobs but couldnt identify any job that is hung coz of this.

If there are thousands of jobs, chances are many of them are hung.

Take a few of the oldest ones and run them through with iwgetwfobj to see what task they're sitting at. If they seem to be waiting for an externaltask to finish - that's probably [one of] the culprit.

Also verify that you have sufficient memory on your server (although I believe that usually gives an error about not being able to "spawn" a process rather than "create" - but that might have changed over the years or be OS-version specific)

nipper

Thanks Andy for the reply.

The workflow lists thousands of jobs but couldnt identify any job that is hung coz of this.

Also, there is no such file called "iwperl" inside iw-home/iw-perl/bin folder.

OK, on your first point, there are likely hung jobs.

Start viewing them, see what the active task is, note any external tasks and what step they are running.

Point 2 was a shot at a common problem. It still could be a number of other issues, do you use non-OS users (who do you authenticate users) ?

Reji Varghese

If there are thousands of jobs, chances are many of them are hung.

Take a few of the oldest ones and run them through with iwgetwfobj to see what task they're sitting at. If they seem to be waiting for an externaltask to finish - that's probably [one of] the culprit.

Also verify that you have sufficient memory on your server (although I believe that usually gives an error about not being able to "spawn" a process rather than "create" - but that might have changed over the years or be OS-version specific)

there are around 1500 jobs and i randomly picked some of the jobs to get some info of it using iwgetwfobj, but it just doenst return anything.

Dont know what happened now, from today morning, this error no longer appears in the log files. Strange !!!

Thanks ghoti and nipper for your time Smiley Happy