We are using Exchange 2007 SP1 and have applied RU 8 but westill continue toreceive the event error 9667 (below). I understand I can continue to increase the quota limit but isthere anything I can do to correct this issue permanently?Thank you!Event ID: 9667Type: ErrorCategory: GeneralSource: MSExchangeISDescription: Failed to create a new named property for database "<database name>" because the number of named properties reached the quota limit (<configured quota>). User attempting to create the named property: <user name>. Named property GUID: <GUID of named property>. Named property name/id: <name of named property>.

Did those start after applying RU8? The rollup doesnt remove existing named properties, only prevents the promotion of certain types.You'll still need to raise the quota to stop those errors. http://technet.microsoft.com/en-us/library/bb851492.aspxUnderstanding the Impact of Named Property and Replica Identifier Limits on Exchange Databases

Theystarted before RU8. Since I've applied RU8 in June I've had to raise the quota twice.If I continue to raise thequote, the concern is it will eventuallycome close to the max limit.What is recommended at that point? Will I need to eventuallymove the mailboxes to another databases or is there something else I can do?

Ok, per : http://technet.microsoft.com/en-us/library/bb851495.aspx9667 events willfire for unauthenticated, authenticated and mapi promotions, so you'll need to track that down which one it is.These are firing for the same store each time, even after raising the limit? Which limit did you raise specifically?The non-mapi or the named?http://technet.microsoft.com/en-us/library/bb851493.aspxWhat do you have them set to now?

Exactly, after I raised the limit they continue tofire for the same store each time. I raised both the Named Props Quota limit & thenon-MapiNamed Props Quotaand currently Ihave themset to 9192.

But firing for which limit? the mapi or non-mapi?If you set the mapi created/authenticate to 9192, you actually lowered it:http://technet.microsoft.com/en-us/library/bb851492.aspx"By default, Microsoft ExchangeServer2007has a quota of 16,384 for named propertiesthat are created by authenticated users and replica identifiers. The default quota for named properties created by users who are not authenticated is 8,192. "

Both, butthe majority arenon-mapi.

Well, I would remove the reg key for the Named Props Quota and remount the store and test since its actually lower than the default.If you are still getting 9667 errors then you will have to raise the non-Mapi unauthenticated quota.Some other things you can do if it continues for unauthenticated messages is install the X-Header Filter Agent on the Hub Transport:http://www.codeplex.com/HeaderFilterAgentI have used it in the past with good success.You could also move mailboxes to new stores ( dividing them?) This won't remove the named props in the existing messages, but any that have been deleted wont follow the moved mailboxes and with less mailboxes per store, you'll have less chance of encountering this again for a much longer time ( E2010 fixes much of this problem)

Yes, I read that the default on the named props quota is 16K but it's strange because when I first went in to modify these settings it was setto 8192. I'll increase it to the default and see if that solves the issue. Thanks.

Great, I'll give that a try. Thanks Andy!

Is this problem fixed completely in SP2?

Sorry to resurrect this dead horse, but it the registry entry seems to be back on Exch 2007 SP2 RU4 servers, and it's set on every database to 8192. Where the ____ is the entry coming from, as our older server have a mixed bag of the reg key existing or not at all. On 200+ databases, to correct, what a pain.