Tag: Hotfix

Unable to uninstall Domino 12.0.1 HF

I wanted to upgrade my Windows 2016 Domino 12.0.1 HF18 server to Domino 12.0.1 HF24 today to fix an issue with DAOS.

You need to uninstall any existing HF prior to install a new one. When I start the HF installer to revert the HF 180 installation I get an error message even when I start the executable as administrator.

Sysinternals ProcExplorer does not show any running HCL / Notes/ Domino task. I also set the existing Domino service to “Manual” and restarted the VM.

I can reproduce this behaviour on another installation. Not sure, if this issue only occur when you run Domino in a VM.

The only workaround at the moment is to uninstall Domino keeping all data and settings, restart the computer and reinstall Domino. Now you can apply the HF.

UPDATE / SOLUTION

Found the solution here https://blog.nashcom.de/nashcomblog.nsf/dx/solution-for-notesdomino-related-process-is-still-running-when-applying-a-fixpack-or-hotfix.htm?opendocument&comments

Stop the WMI services. Now you can uninstall / install the HFs


New Replica Crashes Domino 8.0.1 (64 Bit)

When creating a new replica from another server on a Domino 8.0.1 (64 Bit) on Windows 2003 (64 Bit), the server crashes and you will find these lines in your NSD file:

############################################################
### FATAL THREAD 54/73 [ nSERVER: 0138: 09a4]
### FP=0x1080C9342, PC=0x014fb0a8, SP=0x1a92bcd0
### stkbase=1a930000, total stksize=4194304, used stksize=17200
### EAX=0x1080C931C, EBX=0x00000000, ECX=0x080c9342, EDX=0x080c9344
### ESI=0x080c9342, EDI=0x1a92f2d8, CS=0x00000033, SS=0x0000002b
### DS=0x0000002b, ES=0x0000002b, FS=0x00000053, GS=0x0000002b
Flags=0x00010293
Exception code: c0000005 (ACCESS_VIOLATION)
############################################################
@[ 1] 0x014fb0a8 nnotes.Cmovmem+656 (1a92f2d8,4f0101,0,159b400)”

This seems to be similar to SPR RMAA7D9HAP. The Knowledgebase says that this will be fixed in 8.0.2.
I informed IBM and they promised to provide a hotfix to solve this issue.

Update: Received hotfix today. Problem solved!