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; } } }

iwsubmit error: ERROR:00920

JKSharma

Hi,

When i try to submit a file to staging , i'm getting the following error:

Invalid workflow:
ERROR:00920 : Object being lookedup was not found
ERROR: Couldnot add variable submittask_name to task Submit
ERROR: ERROR : 00920 : Object being lookedup was not found

does anyone know how to fix this?

thanks in advance
JK Sharma

Find more posts tagged with

Comments

nipper

Details on your file ? Check the permissions.

Is this the OOTB submit workflow or has it been modified ?

JKSharma

The file permissions are rw-rw-r and the user is the owner submitting the file.
the issue is with all the branches.

the workflow being used is attached.

Kindly suggest how to proceed, as i'm not able to submit any of the files.

thanks in advance
JK Sharma

nipper

That is not the workflow. That is the XML defining the WFT in available templates.

Have you had any training? This is an OOTB workflow which can be customized. Since there are about 10 different files in the workflow but only 4 that matter you should revert all the files to the initial state or write one from scratch using workflow Modeler.

JKSharma

missed out attachment. No changes were made to the wft solutions/configurable_default_submit.wft.

find the same as attachment.

thanks in advance.

Adam Stoller

Out of curiosity - what role(s) does the owner of the workarea have on that branch?

Although the error message doesn't indicate it, I have seen issues where "Authors" were made owners of workareas which "broke" the OOTB submit workflows because they automatically assign the workarea owner to the SubmitTask and "Authors" weren't (aren't) able to actually perform the submit command.

I'm pretty sure the error message is / was different for that case - but it's still work verifying your environment.

Also - make sure all the stores are unfrozen (just another thought)

JKSharma

the role of owner for the branch is admin.

Adam Stoller

the role of owner for the branch is admin.

Okay - that rules out that potential issue. And I'm assuming you've verified that none of the stores are frozen?

nipper

Try a command line submit.

See if it is a backingstore issue or a workflow issue.

cd /default/main/some/branch/WORKAREA/Content/
iwsubmit ms/local/index.html "comment"

the issue exist only from UI. the command iwsubmit is working when executed.

Adam Stoller

I don't think the problem is with the submit command as such - the error message from the original posting seems to indicate a problem with the Submit Task itself and not its operation.

Try creating your own simple workflow - something like:[indent]

submittask (start="t") -> endtask

[/indent]If that works, then compare all the various attributes for the submit task in this test workflow against those in the workflow that was failing and begin syncing them one-by-one.
If you manage to get all the way to the end with it working, then the problem has to be somewhere else - but if it breaks during the course of this process, you'll at least have narrowed down the issue.

If the very simplistic workflow doesn't work from the get-go, then you probably need to contact Support because there's something wrong with your setup (perhaps the owner of the TeamSite service is wrong?)

stya

Hi,

I have faced the same issue.

In my case the content store got corrupted when we did a copy of content store .It got solved.

Thanks,
stya

WideReportSplitAcrossPagesInPDF.rptdesign

Narmada

Hi can anyone Please tell the solution to fix this issue. i too came across this kind of error while triggering submit workflow. its a customized work flow.
Your support on this would highly be appreciated..

Adam Stoller

Hi can anyone Please tell the solution to fix this issue. i too came across this kind of error while triggering submit workflow. its a customized work flow.
Your support on this would highly be appreciated..

In short - since you already acknowledge that you're dealing with a customized workflow - you should realize that we cannot know anything about the workflow. And you should make an effort at providing a detailed description of everything you've attempted to diagnose / debug the issue on your own before asking others to help you.

Narmada

Version: TeamSite 6.7.2 Service Pack 2
OS : LINUX
recently our Team Site environemnt was crashed by third party members. Then we did reinstallation. after installation few of the core files were having the ownership of iwts user. due to that, we got so many issues. we are resetting the actual ownership and trying to fix those issues one by one. the issue i posted was one of them. when i click on submit, it is showing the above error. i have checked errror log,iwevents log,access log,opendeploy logs and workflow logs. Open Deploy logs and workflow logs are not updated as submit itself failed. and i didnt find any specific error related to this error in any one of the logs which i looked up. and iwsubmit is worked for me in backend as specified in this post.

Adam Stoller

When was the last time you ran iwfsck -d on your backing store?
If someone crashed your server, that's the first thing you should do when you get it back up. Re-installing the application doesn't verify the stability of the backing store (which I'm assuming you did not re-create from scratch).

As for the ownership on files being wrong - you may need to use iwidmap - but you also might need to run a chown on the backing store (do not do this without checking with Support first)

Narmada

as a team, we need to follow the staretegy proposed by our manager. its all done. Is there any solution to fix this submit issue.

nipper

as a team, we need to follow the staretegy proposed by our manager. its all done. Is there any solution to fix this submit issue.

Open a case with support. & then hire someone who knows what they are doing, something you are definitely lacking. Someone has to investigate what the state of your server is and propose some fixes. That is not something that can be done via a BBS like this.

ISCBorisB

Open a case with support. & then hire someone who knows what they are doing, something you are definitely lacking. Someone has to investigate what the state of your server is and propose some fixes. That is not something that can be done via a BBS like this.

Definitely a case for support. I *seem* to recall 6.7 bug that was sometimes causing this problem, something to do with unlocking.
If memory serves, it's been fixed in SP1. Narmada indicated 6.7.2 SP2, I wonder if SP2 is cumulative or SP1 should have been installed first.

Then again, it does not sound like a clean (re)install has been actually performed, could be anything
(Team Site was crashed...we did reinstallation...we got so many issues...)