Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Integration / Customization
IPA/ProcessFlow
Lawson forms no longer triggering Workunit after Landmark Installation
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jeffin Joy
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
4988
People Online:
Visitors:
55
Members:
0
Total:
55
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1377
Roger French
1315
mark.cook
1244
Chris Martin
825
Forums
Filtered Topics
Unanswered
Unresolved
Active Topics
Most Liked
Most Replies
Search Forums
Advanced Search
Prev
Next
Forums
Integration / Customization
IPA/ProcessFlow
Lawson forms no longer triggering Workunit after Landmark Installation
Please
login
to post a reply.
1 Replies
0
Subscribed to this topic
53 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
Demichener
New Member
Posts: 0
4/8/2014 2:49 PM
Lawson apps 9.0.1.11; Landmark 10.0.6.0. We are in the processes of implementing Landmark (no LTM, no procuments, no stategic sourcing). We had several customized PFlows for Job Reqs, Personnel Actions and Purchase Requisitions (all using pre-defined Services, Processes, Form, etc). We can trigger the flows in landmark. We can trigger the flows using wfwk.1 in Lawson. But when we try to trigger the flows from the lawson form(or LID:lapm) - we get API return codes of 1 and 7 referencing a 'variable'. The lapm logs are showing com.lawson.bpm.eprocessserver.interfaces.LPSConnectionException: Null Proxy for: com.lawson.bpm.eprocessserver.interfaces.LPSDatabaseBridgeForLSF DataArea: conv
at com.lawson.bpm.eprocessserver.interfaces.LPSGridSession.checkForNullProxy(LPSGridSession.java:199)
at com.lawson.bpm.eprocessserver.interfaces.LPSGridSessionForLSF.isServiceExistAndEnabled(LPSGridSessionForLSF.java:172)
pfrmi.log .....
com.lawson.bpm.netutils.LPSConnectionException: Unable to create LPSGridSession - Process Server is not running for data area: BLANK-HERE
Any ideas, suggestions.....
Peter O
Veteran Member
Posts: 69
5/14/2015 5:30 PM
Split
I know this is an old question - but maybe a response will help someone in the future searching about this issue (I found this googling a related issue
):
This error & similar is referenced in the Lawson/Infor documentation: Infor Lawson System Foundation Using Infor Process Automation Configuration Guide
It looks like there's a configuration issue with your BPM.properties file referencing a nonexistant data area, or that the process server is not running, you've configured the connection URL incorrectly, or some other config issue along those lines. I would double check your configuration and refer to the documentation I referenced above.
"Process Server is not running for data area: BLANK-HERE" shows that "BLANK-HERE" is the data area attempting to be connected to.
Page 32 references this error and pages 25 and on are very useful to double check your configuration setup.
Also, I've noticed that - after you set up landmark, ensure process server is running, and config your BPM properties file on the LSF side, you may need to recycle the servers.
Did you resolve your issue, and am I on the right track with how you did resolve it?
Please
login
to post a reply.