Prev
Next
Forums Infor / Lawson Platforms S3 Systems Administration

tsSendDbMsg Invalid argument

 3 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
Ben Coonfield
Veteran Member
Posts: 146
Veteran Member
4/22/2009 8:03 PM

    Has anyone seen a failure message similar to this in the ladb.log?

    api (tsSendDbMsg): Serious Error, Unable to send ladb message via connection 6291472: Invalid argument
    IpcMsg is: MsgType 1, Cmd 0, UserNbr 2, Datum 24, spid 1024074, scmd 9, snd user.2
     

    I have seen several variations of this.  Pre-LSF the message for what I think is the same problem looked more like:

    ladb task failed with logn message ladb (SendFiMsg): can't msgsnd()
    Id = 0 Size = 36 Invalid argument

    This has occurred several times, although with months between occurrences.

    Gary Davies
    Veteran Member
    Posts: 248
    Veteran Member
    4/23/2009 9:47 AM
      The serious error message for the connection may indicate that there may have been a user session that was hung open when lawson shutdown. These 'Serious Error' messages can be ignored. You may want to check the latm.cfg file for the 0x70 environment and see what the value for the remotmachines and remoteprograms is set at. If they are set to 10, change them to 1, which will cause Lawson to use up less message queues when it is started.
      Ben Coonfield
      Veteran Member
      Posts: 146
      Veteran Member
      4/24/2009 11:03 PM
        Unfortuantely this one can't be ignored -- it is associated with a ladb failure. I have looked at the remotemachines & remoteprograms options, but the doc doesn't say much to indicate what they really do. I've got remotemachines=1, & remoteprograms=10.
        John Henley
        Posts: 3353
        4/25/2009 1:19 AM
          Can you describe the situation a bit, e.g. Is this production or test, how often, what is affected, what are the symptoms, etc.
          Thanks for using the LawsonGuru.com forums!
          John