Failed to instantiate a workflow model error

My issue is that I get an error "Failed to instantiate a workflow model. Click details for more information, or contact your system administrator." whenever I submit workflow for a specific branch.

Here is the real issue, workflow is submitted successfully from some branches not listed in available_templates.xml. However, some branches also not listed in available_templates.xml also give the above error, which I can't seem to understand this inconsistency. Can these non-seen branches be customized into another non-obvious config file location. If yes where, I have checked wft and opendeploy/conf folders and don't see any reference for these non seen branches.

When I try to add the missing branch, this specific workflow is removed from the workflow instantiation screen. We previously used teamsite 6.7.1 (used missing branches in available_templates.cfg) before upgraded to 7.3.2 (now using available_templates.xml)

Any help in resolving this issue is greatly appreciated.

Thanks guys.

Find more posts tagged with

Comments

Rick Poulin

It would help if you posted the relevant section of your available_templates.cfg file. What you describe doesn't make sense, so you must have something wonky in there. Or, if your workflow in question is a WFM, then you'll actually want to look at available_models.xml (in the /iwadmin/main/workflowModels branch)

As for the "can't instantiate" problem, that's seperate and is not related to the above configs. It's usually caused by the workflow wanting to set task ownership to a user or group that is not allowed in that workarea. It would help if you provided the stack trace from the 'details' button though.

shameem

Environment: TS 7.3.1 Windows

Using WFM 1.0.1 (external client) to build the workflow.

I am getting the following error "Failed to instantiate a workflow model. Click details for more information, or contact your system administrator."

Gone through various articles which says "if any user/group doesnot have previliges to own a task caused this issue" and also says "to click the details for more information and share that info".

Unfortunately

- I donot see any link for clicking the details.

- To debug there is nothing reported in logs.

- Iwjoberrors.log (only log file updated) shows only a small xml with job variables.

- Debug true, job specification shows only small xml with job variables.

- All my job tasks are owned by myself(initiator - as $iw_user used for all tasks) and I am the master and have full access to the workarea too.

- I am able to initiate successfully another workflow from the same branch/wa where I am initiating this workflow.

Need your hlep/suggestion to dig the rootcause.

1. Where is this "click the details..." link situated. Is it a known bug from HP where you say to click and dont have a link to click.

2. Is there any verbose which I can increase to log more exact information.

3. If a user is deleted from AD/LDAP, I get a big number as S-1-5-21-434333158-1563304843-1661670574-1650044. How do I know which user is been removed. is there any way to find out.

#3 is little deviated from the issue but looking at all directions as this workflow was working fine suddenly stopped working. Looking at deleted users information too.

Appreicate your help.

shameem

My problem resolved.

Based on instantiation screen selections, workflow is directed in to different processes flows. Instantiation screen variables updated recently, but not the script variables on the flow line which decides where to go. As a result the workflow couldn't move ahead from "start" as none of the flow line is true.

So actual problem is resolved.

Looking forward for your valubale inputs on #1 and #3.

Rick Poulin

1. Where is this "click the details..." link situated. Is it a known bug from HP where you say to click and dont have a link to click.

The dialog box is rendered with Javascript, so there are some situations where special characters in the stack trace cause JS exceptions, leading to the UI misbehaving. Sometimes you can inspect the source of the window to find it, or usually there's a copy in server.log and/or content_center.log.

3. If a user is deleted from AD/LDAP, I get a big number as S-1-5-21-434333158-1563304843-1661670574-1650044. How do I know which user is been removed. is there any way to find out.

You can use iwidmap to export a list of all users in a store. Find this SID in the XML file and note the entity ID. Then, go in TeamSite/local/entities/Data and open the file with the number you recorded. If that SID ever logged into TeamSite, you should still have a few details in this entity file, including what used to be the username.