Transaction Logging error: "Cannot write to log file: Recovery Manager: Log File is Full, try again later"

We have experienced several server crashes due to this error. The servers are setup with Circular TA logging with the maximum extent file size of 4GB. The drive is a separate logical drive from the Domino server partition and the available space is 68GB total. When TA logging is disabled the server runs great, but when the TA logging extent files are removed and TA logging is re-enabled the server crashes immediately with the extents totalling 4GB.

We are working with IBM/Lotus support without success.

Has anyone experienced the same problem?

Subject: Try removing the following lines from the servers Notes.INI file before re-enabling.

TRANSLOG_AutoFixup=1TRANSLOG_UseAll=1

TRANSLOG_Style=0

TRANSLOG_Performance=2

TRANSLOG_Path=f:\

TRANSLOG_Status=1

Subject: RE: Try removing the following lines from the servers Notes.INI file before re-enabling.

We discovered that due to some unexplainable reason the nserver.exe executable went corrupt. IBM has taken all log files for investigation. For future problems it has been recommended that we disable TA logging, perform a full backup of the txn files and manually delete after. Re-enable, restore the newest txn file and add TRANSLOG_RECREATE_LOGCTRL=1 to the notes.ini to allow the restore ability of the past transactions of the server. Thanks for your help.

Subject: Have you tried a Linear logging style instead of Circular?

Besides, that’ll let you use the full 68GB of space.