Zenworks suite upgrade from 11.4.0 to 2017

We are upgrading and are stuck with this error loading zman.  Error: A JNI error has occurred, please check your installation and try again.  Exception in thread "main" java.lang.UnsupportedClassVersionError: com/novell/zenworks/zman/ZManLoader : Unsupported major.minor version 52.0

The database has upgraded and it appears the runtime environment has updated but the zenworks server has not.  So stuck partially in limbo.  Any ideas would be appreciated.

 

Top Replies

  • In General it is this.....

    https://javarevisited.blogspot.com/2015/05/fixing-unsupported-majorminor-version.html

    It sounds as if Java did not update.....Perhaps there is another Java Version in the Path taking precedence.

    What OS is the Primary Server?

    --

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • The server OS is Windows Server 2016. The current version of Zen 11.4 has been running on there until we tried to update. Will take a look at the TID you sent. Thanks so much.
  • https://support.microfocus.com/kb/doc.php?id=3418069

    Log Location:
    Windows:
    %ZENWORKS_HOME%\logs\system-update\<update GUID>\system-update.log and all msi logs
    %ZENWORKS_HOME%\logs\LocalStore\zmd-messages.log
    %ZENWORKS_HOME%\logs\loader-messages.log
     
    You need to review the logs above....
    System-Update.log will give a high level view of each MSI.........
    Perhaps Post that here.
     
    Individual MSIs logs may help indicate that failed.
    You could try re-installing any particular MSI if you know it failed.
    Maybe if it was JUST Java then it would not be too bad.
     
    IMPORTANT...The Logs will indicate COMMAND-LINE Parameters with the MSIs.  Adding a value for "TargetDir" per what is used in the logs may help.
     
    Perhaps running an "MSI Repair" may help.
    Again, the logs point to Java Version issues, but there could be ALOT more wrong or maybe your lucky day and nothing else is wrong.
     
    Also Check the Windows Path, make sure there are not any other "Java" versions in the path that are ahead of ZENworks or no unusual JAVA Environment variables pointing to other java stuff.  I can't RECALL any case where ZCMs Java was trumped in Windows, but just trying to troubleshoot in broadstokes.  (Note: I did see such cases years ago on Linux with OES, but that was in the early ZCM 10.x days when ZCM shared java with the OS on Linux.)

     

    --

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • "%ZENWORKS_HOME%\share\java\bin\java" -version

    --

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • I neglected to say we did update the Java version on the server before we posted but that did not seem to help.
    These are the system logs from the days we worked on it. As you can see we have been poking away at this for a while. I will spend some time tonight going through them and the msi logs. On 8/8 there were only the high level msi logs but on the two folders dated 8/11 there are 170 logs.
  • Is Java Listed in Add/Remove Programs?  Why?

    ZCM Ships with it's own Java.  It is not supposed to use the OS Java. Removing that may help.  The only java that should be on the system is the Java in the %ZENworks_Home% that is installed from the ISO/Upgrade.

    --

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • And to be clear...only remove it's is some Java install that did not come with ZCM.

    --

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • Removed the Java 8 install that we added.  Will update on the rest.  Thanks for all your help.

  • Hi Craig, 

    Sorry it took so long to get back to you.  We apparently just had a very broken installation.  Don't think any fix would have worked.  We tried setting up 2017 same installation on a virtual machine with no issue.  We ended up opening a service request with MicroFocus and working with Paul Pedron.  Unable to repair the original installation he moved our database over to the virtual machine using disaster recovery.  It was a long process but we are up and running.  Paul was great to work with and we are preparing to move on to 2020 now that our issues are resolved.  

    I appreciate all the information you provided and all your attempts to help.

    Thanks, Bobbie