Event Type: Error Event Source: MSExchangeIS Event Category: General Event ID: 9667 Date: 3/28/2010 Time: 8:20:35 AM User: N/A Computer: ?????? Description: Failed to create a new named property for database "First Storage Group\Heavy-Users Store (??????)" because the number of named properties reached the quota limit (8192). User attempting to create the named property: "????????" Named property GUID: 00020386-0000-0000-c000-000000000046 Named property name/id: "X-Imriu" For more information, click http://www.microsoft.com/contentredirect.asp. do i need to run an offline defragment or there is another solution?

Hi Which version of Exchange are you talking about here? I found a link, maybe it's helpful for you if you're talking about Exchange 2003 http://msexchangeguru.com/2009/09/04/event-id-9667/ http://support.microsoft.com/default.aspx?scid=kb;en-us;820379&sd=eeJonas Andersson MCTS: Microsoft Exchange Server 2010, Configuration | MCITP: EMA | MCSE/MCSA Blog: http://www.testlabs.se/blog

Hi first of all thanx for your reply. my exchange server is 2003 sp2 and i'm reading your links.

Hi, Go with the following link and it would be helpful for you. http://support.microsoft.com/kb/820379 Ashwin Raj

all links describe how to change on the registery but as i understand its not a permenant solution the other solution to create another DB and move some uers to it. but i want to ask if i did an offline defrag to reduce the DB size is this will be a good solution

On Mon, 17 May 2010 05:36:19 +0000, Mohammed_Omar wrote: >all links describe how to change on the registery but as i understand its not a permenant solution the other solution to create another DB and move some uers to it. but i want to ask if i did an offline defrag to reduce the DB size is this will be a good solution The original post refers to a problem where the number of named properties has exceeded the maximm number allowed. Defragging the database won't help even if you reduced its size to zero. Moving ALL the mailboxes to another database will halp -- temporarily. The only way to stop the increase in tne number of named properties is to remove the unwanted X-Headers from the messages before they arrive at the information store. Exchange 2007 SP1 RU9 can do that. There's also a transport agent that can be used to remove the headers. Exchange 2003, sadly, has no such ability unless you write your own code. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP