Event 40966, 41118 Provisioning task fails "Unable to get journal settings from server"

Problem

Lotus Domino Mailbox Provisioning task fails with Event ID 40966 and Event ID 41118, the errors logged are "Unable to get journal settings from server" and "Missing journal database name definition"

Error Message

Lotus Domino Mailbox provisioning task is been aborted logging the errors: 

Type :  Error
Event :  40966
Source :  Enterprise Vault
Category : Lotus Domino Mailbox Provisioning Task
User :  N/A
Computer : EVDG.example.loc
Description:
A program fault has raised an exception.

Exception: Unable to get journal settings from server: CN=evdg/O=example - System.ApplicationException: Missing journal database name definition
   at DomJournalSettings.Get(String sServerName)
   at DomJournalSettings..ctor(DomSession session, String sNAB)
   at DomNAB.GetJournalSettings(S_NAB_RECORD s)
Diagnostic:
Type: DominoLibraryExceptions.DominoLibraryUnableGetJournalSettings
Reference:

Command Line: "C:\Program Files (x86)\Enterprise Vault\EvLotusDominoPolicySyncTask.exe" -URL:tcp://192.168.1.22:1157/5d5e2d70_ab0c_4529_a289_d85e63c49375/KVS.EnterpriseVault.ProcessManager28327059 -CUSTOM:14D8A6052D982A44EBEBDB54079B0532E1012t00evserver1|False||
Application Domain: EvLotusDominoPolicySyncTask.exe
Process Id: 5024
Thread Id: 5820
Stack Trace:    at DomNAB.GetJournalSettings(S_NAB_RECORD s)
   at DomNAB.Initialise(String sServerName, Boolean bLocalDomainOnly)
   at KVS.EnterpriseVault.LotusDomino.Common.NABSession..ctor(String taskEID, String server, String idFile, String passwd, Boolean bLocalDomainOnly)
   at LotusDominoMailboxPolicySyncTask.DominoMailboxPolicySyncTaskProcessor.TaskMain(String[] args)
V-437-40966
 

Type :  Error
Event :  41118
Source :  Enterprise Vault
Category : Lotus Domino Mailbox Provisioning Task
User :  N/A
Computer : EVDG.example.loc
Description:
The Domino Mailbox Provisioning task 'Domino Provisioning Task for EXAMPLE' has been aborted.
V-437-41118

The dtrace of the provisioning task (EvLotusDominoPolicySyncTask.exe) reveals: 

...(EvLotusDominoPolicySyncTask) <5820> EV-M {DOMJOURNALSETTINGS.EN_US} System.ApplicationException: Missing journal database name definition|   at DomJournalSettings.Get(String sServerName)
(EvLotusDominoPolicySyncTask) <5820> EV-L {DOMNOTE.EN_US} Closed note [1552] in DB [evdg/example!!names.nsf]
(EvLotusDominoPolicySyncTask) <5820> EV-L {DOMDATABASE.EN_US} Closed DB [evdg/example!!names.nsf]
(EvLotusDominoPolicySyncTask) <5820> EV-L {DOMNAB.EN_US} DominoLibraryExceptions.DominoLibraryUnableGetJournalSettings: Unable to get journal settings from server: CN=evdg/O=example - System.ApplicationException: Missing journal database name definition|   at DomJournalSettings.Get(String sServerName)|   at DomJournalSettings..ctor(DomSession session, String sNAB)|   at DomNAB.GetJournalSettings(S_NAB_RECORD s)|   at DomNAB.GetJournalSettings(S_NAB_RECORD s)|   at DomNAB.Initialise(String sServerName, Boolean bLocalDomainOnly)
(EvLotusDominoPolicySyncTask) <5820> EV-L {DOMDATABASE.EN_US} Closed DB [evdg/example!!names.nsf]
(EvLotusDominoPolicySyncTask) <5820> EV-M {DOMSESSION.EN_US} Terminating session...
 

Cause

This happens when Domino Journaling is enabled on a Mail Server within the Domino Directory and it does have as Journaling method 'Send to mail-in database' as shown in the following picture:

The provisioning task checks if the Domino Journaling is enabled by reading the 'JrnlEnbld' attribute in the $ServerConfig hidden view from the names.nsf; if Domino Journaling is enabled ('JrnlEnbld' to 1) the provisioning task checks the 'JrnlDBName' attribute which in case of Journaling method to 'Send to mail-in database' remains empty (it uses the 'JrnlDest' instead).

Solution

This issue has been addressed as part of the following release:


Enterprise Vault 9.0.4 - Release Details
http://www.symantec.com/docs/TECH147785

Enterprise Vault 10.0.2 - Release Details
http://www.symantec.com/docs/TECH147789

 

 

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)