Prev
Next
Forums Infor / Lawson Platforms S3 Systems Administration

FILE GEN EXECUTABLE

 7 Replies
 2 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
Murtaza2016
New Member
Posts: 1
New Member
7/15/2016 7:01 AM

    am getting error when opening any command like pgmdef dbdef

     

    FILE GEN/EXCUTABLE

    OPEN DB FILE2 Error is drivef failed (54)

    oracle database is up running and can connect using sql with Lawson id

     

     

    JimY
    Veteran Member
    Posts: 510
    Veteran Member
    7/15/2016 10:49 AM
      Did anything change prior to this happening? Was it working before?
      Murtaza1973
      Posts: 3
      7/16/2016 5:51 AM
        yes it was working fine, have realized ladb is not starting

        Enterprise server manager (ladb) version 9.0.1.7.181 2010-08-10 04:00:00 (201010)
        $GENDIR = E:\Lawson\lsf1\gen
        $LAWDIR = E:\Lawson\lsf1\law
        $LADBDIR = E:\Lawson\lsf1\db
        $LAWIPC = 0x80
        Global settings:
        DICTS 25, FILES 603, FOREIGN 100, IFILES 450, REUSE 1,DBAPIERRORS = ON,
        LOCKTRY1 5, LOCKTRY2 7, UFILES 450, USERS 200,
        LAWSONUID ,
        MAILUSER root
        Lawson database settings:
        AUDIT 0, BALANCE 50, CACHE 50, DEBUG 0, LAFILES 67, LFILES 9,
        ULIMIT -1
        Fri Jul 15 11:41:07 2016: ladb (LoadLic): added license for 999 df users
        Fri Jul 15 11:41:07 2016: ladb (LoadLic): added license for 999 un users
        Fri Jul 15 11:41:07 2016: ladb (LoadLic): added license for 20 AD users
        Fri Jul 15 11:41:07 2016: ladb (LoadLic): added license for 20 AM users
        Fri Jul 15 11:41:07 2016: ladb (LoadLic): added license for 20 AP users
        Fri Jul 15 11:41:07 2016: ladb (LoadLic): added license for 20 AR users
        Fri Jul 15 11:41:07 2016: ladb (LoadLic): added license for 20 BL users
        Fri Jul 15 11:41:07 2016: ladb (LoadLic): added license for 20 GL users
        Fri Jul 15 11:41:07 2016: ladb (LoadLic): added license for 20 LM users
        Fri Jul 15 11:41:07 2016: ladb (LoadLic): added license for 20 MA users
        Fri Jul 15 11:41:07 2016: ladb (LoadLic): added license for 20 ML users
        Fri Jul 15 11:41:07 2016: ladb (LoadLic): added license for 20 SL users
        Fri Jul 15 11:41:07 2016: ladb (LoadLic): added license for 999 BN users
        Fri Jul 15 11:41:07 2016: ladb (LoadLic): added license for 999 TA users
        Fri Jul 15 11:41:07 2016: ladb (LoadLic): added license for 999 LP users
        Fri Jul 15 11:41:07 2016: ladb (LoadLic): added license for 999 PA users
        Fri Jul 15 11:41:07 2016: ladb (LoadLic): added license for 999 TP users
        Fri Jul 15 11:41:07 2016: ladb (LoadLic): added license for 999 PR users
        Fri Jul 15 11:41:07 2016: ladb (main): can't create shared memory
        Invalid argument (22)
        Fri Jul 15 11:41:07 2016: ladb (ShutDown): initiated (-2)
        Fri Jul 15 11:41:07 2016: ladb (ShutDown): startup
        ladb: Database server startup failed.
        Fri Jul 15 11:42:29 2016: [UNKNOWN] tsConnectInit (0) Unable to attach the ladb shared memory segment
        Fri Jul 15 11:42:30 2016: [UNKNOWN] tsConnectInit (0) Unable to attach the ladb shared memory segment

        Enterprise server manager (ladb) version 9.0.1.7.181 2010-08-10 04:00:00 (201010)
        $GENDIR = E:\Lawson\lsf1\gen
        $LAWDIR = E:\Lawson\lsf1\law
        $LADBDIR = E:\Lawson\lsf1\db
        $LAWIPC = 0x80
        Global settings:
        DICTS 25, FILES 603, FOREIGN 100, IFILES 450, REUSE 1,DBAPIERRORS = ON,
        LOCKTRY1 5, LOCKTRY2 7, UFILES 450, USERS 200,
        LAWSONUID ,
        MAILUSER root
        Joe O'Toole
        Veteran Member
        Posts: 314
        Veteran Member
        7/17/2016 10:16 AM
          We have been plagued by this error for several years. In our case it was caused by an orphaned Java PID that never closed when the env service was restarted. It got so bad that I had to write a script to find and terminate any Java PIDs relating to Lawson before trying to start my env service back up. When we rebooted the OS it was never a problem but we are trying to reduce the number of times we reboot which before developing the workaround was several times per week. I had several support tickets on this with Infor and they found some issues with our process flow startups which reduced the number of orphaned PIDs but the problem was never completely resolved. I hope the problem goes away when we move to V10.
          Murtaza1973
          Posts: 3
          7/18/2016 6:23 AM
            Thanks can you pls share the script to find and terminate any java PIDs
            Murtaza1973
            Posts: 3
            7/18/2016 9:31 AM
              for now am getting FILE GEN/EXCUTABLE

              OPEN DB FILE2 Error is drivef failed (54)
              JimY
              Veteran Member
              Posts: 510
              Veteran Member
              7/18/2016 9:47 AM
                I found this KB on the Infor Support site. KB 1190006. Maybe if will help.
                Joe O'Toole
                Veteran Member
                Posts: 314
                Veteran Member
                7/25/2016 1:04 PM
                  I can't post my code but I can tell you it's basically Windows cmd script using a combination of Handle, Findstr and Taskkill commands.
                  Some of these tools may not be supplied with Windows but are readily available to download.
                  This job can be used to find any PID related to a given string which is passed to the script (Lawson, BPM, etc).
                  I run this when the ENV is down before trying to start it back up, if everything shut down properly when the ENV was stopped there should be no active processes related Lawson apps.
                  If any thing is found it kills them off so we don't end up with failure of some of the ENV startup processes due to shared memory segment error.