• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2025
  • Last Modified:

Exchange 2007 Storedriver Fail MapiExceptionNoAccess Errors

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.
0
Hayling
Asked:
Hayling
1 Solution
 
MesthaCommented:
Is the server fully up to date?
What else is on the machine?

-M
0
 
HaylingAuthor Commented:
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 http://support.microsoft.com/kb/313866 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
0

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now