locked
Upgrade to Exchange 2007 MAPI_E_NOT_FOUND RRS feed

  • Question

  • I have a vb program that has been running for about 1 year.  This program reads functional mailboxes and stores sender, recips, body, etc in a database.  I'm using CDO 1.21.  We have some messages that come in with dummy senders (Dummy Complete), no email address just a name.  This was not a problem until our recent upgrade to Exchange 2007.  The program now errors out when attempting to read the sender type or sender.  The error received is MAPI_E_NOT_FOUND 8004010F.  Does anyone know why this is now occurring after the Exchange upgrade and how I might resolve?  Thanks in advance.

    Const PR_SENDER_ADDRTYPE = &HC1E001E
    With objMessage
            
            If .TimeReceived > StartDate Then
              
                strSubject = Trim(.Subject)
                dtReceivedDate = .TimeReceived
                
                
                'Sender Email
                strSenderType = .Fields(PR_SENDER_ADDRTYPE)
                Set objSender = .Sender
    End With
    Tuesday, September 7, 2010 6:54 PM

Answers

  • So that means the property is not present and you need to handle the exception in your code.
    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    • Marked as answer by NetLost Monday, September 13, 2010 2:32 PM
    Thursday, September 9, 2010 2:45 PM

All replies

  • I believe that IS the expected error if the recipient doesn't exist:

    Error 8004010F "MAPI_E_NOT_FOUND" with CDO 1.x:
    http://support.microsoft.com/kb/179639

    If you handle it with exception handling you should be able to continue your processing.


    (P.S. Please don't forget to mark this post as an answer if it has helped you)
    Eric Legault: MVP (Outlook), MCTS (SharePoint)
    Owner: Collaborative Innovations
    Twitter: elegault
    Blog: Eric Legault My Eggo
    Tuesday, September 7, 2010 7:47 PM
  • Happen to know what's different in Exchange/Outlook 2007 that would have triggered this to start occurring?
    Wednesday, September 8, 2010 4:09 PM
  • I doubt the Exchange version has anything to do it.  Is it possible that these recipients were in an address book that existed in the previous Exchange store and isn't in the current one?
    (P.S. Please don't forget to mark this post as an answer if it has helped you)
    Eric Legault: MVP (Outlook), MCTS (SharePoint)
    Owner: Collaborative Innovations
    Twitter: elegault
    Blog: Eric Legault My Eggo
    Wednesday, September 8, 2010 4:36 PM
  • It simply means that the PR_SENDER_ADDRTYPE property does not exist on the message.

    Can you see it in MFCMAPI or OutlookSpy (click IMessage) for that particular message?


    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    Wednesday, September 8, 2010 6:10 PM
  • Hi Dmitry,

    In OutlookSpy under IMessage, PR_SENDER_ADDRTYPE does not exist.  Looking under Item, SenderEmailType shows a value of blank ('').

    Thursday, September 9, 2010 2:43 PM
  • So that means the property is not present and you need to handle the exception in your code.
    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    • Marked as answer by NetLost Monday, September 13, 2010 2:32 PM
    Thursday, September 9, 2010 2:45 PM