Invalid attachment with DAOS

HCL Domino Domino Forum
1

Hi,

we enabling/compacting some databases for DAOS,

after this we get this error message when trying

to open some attachments:

The database /notes/data/mail/database.nsf was unable to open or read the file Document attachment is invalid

When disabling DAOS compacting the databases, the same attachments can be opened again.

Anyone know this issue?

Cheers Robert

2

Subject: need info

What build are you running (from SHOW SERVER console command)

Please send results of this command

sh stat daos.engine.*

3

Subject: also

…what version and build of Domino are you using, and on what platform?

4

Subject: invalid attachment with DAOS

Hi Guys,

here the infos:

Lotus Domino (r) Server (Release 8.5FP1 for UNIX) 04/09/2009 14:14:20

DAOS.Engine.Catalog = Synchronized

DAOS.Engine.Encryption = Enabled

DAOS.Engine.Status = Enabled

3 statistics found

Cheers Robert

5

Subject: more info

here is the message, which occurs in the event database when trying to access an attachment:The database /notes/data/mail/rjung.nsf was unable to open or read the file Document attachment is invalid

I also found a message which occurs once a day:

Unable to add entry to catalog (for daoscat.nsf): Special database object cannot be located

Maybe this infos are helpfull.

Best regards Robert

6

Subject: Try Restarting Domino…

I had this same issue a while back and a server restart fixed it.

Steve

7

Subject: helps but

restart Domino and deleting the two daos fileshelps but after some days the problems occur again

8

Subject: same problem - any solution?

Hi!

We have the same problem

“unable to open or read the file Document attachment is invalid”

  • 151 mail databases are daos enabled and 2 other applications.

  • on 2 servers in a domino cluster.

  • both servers are in W2K3 64 bit with Domino 8.5 FP1

daosmgr status:

server1 = synchronized

server2 = NEEDS RESYNC

attachment is missing on both servers.

No missing NLO files.

And “resync” on server2 doesn’t fix the problem.

Any ideas? Any solutions? where will be the problem?

Best regards

Michael

9

Subject: no sry

the solution for us was disabling DAOS…i will try it again the upgrading our server to 8.5.1

as temporary fix we stopped our server, deleted the 2 daos files, restartes the server and resynced DAOS