6 Replies Latest reply on Dec 4, 2015 10:30 AM by shawnhopkins

    LEM Client Installation - Java Error

    shawnhopkins

      When running the LEM client installer, InstallAnywhere gets to 100% then we get the following error message:

       

      "Java(TM) Platform SE binary has stopped working..."

       

      InstallAnywhere launches a version of Java in memory called javaw.exe. A version of Java is not needed since InstallAnywhere uses it's own.

       

      I can get past the error on my computer, but not on the set of computers we are trying to install the LEM client on.

       

      - I've tried disabling the Windows Firewall and Anti Virus

      - I've logged in as the built-in Administrator account

      - I've right-clicked on the .exe and chosen "Run As Adminstrator"

      - I've successfully installed the client on my Desktop using the same install files.

       

      I believe the installer is error-ing out right before the Solarwinds splash screen. When it tries to load the screen using javaw.exe, is when we get the Java error message.

       

      Any thought or ideas I haven't tried?

       

      Windows 7 Embedded

       

      Thanks!

        • Re: LEM Client Installation - Java Error
          superfly99

          I don't have LEM so I can't offer any help but you should really move this to the LEM forum. Hopefully more people will see it there.

           

          Log & Event Manager

          • Re: LEM Client Installation - Java Error
            curtisi

            Is there anything in the Windows Event logs when you install to shed some light on what's happening?

            • Re: LEM Client Installation - Java Error
              shawnhopkins

              Ok I think I figured out the problem.

               

              There was one entry in the log file for "Faulting application javaw.exe"

               

              Faulting application path: c:\users\[username]\AppData\Local\Temp\l14480385\resource\jre\bin\javaw.exe

              Faulting module path: unknown

               

              The installer creates a new temp folder each time it's executed so the number above in the path can be anything.

               

              I verified that the install folder was created in Temp and that javaw.exe existed.

               

              Each time I ran the installer, right before the splash screen loads I would get a "Java(TM) Platform SE binary has stopped working..."

               

              So I cleared out the contents of the Temp folder, rebooted, and the installation worked, loading the splash screen.

               

              There are a lot of web installers that user javaw.exe and leave remnants in the Temp folder.

               

              I'm guessing that when you have multiple instances of javaw.exe in your temp folder, InstallAnywhere has a problem with that.

                • Re: LEM Client Installation - Java Error
                  shawnhopkins

                  Ok the saga continues. So on some recent installs even clearing the temp files did not resolve the problem. LEM was still crashing with a Java Platform has stopped responding message.

                   

                  The OS is Windows7 POS Ready on an NCR P1530 cash terminal. Now we were updating software through a web browser enabled remote session and I had thought maybe the web browser was interfering. So I tried the LEM installation in person and it still failed. Basically crashing before the Solarwinds Setup Screen.

                   

                  The item updates we were performing on the cash terminals were Trend Deep Security update, modified hosts file, BIOS update, and LEM installation.

                   

                  I thought maybe AV but in prior attempts, even with no AV, the LEM install still crashed.

                   

                  Faulting application path: c:\users\[username]\AppData\Local\Temp\l14480385\resource\jre\bin\javaw.exe

                  Faulting module path: unknown

                   

                  Well today it was failing on a set of cash terminals but then all of a sudden the installation worked. I'm standing there literally scratching my head trying to figure out what I did.

                   

                  Suddenly it dawned on me that in the previous installations we did the BIOS update first, but in recent installs we did it last.

                   

                  So we never tried the LEM installation after a BIOS update.

                   

                  I had started updating the BIOS on these terminals for a different problem which was they would not boot off of a USB media and also with a backup USB modem attached, sometimes they would not boot at all. We ended up turning off USB Legacy support in the BIOS; until we could find the cause; which later I discovered a BIOS update fixed the problems.

                   

                  Really ticked me off a few months ago to learn that these NCR P1530 cash terminals that we got, never had a BIOS updated from our vendor.

                   

                  We went back to a few systems where the LEM installer originally failed. We tried LEM setup and; after confirming the BIOS had been updated, setup worked fine without clearing the temp files.

                   

                  So not sure how the BIOS could effect an installer; unless the Solarwinds setup screen is trying to read something from the USB controller.

                   

                  But just to summarize, after running setup, the progress bar goes to 100% and right before the LEM setup screen is displayed, a Java Platform Error occurs with event log:

                   

                  Faulting application path: c:\users\[username]\AppData\Local\Temp\l14480385\resource\jre\bin\javaw.exe

                  Faulting module path: unknown

                   

                  Installing a BIOS update at least for an NCR P1530 terminal resolves the problem.