Prev
Next
Forums User Experience Lawson Portal

Lawson portal jobs -submit

 4 Replies
 2 Subscribed to this topic
 13 Subscribed to this forum
Sort:
Author
Messages
Chesca
Veteran Member
Posts: 490
Veteran Member
2/4/2016 3:50 PM

     Hi, we have a new user that's setup with the same access as other users. She is trying to submit a job but for some reason that job never gets submitted and there is no error message provided. When accessing the job she created, she is not able to click on any of the buttons including submit, reports, job sched, print Mgr. I sent the log to Lawson and there is not errors in the log. Our admin guys says there is no issues with her security access.  

    Here is an error I got when I tried to replicate the issue:

    com.lawson.ios.common.impl.SecurityViolationException: AM260

    ClaireH
    Basic Member
    Posts: 5
    Basic Member
    2/4/2016 3:58 PM

      Any chance you are iseries?

      Chesca
      Veteran Member
      Posts: 490
      Veteran Member
      2/4/2016 4:22 PM

        No, we are not iseries. Windows server

        Chesca
        Veteran Member
        Posts: 490
        Veteran Member
        2/4/2016 4:22 PM

          No, we are not iseries. Windows server

          ClaireH
          Basic Member
          Posts: 5
          Basic Member
          2/4/2016 4:34 PM
            Well then this may not help you but maybe it will ring a bell somewhere....we had a very similar issue with one of our iseries users last month. I opened a ticket with Lawson - this is an excerpt from the ticket where we figured out what was wrong:
            we checked the lajs log on the OS
            WRKACTJOB and looked for lajs, did a 5
            when that opened, we searched to the bottom and found the entry for this user and job
            on the message we did a 10 for additional information
            we found a message that said missing message queue
            NOTE - the message queue is normally created when you add a new user
            since this was missing, we returned to the command line and ran:
            CRTMSGQ and created a message queue for the user.
            once this was completed, the jobs run successfully.