I'm curious about the "NOT be created in most circumstances" part of the comment, Michael. Any feeling for what most means there?
We certainly hit this in E2K3, on non-journal servers. Of course, a thousand users in the same database without moving for a few years can do that... we wound up putting the registry keys for 0x6000 Named Props, Replids, and NonMAPI Named Props into our Exchange install scripts. I think some company's stupid anti-spam software was tagging message with different X-headers, instead of using the same X-header with different values. KB820379 links to all the relevant articles, I think; the registry values listed were valid for E2K3 as well as E2K7. ________________________________ From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2008 7:39 AM To: MS-Exchange Admin Issues Subject: RE: events 9666 and 9668 in an Exchange 2003 database Yes, the same max values are fine. The easiest way to reset the counter is to move all the mailboxes in a given store to another store. Drop the old store. I'm personally of the opinion, although no one admits it, that there was a bug in Exchange 2003 prior to sp2 that caused the values to NOT be created in most circumstances. Because prior to sp2, no one ever complained about this.... Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Russ Patterson [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2008 10:25 AM To: MS-Exchange Admin Issues Subject: events 9666 and 9668 in an Exchange 2003 database Hi all - We've recently hit this issue in an Exchange 2003 database and I can't find any specific info about E2k3. The data on E2k7 and these events is pretty clear; and I did find some input somewhere (maybe Experts Exchange??) that said the E2k7 info worked fine on E2k3. We get event 9666 - warning about the number of named properties created for database "JournalStore." - this is a store where we have only 6 mailboxes, each mailbox is journaling a store from our other Exchange servers. (We have 6 stores for end-users, one store for Journaling & 1 store for mailboxes we don't want to journal.) Just wondering if the experts here can vouch for the assertion that the data for E2k7 is harmless for E2k3? Is the max quota given for E2k7 (0x7FFF hex, 32767 decimal) safe for E2k3? Can anyone explain why we need to keep track of all these random headers? Can anyone offer a good explanation about why the store needs to keep up with this info? - I know the kb article says " The named properties provide a way for vendors to extend the standard MAPI property set by adding their own properties. Because the named properties do not have specific IDs assigned to them, MAPI provides a facility for dynamically creating unique IDs for named properties and maintaining a persistent mapping between the named property and its unique ID. " and "For example, when a company implements a new application that integrates with Exchange and uses a specific Simple Mail Transfer Protocol (SMTP) X-header, the Microsoft Exchange Information Store service creates a named property for that custom information when it processes the first message that contains that information. Any subsequent messages that include the same SMTP X-header do not result in the creation of additional named properties." but that doesn't really explain why we need to do this. Plus, it only warns us at 20 before the quota, and we ate 12 of those in less than an hour..... Thanks for any input - This e-mail is intended for the use of the addressee(s) only and may contain privileged, confidential, or proprietary information that is exempt from disclosure under law. If you have received this message in error, please inform us promptly by reply e-mail, then delete the e-mail and destroy any printed copy. Thank you. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
