rhettplace Absent Member.
Absent Member.
1164 views

Start Workflow throws "Error initializing scripting engine"


I have several workflow that run fine when started from the UA or Home
interfaces. However, when they are kicked-off in a driver policy by the
"Start Workflow" action the error, "Workflow Error: Error initializing
scripting engine or scripting context" is shown in the Request Status
section of the UA. The driver log shows that the workflow started
successfully, i.e. no problems with authentication or incorrect start
workflow parameters.

It seems that the workflow starts but is not able to run because of some
misconfiguration on the workflow engine side. The user who is assigned
to authenticate and start the workflow is the uaadmin (for now) and this
user can execute the workflows from UA and Home interfaces without any
issues. The uaadmin has the provisioning role assigned. Is there some
other permission that needs to be assigned to the user?

Thanks in advance for any help.


--
rhettplace
------------------------------------------------------------------------
rhettplace's Profile: https://forums.netiq.com/member.php?userid=876
View this thread: https://forums.netiq.com/showthread.php?t=53829

Labels (1)
0 Likes
3 Replies
wschreiber1 Absent Member.
Absent Member.

Re: Start Workflow throws "Error initializing scripting engine"

Rather than focusing on rights etc I'd look into the flowdata parameters
and their processing in mapping activities.

The error sounds like an unhandled exception. Check your server log, and
the dashboard for details - perhaps add some custom logging and/or
exception handling.

Wolfgang

On 03.07.2015 17:18, rhettplace wrote:
>
> I have several workflow that run fine when started from the UA or Home
> interfaces. However, when they are kicked-off in a driver policy by the
> "Start Workflow" action the error, "Workflow Error: Error initializing
> scripting engine or scripting context" is shown in the Request Status
> section of the UA. The driver log shows that the workflow started
> successfully, i.e. no problems with authentication or incorrect start
> workflow parameters.
>
> It seems that the workflow starts but is not able to run because of some
> misconfiguration on the workflow engine side. The user who is assigned
> to authenticate and start the workflow is the uaadmin (for now) and this
> user can execute the workflows from UA and Home interfaces without any
> issues. The uaadmin has the provisioning role assigned. Is there some
> other permission that needs to be assigned to the user?
>
> Thanks in advance for any help.
>
>

0 Likes
rhettplace Absent Member.
Absent Member.

Re: Start Workflow throws "Error initializing scripting engine"


The cause ended up being related to formatting of the DNs. I found
these two logging packages to be helpful; com.novell.nds.dirxml.ldap and
com.novell.nds.dirxml.util. Once I set those to debug, there was
sufficient information to troubleshoot. Without those logs, it's a
total black box.


--
rhettplace
------------------------------------------------------------------------
rhettplace's Profile: https://forums.netiq.com/member.php?userid=876
View this thread: https://forums.netiq.com/showthread.php?t=53829

0 Likes
Knowledge Partner
Knowledge Partner

Re: Start Workflow throws "Error initializing scripting engine"

On 7/6/2015 11:24 AM, rhettplace wrote:
>
> The cause ended up being related to formatting of the DNs. I found
> these two logging packages to be helpful; com.novell.nds.dirxml.ldap and
> com.novell.nds.dirxml.util. Once I set those to debug, there was
> sufficient information to troubleshoot. Without those logs, it's a
> total black box.


I used to maintain a page where you could go edit and update with a note
like this, that they were helpful, possibly with examples, for the 'next
guy' but it was taken down at someones request.

If you send me some samples I will update a copy I maintain and share
the secret location it is hosted. My email is my full name using gmail.


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.