I setup DAOS on my secondary mail server and everything works great.
After testing I attempted to setup on my primary server. When I restarted the server I receive the following error.
“Daosinit error: (259) File does not exist.” on Domino server startup
I checked the Server Doc and the DAOS Base Path is set to c:\Domino\DAOS. I also tried using just DAOS in that field so Domino would try to place the files under the Domino Data folder which is on a different drive.
I checked the Notes.ini to make sure the path was correct.
I have restarted the server several times and also tried using UNC paths.
I called support and the person I got had never seen the error before.
Subject: Re: “Daosinit error: (259) File does not exist.” on Domino server startup
That’s odd…the message there should have some additional detail information on the reason why. Were there any other DAOS messages in the console just prior to that one?
Does the c:\Domino\DAOS directory exist?
Also note that despite the default, best practice is to NOT locate the DAOS base directory in the domino data directory.
Subject: Re: “Daosinit error: (259) File does not exist.” on Domino server startup
No other DAOS messages prior to this one.
I created the c:\Domino\DAOS folder
If I leave the default of DAOS in the DAOS Base Path field I still get the same error.
I prefer to have the DAOS Base on the c drive.
My Domino\data folder resides on a different volume.
Thanks for your response.
I just got off the phone with IBM support and it looks like I’m the first person to ever have this problem. They suggest that I bring down my sever, run offline mantainance, and try again.
Not really sure how that will help domino create the DAOS catalog but I think it buys the support rep some time to figure out what is really going on.
Subject: Re: “Daosinit error: (259) File does not exist.” on Domino server startup
This is with Domino 9.x? Just checking.
The thing that puzzles me is that the error message is supposed to come out with some extra details about where it originated…and that’s not happening.
Please check the permissions on the directory and make sure that whatever account that the Domino server runs as has write access to it. That’s a longshot, but…worth checking.
Also look at the daos.cfg file. It’s an XML file that can be viewed with a text editor. Check the line that talks about CONTAINER_ID and verify that the PATH matches what you have chosen. Since you are just going through the enablement process, if that is wrong, I’d recommend setting the desired PATH value in the server doc (daos tab), shutting down the server, and then renaming the daos.cfg file to daos.cfg.old or something. When the server is started, a new daos.cfg will be created. Note that I’m only recommending this because of where you are in the enablement process…in general it’s a bad idea to delete either the daos.cfg or the daoscat.nsf files.
Is Domino being starting up as a service, or being run as a standalone application? If it’s a service, the environment has some subtle differences and I’ve seen that cause problems. For at least the DAOS first setup phase, please try disabling the service, and running it as a standalone app and see if that helps.