Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Archiving and eDiscovery Community Blog

EVPM fails with 0x8004011D

Created: 11 Jul 2011 • Updated: 29 May 2014 • 1 comment
Rob.Wilcox's picture
0 0 Votes
Login to vote

 

I’ve seen a few people have issues with Enterprise Vault Policy Manager (EVPM) recently.  Each time there has been a failure with the error code 0x8004011D.  It’s not a very helpful error code, even when you see the explanation :

# for hex 0x8004011d / decimal -2147221219 :
  MAPI_E_FAILONEPROVIDER                                        mapicode.h
# 1 matches found for "0x8004011D"

I’ve seen this caused by at least the following three issues :

* In my own repro environment where I have the Exchange 2003 Server and the Domain Controller / Global Catalog on the same machine, the issue is present.  I’m not sure of the *cause* but the cure is to specify the SMTP address of the system mailbox, rather than the alias. 

That’s an odd solution, I know, but it worked immediately.

 

* In another of my repro environments, with a slightly different setup, but essentially the same way of Exchange 2003, it was solved by specifying the NETBIOS name of the Exchange Server rather than the FQDN

 

* In yet another environment, this time for a customer, and discussed on our forums the issue was that the customer was using the name of a CAS, in their Exchange 2010 environment. 

I guess that they had gotten used to the idea of specifying a CAS, as client access, including Outlook is done through that role in Exchange 2010.  For EVPM though, it has to be the mailbox server.

 

This last example was fathomed out by one of Dev Managers (Hi Karl W), and he looked at the DTRACE.  DTRACE of EVPM is possible, and is usually quite short, and helpful.  Here is what a failure looked like in the above example :

16    16:20:02.296     [6352]    (EVPM)    <11812>    EV:L    Processing Exchange tasks.
17    16:20:02.296     [6352]    (EVPM)    <11812>    EV:L    ProcessExchangeTasks: Entry
18    16:20:02.358     [6352]    (EVPM)    <11812>    EV:M    CMailbox::CreateManagementSession - Input[CASSRV1.somedomain.local], ExchangeServer[CASSRV1], DomainName[somedomain.local]
19    16:20:02.358     [6352]    (EVPM)    <11812>    EV:M    CMAPISession::GetMapiSessionFromPoolEx(AdditionalFlags = 0)
20    16:20:02.358     [6352]    (EVPM)    <11812>    EV:M    CMAPISession::CreateMapiSession - Entering Routine
21    16:20:02.608     [6352]    (EVPM)    <11812>    EV:M    CMAPISession::CreateMapiSession - Calling CreateProfileAndSessionEx

You can see what was passed as input, on line 18.

(Note: In this particular case the 0x8004011D was logged per mailbox that was being processed, in the other examples the failure was in the first attach to Exchange)

Comments 1 CommentJump to latest comment

Tifosa's picture

Another cause of the not very helpful 0x8004011D error code

https://www-secure.symantec.com/connect/forums/zapping-mailbox-returns-error-0x8004011d

+3
Login to vote