Solved

Named Properties Quotas in Exchange 2003 Event ID: 9667

Posted on 2010-09-23
2
547 Views
Last Modified: 2012-08-14
Recently my Exchange 2003 SP2 BE server has started having these errors occur in the Applications Log.  I have read all three of the articles below and I am still a bit confused about the solution.  I am hoping that someone can shed some light on the subject and help me resolve this.  The first link
describes modifying the registry to increase the default quota.  This solution seems like a temporary fix to the issue at hand.  I would hate to just keep increasing this quota until it hits the hard limit and opens a whole new can of worms.

The second article mentioned a hotfix from MS and description of how to modify the registry to prevent the generation of new named properties.  This seems like a more solid fix but my concerns are the side effects of disabling this feature.  If it wasn't necessary, it wouldn't be be there, so by disabling it, what features or functionality would I be losing?  

http://support.microsoft.com/kb/820379/en-us
http://msexchangeteam.com/archive/2010/07/29/455687.aspx

On a side note, the only two accounts listed in the description for this error are the "SYSTEM" and "BES" accounts.  Also, the "SYSTEM" account has only started showing up since I enabled OMA in ESM because I am trying to configure a Droid device to connect to our exchange server.  As I mentioned earlier, I am a bit confused by all of this so I decided to ask for some help.  Thanks in advance,
0
Comment
Question by:RHNOC
[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
2 Comments
 
LVL 34

Accepted Solution

by:
Shreedhar Ette earned 500 total points
ID: 33751071
Hi,

Make the changes as per the Microsoft kb 820379. Problem will be fixed.

Also refer:
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_23163596.html

Hope this helps,
Shree
0
 

Author Comment

by:RHNOC
ID: 33751107
How will the problem be fixed by only increasing the quota?  Won't this problem come back around in the future when the quote gets hit again?
0

Featured Post

Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

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

Unified and professional email signatures help maintain a consistent company brand image to the outside world. This article shows how to create an email signature in Exchange Server 2010 using a transport rule and how to overcome native limitations …
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
In this video we show how to create an Accepted Domain 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 >> Ac…
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…
Suggested Courses

624 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