Absent Member.. JasonCantrell Absent Member..
Absent Member..
123 views

[OO Support Tip] path not found: '<flow path>' during a headless flow execution

Problem:

Using Operations Orchestration (OO) and when a headless flow is executed using RSFlowInvoke.exe/JRSFLowInvoke.jar/wget/curl...etc or by Scheduler,

the following error('error=path not found') can be seen in Central_wrapper.log:

 

  INFO   | jvm 1    | 2013/03/01 13:53:34 | ERROR [649045642@qtp0-470] (13:53:34,020) com.iconclude.dharma.services.execution.HeadlessServiceBase - request=/PAS/services/rest/run/Library/My Ops Flows/myFlow, error=path not found: '/Library/My Ops Flows/myFlow', host=127.0.0.1

 

Additionally if it is executed by a client like RSFlowInvoke.exe/JRSFLowInvoke.jar/wget/curl, it gets a response like:

 

  # ../jre1.6/bin/java -jar JRSFlowInvoke.jar "https://localhost:8443/PAS/services/rest/run/Library/My Ops Flows/myFlow" -u testuser01  -p ***

  <html>

  <head>

  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>

    <title>Error 404 request=/PAS/services/rest/run/Library/My Ops Flows/myFlow, error=path not found: '/Library/My Ops Flows/myFlow', host=127.0.0.1</title>

  </head>

 <body><h2>HTTP ERROR: 404</h2><pre>request=/PAS/services/rest/run/Library/My Ops Flows/myFlow, error=path not found: '/Library/My Ops Flows/myFlow', host=127.0.0.1</pre>

  <p>RequestURI=/PAS/services/rest/run/Library/My Ops Flows/myFlow</p><p><i><small><a href="http://jetty.mortbay.org/">Powered by Jetty://</a></small></i></p><br/>

  </body>

  </html>

 

Cause:

One of possible causes is that no read permission of the flow is granted to OO groups (including EVERYBODY) that the OO user belongs to.

Note that read permission of not only the (parent) flow but operations for steps and sub-flows used in the flow must be granted to the groups to avoid the 'path not found' error.

 

Solution:

1. Verify that the flow really exists in the public repository. "https://localhost:8443/PAS/services/http/list/Library/My Ops Flows/myFlow" -u testuser01 -p ***

2. Check if read permission of the flow, operations for steps and sub-flows used in the flow is granted to OO groups that the OO user belongs to. If not, grant it to at least one of the groups.

If the error still happens even after correcting the permission, its cause should be another one.

To break down the error, headlessly listing the flow by a problematic user and another user (like admin) would be helpful.

# ../jre1.6/bin/java -jar JRSFlowInvoke.jar

If a user has READ permission, a response of listing should be like

<?xml version="1.0" encoding="UTF-8"?>

<listResponse><listReturn><item>/Library/My Ops Flows/myFlow</item></listReturn></listResponse>

 

Otherwise,

 

 <?xml version="1.0" encoding="UTF-8"?>

<listResponse><listReturn/></listResponse>

 

Direct link to the document:

http://support.openview.hp.com/selfsolve/document/KM00374118

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Labels (2)
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.