I have massive problems with DAOS.DAOS was enabled in the Server document along with transaction logging.
DAOS and Translog files are separated in different partitions and separated from domino data.
After reboot the server is running smoothly. But when I activate DAOS in a mail database the server crashes after delivering the first message with an attachment to this DB.
The server console regularly show the message: “The DAOS catalog cannot be created. DAOS cannot operate normally.: Database is currently in use by you or another user.”
I recreate the DAOS catalog several times and re-synchronize, but without success (was also the only clue I could research).
On OS-level UAC has been disabled.
Another problem is, that the Domino Diagnostic Service is not startable - so I have no nsd file to analyze.
Server: W2K8 Enterprise R2 64 bit FP1, Lotus Domino 8.5.2 FP2 (LP German), 32-bit with Sametime Entry 8.5.1 and 8.5.2.2 Traveler.
Does anyone have an idea?
Subject: Hi…check these
This message occurs when Domino cannot access DAOSCAT.NSF, the catalog file it uses to track DAOS references (tickets) and .NSF files (ticket holders). Opening this catalog file is required for DAOS to verify or update .NLO file information, so this error causes DAOS to be disabled on the Domino server. An additional message such as “Disk Not Ready” may provide information on why the catalog could not be opened.
Try the following approaches to allow Domino to open the catalog file.
The server may not have appropriate access to the catalog file in the Domino data directory. Change the access control on the Domino data directory so that the Domino server can open files, and then restart the server.
The Domino data directory may be on a machine or device that is experiencing problems such as hardware failure, network failure (if using a networked or NAS device) or any other similar problem. Check the system logs to see if there are any logged events related to problems with the device. Correct any issues, and then restart the server.
If neither of the conditions above exist, you can cause Domino to recreate a fresh catalog database.
Stop the Domino server.
Create a backup copy of the DAOSCAT.NSF to send to IBM Technical Support.
Delete the catalog file.
Restart the server.
After Domino has recreated the catalog, use the Tell DAOSMgr Resync command to re-synchronize DAOS references.
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.
Subject: Problem with DAOS
After reinstallation of the Domino Server into the default location c:\program files (x86)\ibm\lotus\domino (before: c:\program files\lotus\domino) the diagnostic service starts without problems.
The server crashed several times with STUserInfo as the fatal thread.
The following IBM APAR describes the cause of crash: LO56145: STUSERINFO PROCESS CAUSES DAOS TO PANIC IN IT'S TERMINATION CODE.
Now we deactivated STUserInfo in the Windows Services and since then the server is running stabile with Sametime and DAOS.
Does anybody know, if this problem is fixed in Sametime 8.5.2?
Cheers
Christian
Subject: Also solved in Domino 8.5.2 FP3
SPR# MIAS8AVREL - Fixed a Crash issue within DAOS, where STUserInfo process causes DAOS to Panic in it’s termination code.