If you are planning on changing the LTPA Token on a Sametime Community Server, save yourself a lot of pain by using the existing LTPA Document and keeping the default name “LtpaToken”. You may not get any errors on the console but the SSO using LTPA just won´t work.
If you want to enable Internet Sites on the Community Server, you should read the instructions in the following article:
Different backup strategy/software can lead to the need for changing the Transactional Logging style on a Domino Server. There are basically two possibilities for doing this.
Disable Transactional Logging on a Domino Server.
You should get a message: “Transactional logging being disabled after this restart”.
“NLOGASIO” or “LOGASIO” should not start.
Rename or delete the Transactional Logging directory.
Restart Domino Server to confirm there are no errors.
Enable Transactional Logging and set the Transactional Logging Style option you want.
Restart Domino and again confirm there are no errors on the console.
This is a subtler approach, although this takes a considerate amount of time, you can make sure there are no issues before letting your server back into production. You can also keep the old transactional logs if by renaming the Transactional Logging folder.
On the downside, a consistency check will be run on every database opened, for the first time, and a new DBIID will be assigned. This can take a lot of time depending on the size of your databases.
Change the Transactional Logging style.
Restart the Domino Server.
If you are changing from “Archive” to “Circular”, you can delete or move the old Transactional Logs.
After this, no consistency check or database fixup is will be done and the databases keep their old DBIID.
Here are some useful URLs about Transactional Logging:
I was lucky to visit the #domino2025 Jam in Vienna, this was a pleasant and positive experience. Together with IBM, HCL was also present. We learned a few new things about the future of Domino and about the HCL.
First of all, HCL is a large and stable company with most employees in North America. They have a large revenue and experience in partnerships like this, they worked with Cisco before in a similar partnership. It is clear that this is not Outsourcing but a full partnership.
The development of Domino 10 has already started, and the first package should already be delivered in 2018 Q3. Everything involving Version 10 is called “Project Sapphire” and “Chat” is also part of it. I also like that the HCL does not want to force the customers to cloud.
After we got briefed on the new Partnership and the future of Domino we started brainstorming and presenting ideas for solutions to existing problems and ideas for features we would like to have in long-term. The word “Marketing” was mentioned a few times by every team, marketing was actually discussed most, and all participants wanted it changed from ground up.
All in all, it is clear that a lot is invested in #domino2025 initiative and that it is taken seriously by both IBM and HCL. I think that many good things are going to be produced from the domino jam and I am looking forward to Domino 10.
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:
Rename the “jvm” folder from the Domino “Program” directory. Example: “D:/IBM/Domino/jvm” to “D:/IBM/Domino/jvm_preFP8”
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.
Start the Domino Server.
Are there any issues which you have encountered when updating Domino? Please mention them in comments. 🙂