ClassFactory cannot supply requested class 0x80040111
Article ID: 100052541
Updated On:
Description
Error Message
A Dtrace of the relevant archiving task process (JournalTask, ArchiveTask) may contain the extracts below:
{CMailboxHelper::CreateProfileAndSessionAndOpenMailbox:#1237} Failed to open mailbox
{CMailboxHelper::CreateProfileAndSessionAndOpenMailbox:#1238} Error being returned : 0x80040111
{CMAPISession::CreateMapiSession} (Exit) Status: [ClassFactory cannot supply requested class (0x80040111)]
{CMAPISession::GetMapiSessionFromPoolEx} (Exit) Status: [ClassFactory cannot supply requested class (0x80040111)]
{CAgentTask::Initialise:#1347} Failed to open privileged MAPI session: [0x80040111]. Aborting agent startup.
Cause
The issue is attributed to Internet Explorer on the EV server not being registered properly.
It can also be caused when a load balancer is used, such as NetScaler, and higher level Exchange servers have been added to the environment.
Resolution
Launch a command prompt as an Administrator & run commands below:
regsvr32 ieproxy.dll
regsvr32 actxprxy.dll
Reboot the EV server.
Notes:
1. The ieproxy.dll file should be located under folders with their names and paths beginning with C:\Windows\WinSxS\x86_microsoft-windows-ie-ieproxy_... on the server. For example:
C:\Windows\WinSxS\x86_microsoft-windows-ie-ieproxy_31bf3856ad364e35_11.0.14393.447_none_b1a25e47599060cc
2. The actxprxy.dll file should be located under folders with their names and paths beginning with C:\Windows\WinSxS\x86_microsoft-windows-activexproxy_... on the server. For example:
C:\Windows\WinSxS\wow64_microsoft-windows-activexproxy_31bf3856ad364e35_10.0.14393.0_none_49d7493d355dbcf8
3. These paths are not typically part of the Path environment configuration. As such, it may be necessary to search for and locate the path to these files in order to use them in the commands.
NetScaler
Ensure the lower version Exchange servers are disabled in the NetScaler so that all traffic is sent to the higher version. For example: Exchange will re-route the request for a 2016 mailbox when connecting to a 2019 server. However, it cannot re-route the request for a 2019 mailbox when connecting to a 2016 server.
Issue/Introduction
