This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


Nov 20, 2013, 9:41 PM
4 Posts

Re: "Daosinit error: (259) File does not exist." on Domino server startup

  • Category: Domino Server
  • Platform: Windows
  • Release: 9.0
  • Role: Administrator
  • Tags:
  • Replies: 8

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.

Nov 21, 2013, 6:24 PM
12 Posts
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.

This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal