Named Property Creation Failed

Error description:

Recall messages, meeting requests, out of office replies, iPhone mails froman Exchange 2010 mailbox to an Exchange 2003 mailbox can’t be delivered. In all these cases, one or more errors with ID 9667 are generated in the Application event log on the Exchange 2003 mailbox server. In most cases a 5.2.1 error is returned to the sender.
The underlying error ( ID 9667 ) mentions that the limit of Named Properties has been reached. This error causes that the message is not delivered to the mailbox store.
In order to solve this issue, we have to suppress the error and/or increase the limit of the named properties (nonMAPI + MAPI).br/>

25/05/2011
11:35:13
MSExchangeIS
Error
General
9667
N/A
EXCHANGE2003
"Failed to create a new named property for database ""First Storage Group\Mailbox Store (EXCHANGE2003)"" because the number of named properties reached the quota limit (8192).
 User attempting to create the named property: ""SYSTEM""
 Named property GUID: 41f28f13-83f4-4114-a584-eedb5a6b0bff
 Named property name/id: ""XLoop""
 
25/05/2011
11:35:13
MSExchangeIS
Error
General
9667
N/A
EXCHANGE2003
"Failed to create a new named property for database ""First Storage Group\Mailbox Store (EXCHANGE2003)"" because the number of named properties reached the quota limit (8192).
 User attempting to create the named property: ""SYSTEM""
 Named property GUID: 00020386-0000-0000-c000-000000000046
 Named property name/id: ""X-MS-Exchange-Inbox-Rules-Loop""

 
A meeting request message sent to an Exchange 2003 mailbox that generates one  error:

30/05/2011
14:08:13
MSExchangeIS
Error
General
9667
N/A
EXCHANGE2003
"Failed to create a new named property for database ""First Storage Group\Mailbox Store (EXCHANGE2)"" because the number of named properties reached the quota limit (8192).
 User attempting to create the named property: ""SYSTEM""
 Named property GUID: 00020386-0000-0000-c000-000000000046
 Named property name/id: ""22""

Solution:

Suppress the generation of 9667 errors

Installation of hotfix KB972077. More information about this hotfix: http://support.microsoft.com/default.aspx?scid=kb;EN-US;972077
This hotfix suppresses the generation of new MAPI named properties, and at the same time the generation of the related errors also. This fix prevents that the Named Properties store gets filled up in no time. It doesn’t suppress the generation of nonMAPI properties.
After installation of this hotfix and adding the registry setting, a restart of the system attendant is needed to apply the registry setting.

 

Increase the limit of named props

Add DWORD values to the registry in order to increase the named properties quota ( for MAPI and nonMAPI properties )

Hard limits:

Number of the named properties table (MAPI + nonMAPI):     16000    (0x3E80)
Customizable limits:
Current limit of MAPI + nonMAPI named properties:          8192     (0x2000)
Current limit of nonMAPI named properties:            8192    (0x2000)
Increase limit to:                        
Current limit of MAPI + nonMAPI named properties:          12288     (0x3000)
Current limit of nonMAPI named properties:            12288     (0x3000)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\\Private-2dc73c47-1738-4f62-9f43-b33f75ab8853\Named Props Quota
REG_DWORD : 0x3000

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\\Private-2dc73c47-1738-4f62-9f43-b33f75ab8853\NonMAPI Named Props Quota
REG_DWORD : 0x3000

To apply the registry settings, dismount the mailbox store and re-mount it.
actions for Exchange 2003 clusters

• Set 2 registry settings above
• Dismount the Mailbox Store (EXCHANGE 2003 Server )
• Mount the Mailbox Store (EXCHANGE 2003 Server )
• Restart Microsoft System Attendant
• Repeat the steps above  for the other node
• If done, you can try to send a meeting request from an iPhone with a Exchange 2010 mailbox to a mailbox on Exchange 2003. This way the named properties table gets successfully populated by these named properties before  the new limit is reached.