External users are getting this error when they attempt to accept a meeting invitation sentfrom someone within our organization. The same two accounts can send regularemails between each other no problem. It only happens after a meeting request is accepted. It seems to behappening to users on a particular store, although i'm not positive about that one. We've tested this with several different external companies and even a couple of hotmail and msn accounts. No matter who our internal user sends the meeting request to, the recipient always gets this error when they try to accept. We aren't seeing the problem when internal users accept, or when an internal user accepts from an external meeting request. I've read that one of the possible resolutions is to move all the mailboxes to a new store, and then delete the old one. This sounds silly to me though since that would only buy us some time until the problem reappeared (not to mention the downtime required to move everyone.) We're native Exchange 2007 SP1, rollup 2. -jim Here's an example of the error message: 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: "MapiExceptionNamedPropsQuotaExceeded:16.18969:BE000000, 17.27161:00000000D4000000000000000000000000000000, 255.23226:31000000, 255.27962:7A000000, 255.27962:56000000, 255.17082:00090480, 0.16993:80030400, 4.21921:00090480, 255.27962:FA000000, 255.1494:00000000, 255.26426:56000000, 4.6363:0F010480, 2.31229:00000000, 4.6363:0F010480, 2.17597:00000000, 2.22787:00000000, 2.22787:00000000, 2.22957:00000000, 2.19693:00000000, 2.17917:00000000, 2.27341:00000000, 2.22787:00000000, 4.5415:00090480, 4.7867:00090480, 4.4475:00090480, 4.4603:00090480, 4.5323:00090480, 255.1750:00000000, 0.26849:2F000000, 255.21817:00090480, 0.24529:00000000, 4.18385:00090480".

Hi, Please check whether event 9667 which indicates Failed to create a new named property for database "First Storage Group\Mailbox Database" Default Exchange 2007 has limitation of 16,384 for named properties created by authenticated users and replica identifiers. The default quota for named properties created by users who are not authenticated is 8,192 If yes, then please follow the below kb to configure Named properties and Replica Identifier Quotas to value-32000 How to Configure Named Properties and Replica Identifier Quotas for Exchange 2007 Databases http://technet.microsoft.com/en-us/library/bb851493(EXCHG.80).aspx Understanding the Impact of Named Property and Replica Identifier Limits on Exchange Databases http://technet.microsoft.com/en-us/library/bb851492(EXCHG.80).aspx Events 9666, 9667, 9668, and 9669 Received When Named Properties or Replica Identifiers Are Depleted for An Exchange Database http://technet.microsoft.com/en-us/library/bb851495(EXCHG.80).aspx More information share with you: How to Enable Additional Information Store Logging.http://support.microsoft.com/?id=254606 Hope it helps. Xiu

My understanding is that this would only be a temporary fix, until the named properties limit was reached again. At that point i'd need to create a new database and move all the messages. Am i undertanding this correctly? I'd like have a permanent solution instead of a short-term band aid. jim

Here are detailed discussions you got http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?query=Named+properties+quota+exceeded%3F&dg=&cat=en_US_e2dcdfff-cde7-41b1-98fb-c15563ef8d12&lang=en&cr=US&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us You can increase the quota and monitor the counter with perfmon as Xui suggested and another thing as you told move the mailboxes and dialtone the database but both are workaround to avoide the error for time being. You may need to find out the application if anyone is creating more named properties by dumping named properties with MFCMapi. It seems that we need to wait till next version of Exchange for fix.

I opened a case with MS Support. I had to be transferred to the Connectors department. Apparently it's a known "issue" (i.e. bug) and they're aware of it. I was told they're working on a fix, but i'll need to increase thenamed properties quota in the mean time to correct the issue for now. Hopefully we won't have to wait until the next version of Exchange.

Great, thanks for the update. I am eagerly waiting ifpermanent fix will be availabe about this

Ok, it's been a year and I'm still getting this error, has there been any fixes released? This URL comes up with nothing now? http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?query=Named+properties+quota+exceeded%3F&dg=&cat=en_US_e2dcdfff-cde7-41b1-98fb-c15563ef8d12&lang=en&cr=US&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us

The fix is included in next update rollup of SP1 of Exchange 2007, UR8. Named Properties, X-Headers, and You http://msexchangeteam.com/archive/2009/04/06/451003.aspxAmit Tank | MVP - Exchange | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com

Do they have a fix for Exchange 2003? We are about 10 instances from reaching out quota. I was planning on doing an offline defrag this weekend, and wondered if it would have any positive contributions. Thanks.

How do you make those changes?"MapiExceptionNamedPropsQuotaExceeded:16.18969:BE000000,

On Fri, 18-Dec-09 23:18:16 GMT, carmenchacha4343 wrote:>How do you make those changes?"MapiExceptionNamedPropsQuotaExceeded:16.18969:BE000000, See this URL:http://technet.microsoft.com/en-us/library/bb851493(EXCHG.80).aspxYou should also install Rollup 9 on Exchange 2007.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

http://msexchangeteam.com/archive/2010/07/29/455687.aspx ed About Named Properties Quotas in Exchange 2003 and Exchange 2007? Join the Club!