IBM Domino Fix Pack Installation – Some Issues and how to fix them

I recently encountered some issues as I was applying Fix Pack 8 to a Domino Server. These are some common issues which can occur at every Fix Pack update, not specific to Fix Pack 8.

Installation fails with an error: “Lotus Notes/Domino or a Notes/Domino related process is still running. Please close it before pressing OK to continue.”

If you get this error, start the Task Manager and make sure that no Domino related processes are running. If you still get this error then stop Windows Instrumentation Service. If that doesn´t help then download Process Explorer. It runs on Windows Server 2008 and newer. With it, you can quickly find out which process is locking Domino Files. Most of the time some Application will lock “nnotes.dll” or “nsd.exe”, that is why I would search for those two files in process explorer first, it will return the name of the application which is locking these files.

WARNING: JVM was not upgraded. Please, see UPGRADE.log and jvmpatcher.log for details.

This problem was not so “critical” with Fix Pack updates prior to FP8, because even if the update of the JVM component failed you could still start a Domino Server. FP8 Version of the Domino Server needs a JVM Version of 1.8 or Java 8 and will refuse to start with an older version of JVM.

You could analyze the logs or reinstall the Domino Server completely (with existing Data), but the fastest solution for this is by far the following:

  1. Rename the “jvm” folder from the Domino “Program” directory. Example: “D:/IBM/Domino/jvm” to “D:/IBM/Domino/jvm_preFP8”
  2. Copy the “jvm” folder from a working Domino Server already running under the version 9.0.1 FP8, to a Domino Server where you had a JVM Issue.
  3. Start the Domino Server.

Are there any issues which you have encountered when updating Domino? Please mention them in comments. 🙂

6 thoughts on “IBM Domino Fix Pack Installation – Some Issues and how to fix them

  1. I highly recommend this approach:
    1. Set Domino Service to Startup Type : Manual
    2. Restart Windows Server.
    3. Do the Domino Upgrade
    4. Set Domino Startup Type to Automatic.
    5. Start the Domino Service.

    Trust me…It will save you lots of troubles…

    Liked by 1 person

  2. I second Rainer and Jesper’s recommendations. I sometimes find nlogasio.exe running after shutting down NSD.exe and nserver.exe. The Windows Management Instrumentation service sometimes respawns after being stopped, so check the status before you begin the Domino installation. When patching Domino, I configure both IBM Diagnostic Services and IBM Domino Server to start manually. I also find that after patching Domino one or both services (NSD and nserver.exe) sometimes will not start if they are to “Automatic (Delayed Start).” They need to be set to Automatic without the delayed start.

    Liked by 1 person

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s