Solved

Exchange 2003 - Event 9667 - Named Properties Reached the quota limit (16384)

Posted on 2014-09-18
1
217 Views
Last Modified: 2014-10-16
I am getting a repeating error and I cant seem to get it to stop. The error is:

EVENT ID:  9667

Failed to create a new named property for database "First Storage Group\Mailbox Store (EXEXC)" because the number of named properties reached the quota limit (16384).
 User attempting to create the named property: "SYSTEM"
 Named property GUID: 00020386-0000-0000-c000-000000000046
 Named property name/id: "Yynthel"

What I have done:  
1) Confirmed my quota limit is already at 16384. This was probably changed years ago to this value.
2) I installed a new exchange server and have moved 75% of my mailboxes now to the new server/mailbox store.

Concerns:  
1) I cannot completely disconnect this server because of other issues. Removing the first exchange server will be a challenge for me right now because of time and its on primary domain controller and active directory installed.

Questions:
Can I clean this name properties to make it smaller?
Can I start over with named properties database? What is impact?
Or will this just go away when I finish moving all my mailboxes to new server?  ...and I leave this server as the primary email server for awhile?
0
Comment
Question by:allenkent
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 35

Accepted Solution

by:
Seth Simmons earned 500 total points
ID: 40331726
Microsoft's only solution is to move all mailboxes to a new, blank database.

Events 9666, 9667, 9668, and 9669 Received When Named Properties or Replica Identifiers Are Depleted for An Exchange Database
http://technet.microsoft.com/en-us/library/bb851495(v=exchg.80).aspx
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

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

MS Outlook is a world-class email client application that is mainly used for e-communication globally.  In this article, we will discuss the basic idea about MS Outlook, its advanced features, and types of MS Outlook File formats.
After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses
Course of the Month9 days, 13 hours left to enroll

623 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