We are in the process of an upgrade/migration from Exchange 2003 to 2010. We have moved about 20 users so far. We've discovered a problem when a user who has had their mailbox moved to 2010 tries to send a meeting request to certain (not all) users on the 2003 system they get a bounced message saying: "There's a problem with the recipient's mailbox. Please try resending this message. If the problem continues, please contact your helpdesk." Also, on the EX2003 server event 9667 is logged: "Failed to create a new named property for database "First Storage Group\Mailbox Store (SERVERNAME)" because the number of named properties reached the quota limit (8192)." I've found the MS document http://technet.microsoft.com/en-us/library/bb851495(EXCHG.80).aspx but not sure if/how this helps in this case. It does not seem to happen with all users sent to and only seems to be affecting users who have had their mailbox moved. Any advice welcome. Thanks

For error Event Id : 9667 How to configure quota settings for named properties and for replica identifiers in Exchange Server 2003 and in Exchange Server 2007 http://support.microsoft.com/default.aspx/kb/820379/en-us http://social.technet.microsoft.com/forums/en-US/exchangesvrgeneral/thread/cee1cfb2-1fa1-41e9-adff-00ecd0b0729a Anil

Hi Thanks for your reply. As I said - I found details on how to change the values mention. My concern is why is this happening ? I'm reluctant to make registry changes on the main Exchange server unless absolutely necessary. Why would the user on the EX2010 system only get this error when sending to one particular (so far) mailbox and only with meeting requests ? Thanks

Hi, In Exchange 2010, named property resources are moved to the mailbox level instead of to the database level. When many X-headers are promoted to named properties and reached the quota limitation, unexpected error would occur. For this issue, the new x-header for Exchange 2010 has pushed it to the quota. I would explain more detail: the Microsoft Exchange Information Store service maintains a table of named properties for each database. When the information store processes a message that contains custom information, the store automatically adds an entry to the named properties table for any custom property that has not been previously processed. Because there are a fixed number of named properties available, Exchange uses a quota system to track the number of allocated named properties. In this system, the Store.exe process warns you when available named property IDs are close to becoming exhausted. When a second threshold is reached, the Store.exe process no longer allocates named property IDs. Although with Exchange 2010, it does not promote new X-headers from unauthenticated submissions, embedded messages, and journal messages. However, the X-headers requests that are submitted by authenticated clients can be still promoted. Also, later unauthenticated submissions will still process the values of X-headers because any subsequent messages that include the same X-header do not create additional named properties. But since we still use outlook 2007, x-headers are still stored in PR_TRANSPORT_HEADERS and still accessible to MAPI clients but they are not individual properties. More information to share with you: Understanding the Impact of Named Property and Replica Identifier Limits on Exchange Databases http://technet.microsoft.com/en-us/library/bb851492(EXCHG.80).aspx Similar thread to share with you: Cannot send mails from user in Exchange 2010 to user in Exchange 2003 using Outlook 2007 (it works with Outlook 2010 beta http://social.technet.microsoft.com/Forums/en/exchange2010/thread/be90453d-c028-4a02-a5d3-f4eaa1a7556e Regards, Xiu

Hi Thanks for that. Does this mean there is a danger of the Information Store actually failing if we don't make this registry change ? Thanks

Theoretically speaking, If all named properties or replica identifiers are exhausted(reach maximum of 32,766) for a database, you must perform a recovery process, which is disruptive to your Exchange environment. Regards, Xiu

Hi When you say perform a recovery process do you mean an actual restore of the DB - or just a reboot. Thanks

Hi, That should be a actual restore of the DB. Detail steps we can refer to the article "Understanding the Impact of Named Property and Replica Identifier Limits on Exchange Databases" Regards, Xiu

Hi With regards to the KB article on increasing the value in the registry - http://support.microsoft.com/kb/820379/en-us. What value should we be entering without risking the mail store from failing completely ? The article states the limit is 16,000 but also mentions 32000. The error we are getting states 8192 so I'm a bit confused. Thanks

It says you can enter anything between 1 and 0x7FFF (32767). -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "jarweb" wrote in message news:a51824ed-df2f-4adc-8ecd-4f4cf6df36c0... Hi With regards to the KB article on increasing the value in the registry - http://support.microsoft.com/kb/820379/en-us. What value should we be entering without risking the mail store from failing completely ? The article states the limit is 16,000 but also mentions 32000. The error we are getting states 8192 so I'm a bit confused. Thanks Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Yes - but it says if it hits the upper limit - "maximum of 32,000 entries could make the computer unresponsive to client requests" Hence why I was asking what a "reasonable" value would be without risking the mail store falling over. Thanks