Enterprise Vault processes fail to establish a MAPI logon session to user, journal, or system mailboxes on Exchange. MAPI returns the generic error code 0x8004011d (MAPI_E_FAILONEPROVIDER).
Inspection of the Exchange RPC Client Access logs reveals the underlying exception:
Administrative logon to mailbox '...' is not authorized. The Public Folder Management role group does not grant administrative access to private mailboxes.. Error code = LoginPerm (0x000003F2)
This issue occurs when the Vault Service Account (VSA) is a member of the Public Folder Management Role Based Access Control (RBAC) role group on Exchange Server.
Updated Exchange RBAC authorization checks enforce strict scope boundaries for administrative sessions:
Membership in the Public Folder Management role group explicitly restricts the user's ability to execute administrative MAPI logons (AdminLogon) to private mailboxes.
Even if the VSA has administrative rights assigned elsewhere, the presence of the Public Folder Management role group membership causes Exchange to reject private mailbox logon requests with Error code = LoginPerm (0x000003F2).
Remove the Vault Service Account (VSA) from the Public Folder Management role group in Exchange Management Shell (EMS).
Step-by-Step Resolution:
Open the Exchange Management Shell.
Execute the following cmdlet to remove the VSA from the role group (replace Domain\VSA with your account name):
PowerShell Remove-RoleGroupMember -Identity "Public Folder Management" -Member "Domain\VSA" -Confirm:$false Restart the Enterprise Vault services or the affected Enterprise Vault Task (e.g., Exchange Journaling Task / Exchange Archiving Task).
After upgrading or configuring Microsoft Exchange Server (such as applying Exchange Server Subscription Edition Security Updates 10), Enterprise Vault (EV) Tasks (including Journal & Archiving tasks) fail to access Exchange mailboxes.
Event ID 3419 is logged by Enterprise Vault stating: "Could not access Exchange Server. The dispenser will queue the current item and sleep for 60 seconds." Event ID & Error Symptoms Event Log Entry Plaintext Log Name: Arctera Enterprise Vault Source: Enterprise Vault Date: 9/30/2026 6:42:25 AM Event ID: 3419 Task Category: Journal Task Level: Warning Keywords: Classic User: N/A Computer: xxx.xxx.local Description: Could not access Exchange Server. The dispenser will queue the current item and sleep for 60 seconds. Task: Exchange Journaling Task for xxxxxx
Similar Events
Similar warnings or failures may be observed for the Exchange Archiving Task.
DTrace Log Extract: {AgentMessageDispenser::ActivateObject:#3419} A recoverable [MAPI_E_FAILONEPROVIDER (0x8004011d)] occurred. The process will sleep and re-post the MSMQ msg without incrementing its retry count.
Exchange RPC Client Access Logs 2026-09-30T10:47:30.784Z,18133,1,/o=EnterpriseVault/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=653081b8d98140f19e82556bd20d37d2-EVSysExc,,JournalTask.EXE,16.0.19127.20800,Classic,192.168.1.14,,,ncacn_http,Client=MSExchangeRPC,40342c0d-afe1-4835-9517-cdc3d7c6eb5a|99de3d02-66cf-4f05-8cb7-15cc09e33e14,"""{6570F8D3-2183-405E-89F0-3E7CD0BB63A4} Outlook=16.0.19127.20800 OS=6.2.9200 CPUArchitecture=9""",AdminLogon,1010 (rop::LoginPerm),00:00:00,"Logon: Admin, /o=EnterpriseVault/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=feaf9ed217ea43e4be3080ec5038800f-Journal in database 0d558297-5653-43f0-a3e6-7ee5f5aede9b last mounted on Exchange1.EV.local","RopHandler: Logon: [RopExecutionException] Administrative logon to mailbox '/o=EnterpriseVault/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=feaf9ed217ea43e4be3080ec5038800f-Journal' is not authorized. The Public Folder Management role group does not grant administrative access to private mailboxes.. Error code = LoginPerm (0x000003F2) at M.E.R.H.AdminLogonAuthorizationHelper.AuthorizeMailboxAdminLogon(IExchangePrincipal exchangeMailboxPrincipal, IConnection connection, ClientSecurityContext callerClientSecurityContext)...
Audit RBAC Roles: Review all RBAC role group assignments for the Vault Service Account to ensure it is not assigned conflicting administrative groups such as Public Folder Management.
Verify VSA Permissions: Ensure the VSA retains only the required standard permissions specified in the Enterprise Vault Deployment and Permissions Guide.
Feedback submitted!