|
exchange
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
9667 ErrorOur Exchange 2003 server recently began receiving the following error about4
times daily: Event ID 9667: Failed to create a new named property for database "First Storage Group\Mailbox Store G-M (EXCHANGE)" because the number of named properties reached the quota limit (8192). Any thoughts?
http://technet.microsoft.com/en-us/library/bb851493.aspx
Show quote Hide quote "Don Powell" <Don Pow***@discussions.microsoft.com> wrote in message
news:1CB5AD9C-DBF5-4E26-AE2D-F0FC9BE97F7A@microsoft.com... > Our Exchange 2003 server recently began receiving the following error > about4 > times daily: > > Event ID 9667: Failed to create a new named property for database "First > Storage Group\Mailbox Store G-M (EXCHANGE)" because the number of named > properties reached the quota limit (8192). > > Any thoughts? > Yes, I found that article but didn't understand (or it didn't clearly
explain) what is causing this error. Does it have to do with the size of the message store or something else that we've maxxed out? Also, what should I change the seeting to if it's now at 8192? Show quoteHide quote "John Fullbright" wrote: > http://technet.microsoft.com/en-us/library/bb851493.aspx > > > "Don Powell" <Don Pow***@discussions.microsoft.com> wrote in message > news:1CB5AD9C-DBF5-4E26-AE2D-F0FC9BE97F7A@microsoft.com... > > Our Exchange 2003 server recently began receiving the following error > > about4 > > times daily: > > > > Event ID 9667: Failed to create a new named property for database "First > > Storage Group\Mailbox Store G-M (EXCHANGE)" because the number of named > > properties reached the quota limit (8192). > > > > Any thoughts? > > > > > Named properties and non-MAPI named properties will need to be raised for a
9667. Raising the limit is only a workaround. The issue is X headers, and you need to figure out what is causing them and find a solution to strip them for a long term fix. Show quoteHide quote "Don Powell" <Don Pow***@discussions.microsoft.com> wrote in message news:8C5936EA-34A2-46B5-AD69-52FB8CEA5499@microsoft.com... > Yes, I found that article but didn't understand (or it didn't clearly > explain) what is causing this error. Does it have to do with the size of > the > message store or something else that we've maxxed out? Also, what should I > change the seeting to if it's now at 8192? > > "John Fullbright" wrote: > >> http://technet.microsoft.com/en-us/library/bb851493.aspx >> >> >> "Don Powell" <Don Pow***@discussions.microsoft.com> wrote in message >> news:1CB5AD9C-DBF5-4E26-AE2D-F0FC9BE97F7A@microsoft.com... >> > Our Exchange 2003 server recently began receiving the following error >> > about4 >> > times daily: >> > >> > Event ID 9667: Failed to create a new named property for database >> > "First >> > Storage Group\Mailbox Store G-M (EXCHANGE)" because the number of named >> > properties reached the quota limit (8192). >> > >> > Any thoughts? >> > >> >> >> 
Other interesting topics
Exchange database import
Multiple Domain on one 2003 exchange server Notification at alternate e-mail address form based logon for OWA, ActiveSync, etc. in Exch 2007 Moving a store, post office to another server Mail 3.5 with Exchange 2007 Time off in mail Active Directory Name Change-how 2 move original email to new mail Cant email mail enabled folder exchange 2003 routing service will not start |
|||||||||||||||||||||||
