This is probably not a problem with FP8, to be upfront, but just in case I am using it for the title.
4 out of 8 servers at a customer did not chaaange tehir version number when I updated them to FP8.
They stayed FP7.
In the past, I have had this issue where updates don't happen, due to various reasons like a corrupted NAB, failed hot fix removals, etc..
But this was different because 4 servers, DEV domain, were fine.
QUAL domain is not updated.
How Did I Get Here
Servers were 12.0.2 FP7 HF1 Windoews 2019
I shut the Domino server down, including the Domino service.
Paused the Windows Management service(ONLY affects HF's for some reason), then ran the hot fix as administrator to remove it.
Started the server from the icon asd a regular application, so I can see it running, and a "sh ser" showed the correct FP7 version. Let it run for a few minutes till I saw HTTP start and some other tasks. Then shut it down.
Run FP8 as an administrator, runs fine, no errors.
Restart the box, actually, 2 servers had issues with the Domino service login, and I restarted the whole VM, the other 2 the service started fine.
Waited to see the server docs change, and nothing.
The upgrade.log showed everything looked ok.
I opened a ticket with HCL after the 1st 4 failed to update, then I checked the next 4 and those worked.
The Resolution and Reasoning
Sooraj from HCL Support provided me with the following resolution and an explanation after I provided some files and screenshots.
Take a backup of the files below and replace them from a "working" server [12.0.2FP8]
Domino\nstrings.dll
Domino\res\C\nstrings.res
Shutdown the incorrect Domino server
Take a backup of the two files mentioned above.
Copy similar files from a working 1202FP8 server and replace them.
(I left the existing ones, and added a _BAD at the end of the name)
Start the Domino server.
While I asked to close the ticket, I also wanted an explanation for future thoughts.
Sooraj provided the following:
This problem was reported for the first time, and based on my analysis, it appears that those two files were not updated by the FP8 installer. It was still using the FP7 code. This ideally occurs due to an access issue with the account that started the installation, but unfortunately, I cannot confirm this because the upgrade.log doesn't show any such errors.
Possibly a server processing issue, a delay, or perhaps not fully completing a virus scan, or some other local issue was to blame.
But on 4 servers, I don't believe so.
One, sure, things happen.
In this situation, all 4, well, 8, are nearly identical setups.
Hope this helps others with similar issues at some time in their admin journeys.
