LO40501: PANIC: UNEXPECTED INTERNAL ERROR RETURNED TO LOGGER: 0X20762010

APAR status

• Closed as fixed if next.

Error description

• This is a 3rd-party issue caused when an app locks one of the
  log files via the
  OS instead of using the archive API. When the logger tries to
  open one of the
  files, it gets a locked error back from the OS, and then has no
  choice but to
  panic. Setting allhandles=1 in the nsd.ini (not the notes.ini)
  will provide a
  system-wide process handle dump in the NSD, where it can be
  verified that such
  a 3rd-party app has one or more file handles to the logging
  files.
  
  In the case I saw, it was beremote.exe, which is part of
  Symantec Backup Exec,
  which had a handle to an extent:
  0x0898 0x01120189  File                 879b9888
  \Device\HarddiskVolume3\lotus\domino\data\logdir\S0000005.TXN
  
  Note that this can also manifest itself with an panic message
  that looks like
  this, with no high-bit error code:
   Panic: Unexpected internal error returned to logger: 0x
  2010
  
  
  
  Server crash with Panic: Unexpected internal error returned to
  logger:
  0x20762010
  

Local fix

• recreate the txn file
  

Problem summary

• This problem was resolved as an Enhancement Request.
  

Problem conclusion

Temporary fix

Comments

• This APAR is associated with SPR# TWIG7NJFHY.
  This problem was resolved as: Third Party Software Bug
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• NA
  

Fix information

Applicable component levels

• R802 PSN

     UP