Lawson PF Scheduler Error

 5 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Ward Mitchell
Veteran Member
Posts: 81
Veteran Member
    Friends, what gives with this error? I had to change the LAW_JAVA_HOME and LAW81_JAVA_HOME environment variables because the PF Scheduler would not even pop up. After changing them, I get the following error: HELP!!!

    We need this working ASAP so any help would be appreciated! Thanks in advance for your help!
    Attachments
    Jimmy Chiu
    Veteran Member
    Posts: 641
    Veteran Member
      env version?
      platform?
      can't see anything in the screenshot also.
      Ward Mitchell
      Veteran Member
      Posts: 81
      Veteran Member
        Yeah, the image is not keeping it size when I upload it. Here is the first part of the error:

        Login to URL: http:///bpm/daservlet (nested exception: Error: Unable to login. Exception: com.lawson.lawsec.authen.httpconnection.LHCException: sun.security.validator.ValidatorExceptions: PKIX path building failed....

        I just started getting this yesterday for no good reason!
        Jimmy Chiu
        Veteran Member
        Posts: 641
        Veteran Member
          can you do a "pfserv ping all" and post the status?
          Corrine Clark
          New Member
          Posts: 2
          New Member
            I did the ping all for Ward as I am the admin, and here are the results
            ProcessFlow RMI Server is running on XXX
            Event Manager running on XXX on Port XX
            ProcessFlow Server is running at XX at port XX
            ProcessFlow Scheduler is running on XXX
            XXX are the IP address and ports, it actually shows the correct information in the results.
            Jimmy Chiu
            Veteran Member
            Posts: 641
            Veteran Member
              Check your pfserv config.

              IOS Login Name:
              IOS Password
              ProcessFlow Web User:
              ProcessFlow web Password:

              Verify the passwords are valid and has not been changed. (Maybe your DC admin didn't set "password never expires" policy on the service accounts?)

              Retype in the valid password then recycle pf

              stoppfbpm
              startpfbpm