IPA process flow failing on last step

unknown

We are working on an existing IPA Rich Client process flow in our test environment. Every 3rd test we send through errors out and give the error message below.

I have a ticket with Infor on this issue - their resolution is not directly related to IPA Rich Client, it is related to a bug in MSCM handhelds (KB1681201). Has anyone encountered this type of error message, and how did you resolve it?

Process Flow error message:

Error encountered executing process ehs_pcs_jobreqapproval

PA42-1

Process: JobReq

Activity id: PA42

Error code: 5

Information code: 999

Return message:  2019-02-13 12:36:27 : INCIDENT_ID#1550079387865-0062 An error occurred outside of IOS while accessing Lawson Security

Output data:

<?xml version="1.0"?><ERROR key="SECURITY_ERROR" level="1"><MSG><![CDATA[ 2019-02-13 12:36:27 : INCIDENT_ID#1550079387865-0062 An error occurred outside of IOS while accessing Lawson Security ]]></MSG><DETAILS><![CDATA[ Check IOS logs for details. ]]></DETAILS></ERROR>

 

Log file error in IPA logs:

S3 Transaction PA42: Calling transaction server infordevapp.elliot-hs.org:443 with string _PDL=INFTRAN&PROD=INFTRAN&_TKN=PA42.1&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=Change&PJR-COMPANY=0100&PJR-REQUISITION=000307157&PJR-REQ-STATUS=WFAPPROVE&WEB-REQ-STATUS=WFAPPROVE&FROM-WORKFLOW=Y&PJR-APPROVAL-FLAG=Y&_DELIM=%09&_OUT=XML&_EOT=TRUE as user lawson

PA42_FieldName =

PA42_RETURN_MSG =  2019-02-13 12:35:55 : INCIDENT_ID#1550079355483-0061 An error occurred outside of IOS while accessing Lawson Security

PA42_RETURN_CODE = 999

Variables:

russel-cornelson

Good morning Jen,

Have you applied the fixes related to KB article 1681201?



The fix in that KB article may have been opened by the MSCM team and thus reported that way, but the solution was with lawson-httpclient.jar. IPA and MSCM along with a few other products installed remotely from the LSF server use the lawson-httpclient.jar to make /servlet/Router/Data/Erp and /servlet/Router/Transaction/Erp calls.



It's worth noting the fix addressed an intermittent issue that occurred; most commonly impacting clients who have ADFS and a LDAPBIND authentication method, where IPA/MSCM was using the LDAPBIND endpoint. When I say it was intermittent though, it wasn't every 3rd call. If you are failing every 3rd call you may be dealing with something else.



If you look in lawson-httpclient-error.log (located in the home directory of the user running Grid, usually C:Userslawson) and you see a bunch of /ssoconfig/SSOCfgInfoServlet errors ... straight up, apply this JT. If you don't see any errors in there enable trace logging by creating C:Userslawsonlawson-httpclient-trace.log



The creation of this file starts logging; duplicate the issue and submit the log to an Infor Process Automation Support engineer through Support Incident for review.



NOTE: be sure to remove the log after duplicating the issue; leaving it in that directory will eventually lead to problems with the system.