00920: Object being looked up was not found

Hi,

I installed Teamsite 6.7.1 SP1 with latest patch on a system with Windows 2003 SP1. Now when I try to run all of my old workflows from teamsite 6.5 SP2 I get the following error:

Invalid workflow:
ERROR: Could not add variable submittask_name to task Submit
ERROR: ERROR: 00920: Object being looked up was not found
ERROR: 00920: Object being looked up was not found

Any ideas on what could be causing this error.

Thanks

Tanuj

Find more posts tagged with

Comments

sumitk

Have you tried to verify whether your workflow is a valid XML? Was anything being changed?

Tanuj

Yes all my workflows xml are correct and working fine on my other teamsite 6.5 SP2 server.

Adam Stoller

Hi,

I installed Teamsite 6.7.1 SP1 with latest patch on a system with Windows 2003 SP1. Now when I try to run all of my old workflows from teamsite 6.5 SP2 I get the following error:

Invalid workflow:
ERROR: Could not add variable submittask_name to task Submit
ERROR: ERROR: 00920: Object being looked up was not found
ERROR: 00920: Object being looked up was not found

Any ideas on what could be causing this error.

Thanks

Tanuj

At what point is this error occurring? Is the error reproducible (always)?

I ask because it sounds like it is coming from an externaltask or cgitask script in which the TeamSite::WFtask object being used to perform the AddVariable() method is referencing a task object which is either no longer active or no longer existing (if the job that contained it was ended). Or perhaps, (and perhaps more likely) through an email interface in which the job / task referenced by the email no longer exists.

Tanuj

This is happening at very first step of the workflow. and yes you can reproduce it all the time.


        [cgitask owner="__INSERT__($BusinessUser);"
             name="Check for conflicts"
             start="t"
             immediate="t"]
        [areavpath v="__TAG__('iw_workarea');"/]
        [successors]
            [successorset description="Generate"]
                [succ v="Generate"/]
            [/successorset]
        [/successors]
        [command v="iwconflictcheck.cgi"/]
        [timeout v="+000001"]
            [succ v="Generate"/]
        [/timeout]
        __INSERT__(submit_files_xml());
        [variables]
            [variable key="submittask_name" value="SubmitChanges"/]
        [/variables]
    [/cgitask]

Adam Stoller

This is happening at very first step of the workflow. and yes you can reproduce it all the time.

[html]
name="Check for conflicts"
start="t"
immediate="t">

__INSERT__(submit_files_xml());

[/html]

The above is the code for a task called "Check for conflicts" - the error message clearly indicates that the error occurred with a task named "Submit" - which is retrieved in iwconflictcheck.cgi from the variable in the above task - which appears to say "SubmitChanges" not "Submit".

Nowhere in the 671SP1+Patch1 Windows version of iwconflictcheck.ipl (the Perl script not the binary wrapper) do I see it trying to set or add a variable called submittask_name as the error seems to indicate. Perhaps you need to check your copy of that script to see if it was modified?

Tanuj

Ghoti,

I copied the iwcheckconflict.ipl and cgi from old server too but even that didn't help.

and yes the ipl does have variable submittask_name.

Tanuj

Adam Stoller

Ghoti,

I copied the iwcheckconflict.ipl and cgi from old server too but even that didn't help.

and yes the ipl does have variable submittask_name.

Tanuj

I guess I didn't emphasize it clearly enough - the script references that variable - but it does not create / set it - at last not as far as I could see.

The error message you posted indicated that it could not add (which I read as "create" / "set") that variable to a task named "Submit" - the output you posted showed the variable in existence with a value of "SubmitChanges" -- so there's a mass of confusion here - of which, I'm afraid that I cannot really provide more help in clearing up.