I am having the following issue on the exchange 2007 box:Event Type: ErrorEvent Source: MSExchangeISEvent Category: General Event ID: 9667Date: 3/16/2010Time: 3:42:40 PMUser: N/AComputer: SERVERDescription:Failed to create a new named property for database "First Storage Group\Mailbox Database" because the number of named properties reached the quota limit (8192). User attempting to create the named property: "NETWORK SERVICE" Named property GUID: 00020386-0000-0000-c000-000000000046 Named property name/id: "mlp-districtid" For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.The server database was shut down dirty. I did eseutil /r and then the eseutil /d. I finished with the isinteg -s SERVERNAME -fix -verbose -test alltests.In the end the isinted showed 0 errors 0 warning 0 fixes.I have over 13000 messages in queue, that goes through a journaling account. I don't know if this is caused by flow control on the Exchange box.I saw a post about modifying the registry over at eventid, but can't confirm the post to be true or helpful.http://www.eventid.net/display.asp?eventid=9667&eventno=7326&source=MSExchangeIS&phase=1I plan on moving the mailboxes to a new database store and remove the one that got pooched

Hello, This is quite a nasty situation the one that you had to face.I' ve noticed that you have said you are on Exchange 2007. My question would be are you already on SP2 for E2k7.I dont know if you are aware of this but SP2 has a lot of features that were conceived especially for addressing the name properties exhaustion issues we have faced in the past.Here are a couple of great articles that describe what SP2 brings new to the named properties topic:http://msexchangeteam.com/archive/2009/08/06/451948.aspx : new cmdlet get-namedproperty, allows you to visualise what is happening with named propshttp://msexchangeteam.com/archive/2009/06/12/451596.aspx : great post about the progress being made on this topic" As mentioned before, Exchange 2007 creates named properties for x-headers during delivery. The RTM version of Exchange 2007 would NDR messages if the named property quota was reached, even if the property were only for an x-header. Service Pack 1 changed this behavior to only NDR the message if a non X-header named property could not be mapped (in other words, a property likely to contain critical data). Rollup 8 for Service pack 1 removes the ability of non-authenticated messages to consume named property IDs. Service Pack 2 goes even further. Service Pack 2 is in line with Exchange2010 behavior - that is, no x-headers are ever promoted to individual properties if a client has not already requested (and mapped) them. Not even authenticated submissions can create new named property mappings. "On the other hand, your plan of moving the mailbox to a new database is OKStill, I think you need to take a look at those links and consider SP2 If you dont have it already.Thanks, Mihai

It appears that these messages have been going on for months prior to the database crash.I am going to have the full time exchange admin look into this, I do know that SP2 is not installed.Thanks for the advice.Harold

Agree with Mihai. Please update the exchange server with the latest patch Event ID 9667 occurs when you create a new named property on an Exchange Server 2007 serverJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com