J'ai eu un cas client lors d'une migration Exchange 2003 vers 2010, les invitations de réunion ne revenaient jamais aux utilisateurs du 2003, les utilisateurs du 2010 recevaient un message d'erreur : #SMTP

Il s'agit en fait d'un problème de propriétés nommées dont le quota est atteint, l'event log Applications du serveur est rempli d'erreurs.

Il faut modifier dans le registre les paramètres de la base de données 

Named Props Quota

NonMAPI Named Props Quota

Replids Quota

En les passant par exemple a 7FFF en hexa.

 

http://exchangeserverinfo.com/2009/08/28/how-to-resolve-9667-events-in-exchange-2003--exchange-2007-servers.aspx

 

The Microsoft Exchange Information Store service maintains a table of named properties for each database. By default, Exchange Server 2003 and Exchange Server 2007 have a hard quota of 16,000 named properties or replica identifiers for each MDB. Note You can use this registry value only after you apply Exchange Server 2003 Service Pack 2. The default value of the registry value is 8000.

 

The only way to "clear" named properties is to move to a new store. The workaround is to manually raise the name properties level.

 

When the default value of 8000 is crossed, the 9667 events are generated as shown below for example:

 

Event Type: Error

Event Source: MSExchangeIS

Event Category: General

Event ID: 9667

Date: 8/19/2009

Time: 2:27:35 PM

User: N/A

Computer: EXCHANGE03

Description:

Failed to create a new named property for database "First Storage Group\Mailbox Store (EXCHANGE03)" 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

 

In registry, you might find multiple store Guids as shown below. You need to make sure which one is the right mailbox store where you need to make the changes. You can compare with the ObjectGUID value using ADSIEdit.msc for that particular mailbox store.