increasing database named property quota for Exchange 2003
Hello,I'm seeing event 9667 - "Failed to create a new named property for database....." for one of my databases. The current quota is 8192, so I want to increase the quota. I'm looking at the TechNet page that explains how to do this - http://technet.microsoft.com/en-us/library/bb851493(EXCHG.80).aspx. The problem is, this document stops after telling you how to determine the GUID of the database; it doesn't tell you which registry key/value to modify. Can someone please point me to a complete document that explains how to do this? In addition to dismounting/remounting the affected mailbox store, will I also need to restart the Exchange Information Store service?Thanks in advance for any assistance.
October 7th, 2008 12:52am

OK, I found the registry key/value that needs to be modified to increase the named property quota for the database. When I look at the "Private - xxxx-xx-xx-xx-xxxx" (GUID) registry key for this database, the 'Named Props Quota' has a value of 0x00004fa0 (20384). But in the event logs, the 9667 events say "Failed to create a new named property......because the number of named properties reached the quota limit (8192)." Why does the event viewer think the quota is 8192 when the registry shows the quota to be 20384? Should I assume that the quota is 20384 and set it to be something bigger than that? Thanks.
Free Windows Admin Tool Kit Click here and download it now
October 7th, 2008 1:37am

Can anyone provide more information about this? I'd like to know why the registry and the logs are reporting different values for the current quota. I'm assuming that the registry data value is the accurate data, but on the other hand I don't want to increase the quota to 21000+ if I can get away with setting it smaller (which would be the case if the 8192 quota reported by the logs is accurate). Thanks.
October 8th, 2008 2:28am

Hi, According to the following article: Understanding the Impact of Named Property and Replica Identifier Limits on Exchange Databases http://technet.microsoft.com/en-us/library/bb851492(EXCHG.80).aspx We can get the following information: Exchange 2007 defaults for quota limits: Named Props Quota 16K NonMAPI Named Props Quota 8K Replids Quota 8K Named Properties consists of both Named Props Quota and NonMAPI Named Props Quota. Hence, for taking care of Event ID 9667 in this scenario, we need to add both the Named Props Quota and NonMAPI Named Props Quota registry values to the registry key. The default for Named Props Quota is 16K and for NonMAPI Named Props Quota is 8K in Exchange Server 2003/2007. Since, we are getting Event ID 9667, so that means that the default for Named Properties is exhausted. Hence, we need to add both the above registry keys with values more than the default. Note: Replids Quota value is used by public folder replication, so in this case we do not need to increase its value. ADDITIONAL INFORMATION: We may turn up additional store logging within System Monitor to monitor Named Props table. 254606 XADM: How to Enable Additional Information Store Logginghttp://support.microsoft.com/default.aspx?scid=kb;EN-US;2546061. Start Registry Editor (Regedt32.exe). 2. Locate the Library value under the following key in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\Performance 3. On the Edit menu, click String , change the value from c:\exchsrvr\bin\mdbperf.dll to c:\exchsrvr\bin\mdbperfX.dll , and then click OK . 4. Quit Registry Editor. 5. Start System Monitor, and select MSExchangeIS Mailbox Performance object.6. Select "Rows in Named Props Table" and select the mailbox store we are monitoring. Mike
Free Windows Admin Tool Kit Click here and download it now
October 8th, 2008 12:39pm

Thanks for your response. One more question about this - what exactly is the impact of reaching the *set quota* (not the hard limit) for a store's named property quota? I'm about to increase the quota for my affected store, but so far haven't heard of any issues for my users. So I'm just wondering what the potential risks are if the store reaches the quota and it's not increased.Thanks again for your input.
October 14th, 2008 4:50pm

I would like some more information on this issue also. Is there a way to figure out what is causing you to exceed the quota instead of just increasing it?
Free Windows Admin Tool Kit Click here and download it now
November 26th, 2008 10:53pm

I found the following information regarding the cause (forgot where)... It is applicable in my case as we use postini archive. It is caused by an x-header going in to the message. I don't think it is the exact same issue that you have identified in that Technet article. I would also doubt that would work because it is for Exchange 2007. Does your email come in through another service or server? That is what is putting the X header in that is causing the problem.
December 1st, 2008 10:57pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics