Check the following list for possible causes and potential solutions for this message.

• If the server is running antivirus software, the .NLO file may have been removed by that software. Set the server's antivirus software to exempt folders used by DAOS, and restore the missing file from backup.
• The storage location specified for .NLO files is inaccessible. There may be a temporary power outage, powered-off external drive, lost network connection, or similar problem with the machine or device. Check the availability of the device specified for storing DAOS files, and that the specification for it is correct in the Domino Server document. Then restart the Domino server.
• The .NLO file is corrupted. Restore it from backup and complete the DAOS operation.
• The .NLO file was copied from another server through the operating system, and had been encrypted on the other server, so its encryption key is unrecognizable on the current server.

1. Identify the database(s) that reference the file.

2. To remove the document that contains the ticket for the unreadable .NLO file, on the database(S) containing the document, run

fixup j -d

3. To remove the invalid .NLO from the catalog file's list, run Tell DAOSMgr Resync.
Tip: Depending on the number of DAOS references, the Resync command may take time to complete, and is best run at a time when the server is not in active use to avoid compromising performance.

4. Restore the document to the database(s) by replicating from another server.

Related topics

Attachment consolidation (DAOS) -- Troubleshooting

Glossary