Problem
Occasionally (typically after a server crash or backup application problem), archive-style transaction logs (.txn files) are not deleted or reused on a Lotus® Domino® server. How can these be cleaned up?

Solution
Important note: The procedure below is safe for Domino, but does not take into account the state of existing database backups.
A full backup should be performed before taking this action.
All database DBIID’s will be changed. Consult your backup application documentation for the ramifications of changing DBIID’s.

• Disable transaction logging for this server. This is done by:
  Open the server’s Domino directory (names.nsf).
  Locate this server’s Server document.
  Edit the Server document -> Transactional Logging tab ->
  Basics section.
  Change the "Transactional logging" field to Disabled.
• Stop the Domino server and confirm that all Domino tasks have shut down by checking the Windows Task Manager.
• Start the Domino server and observe the message, "Transactional logging being disabled after this restart". Also notice that NLOGASIO (the task Domino uses for transaction logging) does not load and is not in the Task Manager list.
• From the operating system (OS), rename the transaction log directory. There should be no errors when doing this, as Domino is not using any of the files in the log directory any more.
• Stop the Domino server and confirm that all Domino tasks have shut down by checking the Windows Task Manager.
• Start the Domino server.
• Edit the Server document again and set the "Transactional logging" field back to Enabled. Save the Server document.
• Stop the Domino server and confirm that all Domino tasks have shut down by checking the Windows Task Manager.
• Start the Domino server and observe the message, "Please wait, creating new transaction logs in directory…"
•   Notice that a consistency check is run on any open databases and a new DBIID is assigned. This occurs on each database as it is opened.
•   Delete the old log directory (previously renamed).