SOLVED: Help with installation of MSM (17.05.06.00_MSM_Windows) - Java issues
- Thread starter SecCon
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Thanks for reminding me. Java has released an update since I wrote this, but unless you really need to update Java, that update can be ignored to keep MSM running.
Having said that, you may have security related reasons to update Java, then please go ahead and do so, by all means, but please let us know if anything breaks so we can do some troubleshooting.
On the other hand you might get an error, like I did.
Error Code 1603: Java Update did not complete.
I do not intend to follow those instructions.
MSM still runs ok after that update attempt.
Having said that, you may have security related reasons to update Java, then please go ahead and do so, by all means, but please let us know if anything breaks so we can do some troubleshooting.
On the other hand you might get an error, like I did.
Error Code 1603: Java Update did not complete.
I do not intend to follow those instructions.
MSM still runs ok after that update attempt.
Last edited:
First thank you very much, I also joined because of you. However, this did not work for me exactly.
I had to drop the javax.activation.services file into path (C:\jre\jdk8u282-b08-jre\bin) before my host would appear.
I downloaded the i586/x86 version of jdk8u371 from https://www.oracle.com/java/technologies/downloads/#java8-windows and also had to uninstall all previous installs of jre and jdk as well as remove all old orphaned java.exe, javaw.exe and javaws.exe files from c:\system32, C:\syswow64 and the entire C:\programdata\oracle folder before installing the new installation of jdk.
After that worked without flaw, and was able to flash new firmware to prep for a drive replacement. You rock!
It seems to me you did not read everything, since I specified the system should be clean of Java before doing this, unless you know what you are doing. I also suggested an alternative installation path, where you seem to have gone with the default installation option, that is why you had to copy the javax.activation file to where you mention. I chose another path/folder to show how MSM depends on the environment variable path and where you put the javax.activation file.
You could have kept the java files, as long as you defined the environment variable path and put the javax.activation file, to the same folder, and did not have two conflicting environment variable path definitions.
Nevertheless I am happy it worked out for you.
You could have kept the java files, as long as you defined the environment variable path and put the javax.activation file, to the same folder, and did not have two conflicting environment variable path definitions.
Nevertheless I am happy it worked out for you.
I uninstalled. Those files were orphaned.
First I installed the javax.activation to C:\jre\bin, that did not work. My environment variable path is correctly set to C:\jre.
Upon creating C:\jre\jdk8u282-b08-jre\bin, and placing javax.activation inside. The server started functioning normally.
First I installed the javax.activation to C:\jre\bin, that did not work. My environment variable path is correctly set to C:\jre.
Upon creating C:\jre\jdk8u282-b08-jre\bin, and placing javax.activation inside. The server started functioning normally.
I tried upgrading my MSM, too, to the latest available on downloads (17.05.06.00, I believe).
Hit across the same Java issues, tried all kinds of runtimes, to no avail, even when I matched it to the exact same release mentioned in the release notes.
In the end I went back to the last release in my archives, which had the JRE included and that was the 17.05.00.02 from 2018.
That just worked.
I think software quality control went though a bad patch with all these aquisitions.
Hit across the same Java issues, tried all kinds of runtimes, to no avail, even when I matched it to the exact same release mentioned in the release notes.
In the end I went back to the last release in my archives, which had the JRE included and that was the 17.05.00.02 from 2018.
That just worked.
I think software quality control went though a bad patch with all these aquisitions.
I just think they don't care anymore. They likely had improvements scheduled or completed when the decision to discontinue these cards came down from the top and they probably were told to push what they had, archive it all as legacy, and prepare for onboarding to the new new. I've been thinking they just pulled all the files down for years until I got an inkling to search "where'd the updates go" which is how I found this thread and was pleasantly surprised that I was missing a firmware, driver and MSM update.. so it's not all bad I guess. Though my Dell certified WD4001FYYGs have gotten so amazingly cheap since first buying this controller, it's going to be so great when enterprise NVRAM drives come out and NVRAM RAID gets better support.
Of course they don't care. What do you expect? 10 year warranty and 25 years FW support? They don't make money on us, nor do we foment further product updates and development. That comes from bigger corporate customers who mostly want newer shinier stuff.
We, at least I, are only home or small office people trying to do this as cheap as possible.
We, at least I, are only home or small office people trying to do this as cheap as possible.
Hi and thanks
As I wrote above the Java update failed, but again, it depends on how you use the machine where you have this installed. If it is exposed you may want to update Java and keep Java updated and I guess the easiest solution MIGHT be to uninstall MSM and Java, and do the process all over again, BUT, using the latest release of the i586 32-bit java instead of the one I used.
I have not dug in to why an update failed, it could be due to different installation directories from what I used in my guide. I really do not know at this time.
The important thing is that you have something that works to come back to, and if you like to fiddle with later versions of Java for any reason, feel free to do so, and post here about it.
However, I do not expect MSM to work better or differently with later versions of Java though so to me, that is not something I might dig in to any time soon.
As I wrote above the Java update failed, but again, it depends on how you use the machine where you have this installed. If it is exposed you may want to update Java and keep Java updated and I guess the easiest solution MIGHT be to uninstall MSM and Java, and do the process all over again, BUT, using the latest release of the i586 32-bit java instead of the one I used.
I have not dug in to why an update failed, it could be due to different installation directories from what I used in my guide. I really do not know at this time.
The important thing is that you have something that works to come back to, and if you like to fiddle with later versions of Java for any reason, feel free to do so, and post here about it.
However, I do not expect MSM to work better or differently with later versions of Java though so to me, that is not something I might dig in to any time soon.
Last edited:
Interesting thread.
I run a MegaRaid 9361-8i SAS-SATA3 storage controller in my home workstation. And I've enjoyed MSM and had upgraded to this 17.05.06.00 version, and then I had problems.
I did a reinstall of WIndows 10 and recovery of files this past week to refresh the system, and installed the latest 64bit Oracle-Sun java jre 8. I was able to put in the JRE_HOME variable, using the "open jdk directory" name in the MSM release notes: "jdk8u282-b08-jre ".
What I ended up doing was creating that name under C:\jre\ as a symbolic link to my Oracle java directory.
It worked- somewhat. It fired up MSM fine. But I could not discover a server. In the past this kind of error had been resolved with deinstalling, reinstalling MSM and/or playing with the Windows Defender firewall. However, I suspected that actually pointing to real Oracle-Sun java impeded functionality.
I could swear MSM always had worked with Oracle-Sun java in it C:\Program Files\java directory.
And finding this release-note-endorsed open jdk was a pain in the ass.
I installed the LSI storage authority local webserver/browser solution. Fantastic. Much better. I liked the UI.
Perhaps for curiosity, I'll try SecCon's pictorial steps above with java and MSM install, and see if that discovers and works,
However, the LSI Storage Authority looks and works fine.
I run a MegaRaid 9361-8i SAS-SATA3 storage controller in my home workstation. And I've enjoyed MSM and had upgraded to this 17.05.06.00 version, and then I had problems.
I did a reinstall of WIndows 10 and recovery of files this past week to refresh the system, and installed the latest 64bit Oracle-Sun java jre 8. I was able to put in the JRE_HOME variable, using the "open jdk directory" name in the MSM release notes: "jdk8u282-b08-jre ".
What I ended up doing was creating that name under C:\jre\ as a symbolic link to my Oracle java directory.
It worked- somewhat. It fired up MSM fine. But I could not discover a server. In the past this kind of error had been resolved with deinstalling, reinstalling MSM and/or playing with the Windows Defender firewall. However, I suspected that actually pointing to real Oracle-Sun java impeded functionality.
I could swear MSM always had worked with Oracle-Sun java in it C:\Program Files\java directory.
And finding this release-note-endorsed open jdk was a pain in the ass.
I installed the LSI storage authority local webserver/browser solution. Fantastic. Much better. I liked the UI.
Perhaps for curiosity, I'll try SecCon's pictorial steps above with java and MSM install, and see if that discovers and works,
However, the LSI Storage Authority looks and works fine.
Last edited:
I've been a long-time user of MSM but I haven't used it it a while since shelving all of my boxes with LSI 9260-8i's. I decided to repurpose one of my boxes but I could not get MSM to discover the server (self). I followed the instructions in the "readMe" and in this thread but just like @basskleff, I had to switch to LSI Storage Authority. It installed and works great. Just takes a little getting used to.
I had trouble finding the latest version of LSA for Windows. Here's a link to it: https://docs.broadcom.com/docs-and-downloads/008.006.010.000_LSA_Windows.zip
I had trouble finding the latest version of LSA for Windows. Here's a link to it: https://docs.broadcom.com/docs-and-downloads/008.006.010.000_LSA_Windows.zip
Sometimes the simplest way is best.
Unless there is an overpowering reason to need MSM version 17.05.06.00, just install MSM version 17.05.01.02.
MSM version 17.05.01.02 works with W10 and W11 and virtually any Java version from the last 2 -3 years without problems or a need for workarounds.
Download (lenovo.com)
Unless there is an overpowering reason to need MSM version 17.05.06.00, just install MSM version 17.05.01.02.
MSM version 17.05.01.02 works with W10 and W11 and virtually any Java version from the last 2 -3 years without problems or a need for workarounds.
Download (lenovo.com)
Mate, tks a million. I too registered just to thank you for taking the time to post such a detailed solution.