Learn how to a build a cloud-first strategyRegister Now


Named Property Limits on Exchange 2007 SP1

Posted on 2008-11-17
Medium Priority
Last Modified: 2012-05-05
I have recently started receiving the EventID 9667, msgidNamedPropsQuotaError on a Exchange 2007 mailbox server.  Research has shown that the server has reached the default quotas for named propertiy entries for the database.  These can be increased by adjusting the values in the registry of the "Named Props Quota" and "NonMAPI Named Props Quota" for a mailbox database or "Replids Quota" for a public database.

KB articles say the default limits are 16384 for the "Named Props Quota"(NPQ) and "Replids Quota"(RQ) and 8192 for the "NonMAPI Named Props Quota"(NNPQ).  They also say that each database has a hard limit of 32766.  They say if you reach that limit, you will have to create new databases and move the users out and then back in to reset the numbers.  They also say you should not set the quotas to the max limits.  However, the instructions on how to change the values say to enter a number between 1 and 32767.

Currently, my registry only has the NNPQ setting with a value of 8192.  The 8192 value is the one being referenced in my event log errors.

Relevant articles:
Event ID 9667:  http://technet.microsoft.com/en-us/library/bb851495.aspx
How to configure:  http://technet.microsoft.com/en-us/library/bb851493.aspx
What they mean:  http://technet.microsoft.com/en-us/library/bb851492.aspx

What they don't say is how the numbers relate to each other.

Since the NPQ and NNPQ both affect the mailbox database, do their combined values need to stay below 32766 or are their limits separate?  
Do I only need to update the value that is already in the registry or should I be creating the others?


Question by:CMES-IT
  • 2

Expert Comment

ID: 22981456
More than likely you are reaching the max on the Non Mapi named props, I think you are saying that you believe that as well. When you send emails that cross spam filters or whatever, non mapi named props are added such as x-headers and so on, anyways, the two types are seperate, so yes you can just raise the single entry in the registry for non mapi to buy you more time. However....like you mentioned you should NOT set this to the MAX, because the next time you get the warning there will be no more time to add more grow room. I would recommend that you push the non mapi to 16k or so, then start your plans on how you will begin moving mailboxes to a new db.

How long have you had this DB in production? That is how long it took the DB to reach 8k, so that can help you determine how long you have before 16k....though this can spike and move faster and slower depending on mail traffic.

Also, the named prop tables are db specific so you will have to move the users to a new db, and you can not move them back into the old.

hope this makes sense, let me know if you have any questions.


Author Comment

ID: 22984034
If I bump the single for nonMAPI to 16k and the MAPI is already at 16k, won't that risk me reaching the set limit of 32k or are the limits seperate so they can both go to 32k?  I guess I'm asking if it is a combined limit or a seperate limit for each type?

They say that if you reach the 32k limit you should create a new db, move the users, delete and recreate the old db (makes a new file) and then move them back.



Accepted Solution

DraconianSoul earned 2000 total points
ID: 23511915
I came across this question because I had similar concerns.  I thought I'd post with what I've discovered...  According to the article here: http://technet.microsoft.com/en-us/library/bb851492.aspx, "Exchange has a maximum limit of 32,766 property IDs for each database."  This means to me, that all the property IDs, whether they are anonymous or otherwise, live in the same space.  Therefore, if both quotas are set to 16384 and you max both out, you will have hit the 32766 hard limit.

Author Comment

ID: 23513833
That would make sense.  It would also explain why there is no value for the MAPI in the registry since it is already at the max by default.

As a side note:  From what I can see, the numerous headers being placed by spam control efforts combined with the spoofed headers in spam and virus messages, is causing this number to rise quicker than developers expected.  I have also heard rumor that rollup 7 may have a method to address hitting the limits that is not as drastic as the method currently required.  I guess we can wait and see.


Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Here in this article, you will get a step by step guidance on how to restore an Exchange database to a recovery database. Get a brief on Recovery Database and how it can be used to restore Exchange database in this section!
In this post, I will showcase the steps for how to create groups in Office 365. Office 365 groups allow for ease of flexibility and collaboration between staff members.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
Suggested Courses
Course of the Month20 days, 14 hours left to enroll

864 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question