Prev
Next
Forums Integration / Customization IPA/ProcessFlow

Running ssoconfig from IPA

 6 Replies
 2 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
JimY
Veteran Member
Posts: 510
Veteran Member
2/4/2016 1:02 PM

    I have a flow that uses the syscmd node to execute a bat file that contains the command: ssoconfig -S pwd D:\Data\SyncFile\Sync_File.xml.  This is supposed to perform a list based sync.  If I run the bat file from the command line on the server it works fine without any issues.  If I execute the bat file from IPA I get the following error: 

    

    com.lawson.lawsec.util.LawsonEventException:Required attribute SYNC_STATUS is missing from message (Error: No more tokens).
    
 (and 468 additional characters)
    
     Command error output: com.lawson.lawsec.util.LawsonEventException:Required attribute SYNC_STATUS is missing from message (Error: No more tokens).
    
    at com.lawson.lawsec.server.events.LSFBaseEvent.getNextMsgAttribute(LSFBas (and 393 additional characters)
    
     System command returned error code 0 

     

    Not sure what to do with this one.  I opened a ticket with Infor, but haven't had much progress so I thought I would post it hear.  This is on a Windows Server 2008r2 and the landmark version is 10.1.1.23.  Thank you.

     

    JimY
    Veteran Member
    Posts: 510
    Veteran Member
    2/4/2016 1:04 PM
      I forgot to mention that our LSF environment version is 10.0.6.
      John Henley
      Posts: 3353
      2/4/2016 1:21 PM
        what options are you using on the syscmd node?
        Thanks for using the LawsonGuru.com forums!
        John
        JimY
        Veteran Member
        Posts: 510
        Veteran Member
        2/4/2016 1:42 PM
          Execution mode is set to automatic and Combine error output into standard output is checked. I define the ssoconfig command in a variable in the Start node and use that in the syscmd node in the command section. Thank you.
          DavinM
          New Member
          Posts: 2
          New Member
          3/6/2016 9:33 AM
            Hi Jim,
            What a weird coincidence... I just ran into this problem yesterday. Our company is working on an upgrade from LSF 9.0.1.12 to 10.0.7. I'm in the process of modifying a user provisioning processflow to run ssoconfig and trigger a list-based sync. I'm experiencing the same problem that you are. If I run the command directly on the S3 server it works fine but errors out in the flow. I was about to create an Infor ticket and I saw your post here.

            I tried running ssoconfig directly in syscmd, through a batch file, even wrote a console application which executes the ssconfig process and tried call my application in syscmd but nothing works. I think my last resort is to have my flow dump the sync files in a folder and develop a custom Windows service pick them up and run the list-based sync. Please let me know if you find a solution to this problem. Thanks!
            JimY
            Veteran Member
            Posts: 510
            Veteran Member
            3/6/2016 11:52 PM
              There is a patch for 10.0.6 to correct this, but the patch caused a problem with ISS. The resource information would show up blank So I had to back out the patch. I opened a ticket with Infor and they released an updated ISS (DSP) to correct this, but for it to work correctly we had to be on landmark version 10.1.1.25 or higher. We are on 10.1.1.23. I ended doing basically what you are doing. I create a file from the flow and use a powershell script executed through Windows task scheduler to run it. Not the best solution, but the best I could come up with until we upgrade Landmark.  I would still open a ticket with Infor to see if there is a patch for 10.0.7 (It was for ssoconfig).  Depending what version of Landmark and ISS you are on it might solve your problem.  Good luck.
              DavinM
              New Member
              Posts: 2
              New Member
              3/7/2016 8:00 PM
                Jim, I appreciate the info. I'll open up a ticket but most likely I'll have to implement the workaround. We're currently in a code freeze leading up to our ERP upgrade. Thanks!