Prev
Next
Forums Infor / Lawson Platforms Lawson Landmark

Errors installing Grid

 10 Replies
 0 Subscribed to this topic
 32 Subscribed to this forum
Sort:
Author
Messages
Gary Padgett
Veteran Member
Posts: 90
Veteran Member
8/13/2012 5:13 PM
    First-time attempt at installing Grid on new Win2008R2 server.  Have installed Perl and Java.  The Grid installation works up to the point where it appears to be trying to start the Grid service, then fails with Java errors.  The log folder for the install just says "failed to load dll: C:\Program Files\Java\jdk1.6.0_33\jre\bin\server\jvm.dll.  Message: Error: 193 Message: (null)
    Any ideas?
    Thanks
    John Henley
    Posts: 3353
    8/13/2012 5:38 PM
      Install JDK to no spaces location, e.g. C:\JDK
      Make sure JAVA_HOME is set and added to PATH.
      Thanks for using the LawsonGuru.com forums!
      John
      Gary Padgett
      Veteran Member
      Posts: 90
      Veteran Member
      8/13/2012 6:31 PM
        I installed to C:\JDK etc. Now the service fails because of
        "no jdk files found at path C:\Program Files\Java\jdk1.6.0_33\jre\bin\client\jvm.dll"

        Well, I didn't install it there!
        When I enter "where java" it gives "C:\Windows\System32\java.exe" and not this other location where I really installed it.
        My JAVA_HOME is set to C:\JDK\Java\jre6
        John Henley
        Posts: 3353
        8/13/2012 7:07 PM
          Make sure you are installing both the 32-bit *AND* the 64-bit JDKs (they are separate installs).
          Point %JAVA_HOME% to the 64-bit JDK,
          Add %JAVA_HOME%\bin to the PATH -- at the beginning.
          Thanks for using the LawsonGuru.com forums!
          John
          Gary Padgett
          Veteran Member
          Posts: 90
          Veteran Member
          8/13/2012 7:25 PM
            I would never have guessed to install both. Do I need to install the 32-bit to an alternate directory with no embedded spaces, like I did on 64-bit?
            John Henley
            Posts: 3353
            8/13/2012 7:54 PM
              Yes, if I remember correctly, you need to do both.

              Are you getting the error when running "installLcmServer.jar"?
              If so, also make sure you are including the JDK location, e.g.
              %JAVA_HOME%\bin\java –jar installLcmService.jar

              Try that first.
              Thanks for using the LawsonGuru.com forums!
              John
              Gary Padgett
              Veteran Member
              Posts: 90
              Veteran Member
              8/13/2012 8:05 PM
                No, the error comes after the install, when trying to start the Grid service. I am not installing LifeCycleManager, as Grid has its own standalone installer now. (Confirmed by Lawson support)
                John Henley
                Posts: 3353
                8/13/2012 9:07 PM
                  OK, what version are you installing? I don't want to be leading you down the wrong path...
                  Thanks for using the LawsonGuru.com forums!
                  John
                  Gary Padgett
                  Veteran Member
                  Posts: 90
                  Veteran Member
                  8/14/2012 10:53 AM
                    The java version is 1.6.33
                    The Grid version is 10.1.8.1.28
                    John Henley
                    Posts: 3353
                    8/14/2012 11:28 AM
                      According to my copy of the Grid 10.1.8.1 installation guide, Life Cycle Manager 9.1.9.0 is still required.
                      Thanks for using the LawsonGuru.com forums!
                      John
                      Gary Padgett
                      Veteran Member
                      Posts: 90
                      Veteran Member
                      8/16/2012 4:08 PM
                        That is true. But the 10.0.1.0 Landmark install guide doesn't require LifeCycleManager. Lawson confirmed that it's not needed.
                        By the way - I had my Java directory defined incorrectly, causing my issues. Finally got it fixed.