Without logs(EMC evt, ExArchiveJBC with trace verbosity 4 and ExSyncService with trace verbosity 4) it will be hard to understand the series of events that lead to the problem you are facing. I suggested to increase the log verbosity for the above mentioned logs, recreate the problem and collect all three logs. I suggest you open a support case and attached the collected logs.

Thanks for your answer.

How can I change the verbosity of the logs file ?

Thanks

Amaury

if you are on windows 2008 64 bit - registry location to change log verbosity - HKLM\Software\WOW6432Node\EMC\SourceOne\Tracelogs\ \Settings\TraceVerbosity

if on windows 2003 - registry location to change log verbosity- HKLM\Software\EMC\SourceOne\Tracelogs\ \Settings\TraceVerbosity

Master server role will have - ExSyncService.exe log

Worker server role will have - ExArchiveJBC.exe.log

Collect EMC evt from both the machines. If all the roles are installed on same machine then collect ExSyncService, ExArchiveJBC and EMC evt log from the same machine.

Thanks for this information.

I can not explain why but after a repair of the Master software with re specify of the Notes ID, the solution works fine and archive mail and nsf file.

I'm not sure it's the solution that we can done on alle the site but in my case, it will correct my problem

Thanks very much for your help

Amaury

It must be some sort of problem with NotesID after the master server install. i-e if someone installed ONMViewer, or if someone changed credentials for the NotesID. In such cases repair is not a bad solution to the problem.