Outlook 2010 Beta Error on Exchange 2007 - #550 5.2.0 MapiExceptionNamedPropsQuotaExceeded:16.18969

  • Thread starter ScottM762
  • Start date Views 3,029
Status
Not open for further replies.
S

ScottM762

We're having some issues with some users using Outlook 2010 Beta on Exchange 2007 SP1, with UR8. The message is rejected and the error is:

#550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error. The following information should help identify the cause of this error: " MapiExceptionNamedPropsQuotaExceeded:16.18969

Only one known recipient bounced that I know of. The issue seems to remain between the afflicted sender and recipient as long as the sender is using Outlook 2010. I searced for solutions and originally it is thought that the Named Props Quota is the culprit, but we shouldn't experience that with Update Rollup 8 installed. I wasn't able to move the effected recipient, but I did try using 2010 with my account and could not replicate the issue. Originally I was on a different database then the original sender, I moved my account to the sender's database, and sent to the same recipient without an issue.

One thing I couldn't replicate is that the original sender is using Vista, and I used XP with SP3.
 
G

Gavin-Zhang

Hi Scott,

Agree with Andy, you could learn more about the named property and the ur8 from below link:

http://technet.microsoft.com/en-us/library/bb851492(EXCHG.80).aspx

http://technet.microsoft.com/en-us/library/bb851495(EXCHG.80).aspx

http://support.microsoft.com/kb/948856

And according to your description, there is just only one user client have the issue, it seems the client would create a new x-header from the named property. So please confirm there no other client has the same question, and confirm the issue client whether has some other software installed, such as anti-spam, antivirus, and messaging server applications, may add their own X-headers to a message.

Regards!

gavin
 
S

ScottM762

Check the event logs on the Exch Server, it should have fired an error if the named props were exceeded.

Please see my responses to this issue in as well. Its important to note that SP1 RU8 only prevents the promotion of anonymous x-headers, it doesnt fix an existing quota overlimit issue or remove existing named props.

http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/411a3203-9802-4463-b2b1-a7d659c3e512
Thanks for the replies... Sorry it took so long, priorites often shift.

There was a 9667 event generated when these messages failed.
 
S

ScottM762

Hi Scott,
Agree with Andy, you could learn more about the named property and the ur8 from below link:
http://technet.microsoft.com/en-us/library/bb851492(EXCHG.80).aspx
http://technet.microsoft.com/en-us/library/bb851495(EXCHG.80).aspx
http://support.microsoft.com/kb/948856
And according to your description, there is just only one user client have the issue, it seems the client would create a new x-header from the named property. So please confirm there no other client has the same question, and confirm the issue client whether has some other software installed, such as anti-spam, antivirus, and messaging server applications, may add their own X-headers to a message.
Regards!
gavin Thanks Gavin. The issue did occur with more that one person, but most others already uninstalled Outlook 2010. The recipients were isolated to a rather large database.

If anyone else runs into the problem, we upped the named property limit in the registry on this database as a temporary solution, and then moved the users off to two databases.

Scott
 
Status
Not open for further replies.
Top