Exchange 2007 Storedriver Fail MapiExceptionNoAccess Errors

Posted on 2009-02-13
Last Modified: 2012-05-06
We have an Exchange 2007 SP1 running with mailbox/clientaccess/hub on one server. A lot of emails everyday (seems randomly) from external senders do not get delivered to recipients. There is no edge role and no spam/antivirus in place as we have an externaly antispam mail filter gateway. Emails come through the gateway as clean, get delivered to the exchange server but then fails when delivering it mailbox. So users are not even aware what messages are being missing. Server logs do not show any errors, but these can be picked up from the message tracking results. The eventID of the messages are FAIL and the Source is STOREDRIVER and the recipient status is:

550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error. The following information should help identify the cause of this error: "MapiExceptionNoAccess:16.18969:84010000, 17.27161:0000000098000000000000000000000000000000, 255.23226:00000000, 255.27962:7A000000, 255.27962:56000000, 255.17082:05000780, 0.16993:80030400, 4.21921:05000780, 255.27962:FA000000, 255.1494:00000000, 255.26426:56000000, 4.6363:0F010480, 6.21970:0F0104800201F3670F010480, 4.6363:0F010480, 2.31229:00000000, 4.1091:05000780, 4.4603:05000780, 4.5323:05000780, 255.1750:2F400000, 0.26849:05000780, 255.21817:05000780, 0.24529:00000000, 4.18385:05000780".

The exchange 2007 was a migration from Exchange 2003.

Can someone advise what the problem is.
Question by:Hayling
    LVL 65

    Expert Comment

    Is the server fully up to date?
    What else is on the machine?


    Accepted Solution

    We have now resolved this. Our environment was a migration from exchange 2003. I t appears that some of the permissions for AD were not set correctly. We followed the MS article although that refers to public folders. The permission was missing in one of the parent folders. We edited this using adsiedit uitility. The 'everyone' security group was added permission to:
    CN=Configuration, CN=Services,CN=Microsoft Exchange,CN='our exchange org name'
    The three permissions added were according to the MS article:

    Create named properties in the information store
    Create public folder
    Create top level public folder

    After this change we had no more failed messages

    Featured Post

    Top 6 Sources for Identifying Threat Actor TTPs

    Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

    Join & Write a Comment

    Get an idea of what you should include in an email disclaimer with these Top 5 email disclaimer tips.
    Easy CSR creation in Exchange 2007,2010 and 2013
    In this video we show how to create a Distribution Group in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >>…
    In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

    734 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    18 Experts available now in Live!

    Get 1:1 Help Now