Prev
Next
Forums Infor / Lawson Platforms S3 Systems Administration

lajs not starting

 12 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
Roger French
Veteran Member
Posts: 549
Veteran Member
5/23/2012 4:01 PM
    We have installed 9.0.1.9 with patches, on environment on Win2008, SQL2008
    Each and every time when the environment is stopped or restarted, or the server rebooted,  lajs does not launch or execute. We have to manually execute the startlajs command which works fine and OK.

     I have a case open with Lawson but after many days, there hasn't been much more to add. 

    Has anyone have any ideas how to resolve this? 

    From lajs.log file the error message is:


    Mon May 21 23:55:40 2012: Job Server Version 9.0.1.9.415 2012-03-04 04:00:00 (201111) Started By NT AUTHORITY\SYSTEM, Pid=10224.
    Mon May 21 23:55:40 2012: NICE = 20, RUNJOBS = 10
    Mon May 21 23:55:40 2012: CHECKFREQ = 2 min, EXECTIMEOUT = 180 sec
    Mon May 21 23:55:40 2012: VERBOSE = OFF
    Mon May 21 23:55:40 2012: DEBUGLEVEL = 0
    Mon May 21 23:55:40 2012: 
    Mon May 21 23:55:40 2012: Job Queue initialize issued by:  NT AUTHORITY\SYSTEM
    Mon May 21 23:55:40 2012: Checking for stale queue messages. . .
    Mon May 21 23:55:40 2012: Stale queue messages found, processing. . ..
    Mon May 21 23:55:40 2012: Processing complete.
    Mon May 21 23:55:41 2012: Job Server Ready.
    File GEN/EXECUTABLE.
    OpenDBFile2 error is Unable to communicate with database driver process (99).
    Additional information is 1171.






    Greg Moeller
    Veteran Member
    Posts: 1498
    Veteran Member
    5/23/2012 7:02 PM
      looks to me like the database isn't up (fully) when the startlaw issues the startlajs command.
      It's having trouble communicating with GEN at least.
      Not sure how you would fix this though?
      Check your CAP file for GEN... but I'd suspect that's OK since you are able to run it manually.
      Jimmy Chiu
      Veteran Member
      Posts: 641
      Veteran Member
      5/24/2012 12:50 PM
        Are they on the same server? The application server and the database server.
        Roger French
        Veteran Member
        Posts: 549
        Veteran Member
        5/24/2012 4:29 PM
          Yes they are
          Jimmy Chiu
          Veteran Member
          Posts: 641
          Veteran Member
          5/25/2012 5:52 PM
            Looks to me that lawson service is starting before your SQL database engine service completed startup. Thus, the error.

            To ensure the lawson service starts AFTER SQL completed startup.

            Add multi-string value (REG_MULTI_SZ) "DependOnService" to your lawson service in registry. Populated data of this multi-string value with the name of your SQL service, which is probably "MSSQL" or "MSSQL$instanceName"

            With this, lawson service will wait until SQL service finished starting, then it will start.

            NOTE: if you have setup WAS cell/nodeagent/application server to start automatically as windows service, you may need to add the DependOnService key to the WAS services, so it will wait for Lawson service finished starting up first.

            IE: SQL Database Engine > Lawson Service > WAS Cell/Node/Application server.
            Roger French
            Veteran Member
            Posts: 549
            Veteran Member
            5/25/2012 7:24 PM
              Thanks Jimmy, I already have the service dependencies set up, much like you described, but the issue still occurs. 

              I think it's something in the database config. This is SQL 2008, Win2008, using LUU.

              ladb.cfg:

              DICTS 15 /* maximum number of open dictionaries */
              *
              FILES 1500 /* maximum number of open files                       */
              * /* If adjust FILES, must also adjust kernel value(s). */
              *
              FOREIGN 100 /* maximum number of foreign servers                    */
              * /* FOREIGN should be set to same value as USERS.        */
              * /* If adjust FOREIGN, must also adjust kernel value(s). */
              *
              IFILES 450 /* number of open files per foreign server       */
              * /* IFILES should be set to same value as UFILES. */
              *
              LFILES 9 /* number of open files per lafile                     */
              * /* If adjust LFILES, must also adjust kernel value(s). */
              *
              UFILES 450 /* maximum number of open files per user         */
              * /* UFILES should be set to same value as IFILES. */
              *
              USERS 100 /* maximum number of user processes                   */
              * /* USERS should be set to same value as FOREIGN.      */
              * /* If adjust USERS, must also adjust kernel value(s). */
              *
              Jimmy Chiu
              Veteran Member
              Posts: 641
              Veteran Member
              5/29/2012 1:30 PM
                Comparing your ladb.cfg to mine. I am on Win2008R2 SQL2008R2 also (seperate servers however).

                The only differences are the USERS and FOREIGN, mines are at 500.

                Roger French
                Veteran Member
                Posts: 549
                Veteran Member
                5/29/2012 8:07 PM
                  Thx Jimmy,

                  We're using LUU.

                  I'm trying to look into the variables here. Are you also using LUU or MKSToolkit?
                  Jimmy Chiu
                  Veteran Member
                  Posts: 641
                  Veteran Member
                  5/30/2012 11:43 AM
                    We are using LUU also.
                    Jimmy Chiu
                    Veteran Member
                    Posts: 641
                    Veteran Member
                    5/30/2012 11:48 AM
                      There are rare instance where QUEUEDJOB has gotten too large for lajs to auto-start. Will need to do DELJOBHST on QUEUEDJOB to clean things up.
                      Bart Conger
                      Advanced Member
                      Posts: 18
                      Advanced Member
                      5/30/2012 6:25 PM
                        Hey Roger, something you could try is to remove the automatic startup of the Lawson env service and automatic startup of the WAS services, leaving ADAM/ADLDS as automatic. Then create a .bat file with the start for lawson and WAS with a wait command. I put this in for the wait command, some it is as much as 90 seconds before I initiate Lawson start.

                        example of wait in bat file
                        REM Delay 60 seconds
                        ping -n 61 127.0.0.1 > nul

                        On a manual restart of Lawson without the server, validate that the WAS service(s) have stopped according to the logs, vs reviewing the status bar of the service itself for IBM - WAS.

                        I've used this successfully at other clients when there is an issue with startup of lajs on Windows systems. Hope it helps.

                        Last scenario would be to remove the automatic start of Lawson service and start each module separate (even though not recommended) to see if it resolves stop/start.

                        On another note, performing some 9.0.1.9 Env upgrades myself, would you be willing to share the patch bundle and base 9. I wonder if it is specific to your bundle?

                        Good luck,
                        Bart
                        Roger French
                        Veteran Member
                        Posts: 549
                        Veteran Member
                        5/31/2012 11:22 AM
                          Bart, I have seriously thought about doing this exactly but have not implemented it yet. 

                          This bundle 9.0.1.9 is the only instance where I've had this issue. It's just 'surprising' to say the least. I've never had this issue on any other install I've done.
                          RickyY
                          Veteran Member
                          Posts: 50
                          Veteran Member
                          9/21/2014 11:34 AM
                            The lajs is not starting up during our LSF 13 upgrade. Anyone have any ideas?