Prev
Next
Forums Integration / Customization IPA/ProcessFlow

Error changing named job

 3 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Joe Haveman
Advanced Member
Posts: 31
Advanced Member
3/25/2010 12:48 PM

    Does anyone know what would prevent a user from changing a named job?

    I am using a transaction object to change the AR580. I've also tried add and delete. When I run the ProcessFlow using *Run on server*, it seems that PF changes to a different user account (service account?) and it fails with a connection error. When I run the flow locally, it works fine. Just not when I use *Run on server*.

    (I've checked my other flows where I use a transaction object. It uses the service account and works fine when I use *Run on server*. I'm wondering if a user has to have special permissions to change a named job.)

    I just don't know if its a user-domain issue or a lawson-configuration issue or a processflow issue.

    Any ideas?

    Joe

    Error while Executing activity : Type=AGS, ActivityName=Transaction7200, ActivityId=AGS4, WorkUnit=1069 Date:03/25/2010 Time:08:53:08

    Error while executing Transaction Activity .....java.lang.Exception: Error connecting to with user pfadmind Query string

    at com.lawson.bpm.coreutils.CGIInvoker.invoke(Unknown Source)
    at com.lawson.bpm.coreutils.CGIInvoker.invoke(Unknown Source)
    at com.lawson.bpm.coreutils.CGIInvoker.invoke(Unknown Source)
    at com.lawson.bpm.database.transaction.Transaction.doQuery(Unknown Source)
    at com.lawson.bpm.database.transaction.Transaction.doQuery(Unknown Source)
    at com.lawson.bpm.processflow.workFlow.flowGraph.FgaAgs.startActivity(Unknown Source)
    at com.lawson.bpm.processflow.workFlow.flowGraph.FgActivity.execute(Unknown Source)
    at com.lawson.bpm.processflow.workFlow.flowGraph.FgProcess.run(Unknown Source)
    at com.lawson.bpm.pfengine.ProcessFlowEngine.execute(Unknown Source)
    at com.lawson.bpm.pfengine.ProcessFlowEngine.startProcessAt(Unknown Source)
    at com.lawson.bpm.eprocessserver.KBConnection.startProcess(Unknown Source)
    at com.lawson.bpm.eprocessserver.KBConnection.startProcessDesigner(Unknown Source)
    at com.lawson.bpm.eprocessserver.KBConnection.execute(Unknown Source)
    at com.lawson.bpm.eprocessserver.KBConnection.run(Unknown Source)
    at com.lawson.bpm.eprocessserver.util.ThreadPool$PooledThread.run(Unknown Source)
     

    David Williams
    Veteran Member
    Posts: 1127
    Veteran Member
    3/25/2010 1:04 PM
      Do you log into the Designer as the pfadmind user? Try that and see if you get the same error.
      David Williams
      Joe Haveman
      Advanced Member
      Posts: 31
      Advanced Member
      3/25/2010 2:31 PM

        It works locally and does not work run on server.

        Joe Haveman
        Advanced Member
        Posts: 31
        Advanced Member
        3/26/2010 1:15 PM
          We solved our problem with this. For us, the problem was two-fold. One, our service account was messed up. Two and most importantly, we noticed a "bad Lawson character". There was a '\' in one of the parms for the AGS call and it was blowing up simply saying "Error connecting to...."

          We changed the bad character to the percent-ascii-hex value. In our case, we had to use '%5C' instead of the back-slash.

          Thanks...Joe