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 on Submit Workflow

seeDerekNow

I attempted to submit a file using the WebDesk Pro interface. After selecting the file and clicking on the 'submit' button, i get an internal server error.

Upon looking at the error_log, I found the following entry:

Premature end of script headers: /iwhome/install001/iw-home/httpd/iw-bin/iwwft_instantiator.cgi

I figured this had to do with directory perms on teh iw-bin directory. However, this directory and everything within it is owned by root. Has anyone seen this before?

Find more posts tagged with

Comments

Migrateduser

Is this repeatable? Or was it a one time freak of nature thing?

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

nipper

What OS and TS version do you have ?

On Solaris & TS 552 this is 32470 bytes (iwwft_instantiator.cgi)

Andy

seeDerekNow

It's been happening pretty consistently.

We're on TS 5.5.2 SP3 on AIX

Here are the current perms for iwwft_instantiator.cgi

-r-xr-xr-x 1 root sys 33724 Sep 08 2002 iwwft_instantiator.cgi

Thanks!

mgal

Do you use custom workflow or out of box workflow for submit?

If custom workflow can you post the workflow here?

Do you get this error when you execute a workflow when you use new job?

Thxs,

Mohammed Gazal.

seeDerekNow

We're just using the default author_submit workflow that is configured with the 'Submit' Button on the Webdesk Pro interface. It's just standard out of the box stuff.

mgal

Are you able to reproduce this error when you login as a editor, admin or master and submit the file?

I would also suggest you to open a supprot case.

THxs,

Mohammed Gazal.

Adam Stoller

Are you able to reproduce this error when you login as a editor, admin or master and submit the file?

Probably not applicable if the problem is happening with the default_author_submit.wft ...

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

mgal

Yes thats what we want to make sure. If the issue is with the wft file or the back end iwwft_instantiator.cgi or any other related files used to kick off workflow.
Thxs,

Mohammed Gazal.

seeDerekNow

It happens when I try submitting something as an editor or author. Seems to work fine submitting as a Master.

I checked the author_submit.wft file and it's the same one that came out of the box. I'm not sure what's going on here. I've opened a case, but am still waiting to hear back...

Just wondering if this has happened to anyone else.

coschtl

Did you erver get a solution on this?

We have exactly the same problem with TS 6.5SP2, Patch 1649 on Windows 2003SP1...

Adam Stoller

Did you erver get a solution on this?

We have exactly the same problem with TS 6.5SP2, Patch 1649 on Windows 2003SP1...

Who owns the workearea in which you are trying to perform the submit?
Is that user an Author-only user, or does that user have the ability to log in with the role Editor or above?

If the user who owns the workarea is only able to log in as an Author - that's the source of the problem - Author's are not allowed to submit files to the staging area - and the owner of the submittask (in the OOTB workflows) is the owner of the area in which the submit is taking place. Which points out a problem that's been in TS for ages - that there is nothing in the system that prevents Author-only users being made owners of workareas, even though by "definition" they should never be allowed to be.

Assuming the above is on-track with your problem (otherwise this is all a waste of verbiage) there are three solutions that come to mind:

coschtl

The system I am talking about is a migrated store from TS6.1 which was running on Win2000SP4. The User has role "Editor" and in th past there hasn't been a problem with this user. The problem is also not specific to a workarea or user.

Personally I think the problem is related to Windows-SP1.

Adam Stoller

The system I am talking about is a migrated store from TS6.1 which was running on Win2000SP4. The User has role "Editor" and in th past there hasn't been a problem with this user. The problem is also not specific to a workarea or user.

Personally I think the problem is related to Windows-SP1.

That's certainly a possibility - you need to check the supported platforms carefully because I think Windows SP's only got support after a certain TS SP's and you need to make sure the two are compatible.

You might need to open a support case to find out how to rectify the situation.