Named Properties-Quota Limit 2

[Excalibur1701]

I'm getting a scary message on our Exchange Server 2003-SP2-Standard.

Event ID: 9666
"The number of named properties created for database "First Storage Group\mailbox Store is close to quota limit
Current Number of named properties: 8175
Quota limit for named properties: 8192

I have two questions: One, what happens to my exchange server when I reach the limit, and two, how can I either delete some of the "named properties" or increase the size of it?

Searching the internet provides very little help and it almost always refer to Exchange 2007, and not 2003.

Please help a nervous administrator.

Thanks

 

[ShackDaddy]

1. You can't delete named properties.
2. Most likely, you have merely hit an alert quota limit and not the cap.
3. Once you hit the cap, it's bad news. You have to find a way to migrate your mailboxes to another mailbox database, delete your mailbox database, and migrate back. There are some backup/restore scenarios that might let you do something easier.
4. This problem is usually caused by some sort of archiving or data collecting app tied to email, and the app usually indexes the headers of email it handles and inadvertently creates new named property entries in a database. The possible variations of property values are endless, so it's a good idea to track down the source of the problem (3rd party app usually) and ask the vendor what can be done to curtail that x-header indexing behavior.

Dave Shackelford
ThirdTier.net

 

[xmsre]

There's a script on codeplex to strip out the x headers I believe.

 

[ShackDaddy]

I know there's this one:

http://www.codeplex.com/HeaderFilterAgent

But it only applies to Exchange 2007. I haven't seen one for Exchange 2003.

Dave Shackelford
ThirdTier.net

 

[Excalibur1701]

Thanks for all your useful advice.

I went ahead and increased the "NonMapi Named Props Quota" in the registry. I think the value can be up to 32767 decimal, but don't hold me to that. I figure I have another 3-4 years before I hit that max The messaged has stopped. For those interested, it's located here:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<<your server name>>\Private-00000-000-000

Although the document I found said to dismount the store for the changes to take effect, it wasn't necessary.

 

[Zelandakh]

You could have just told us it was fixed but you came back and reported exactly what happened and additionally offered a tip about not needing to restart.

Nice one.

Have a star on me.