We've had some issues with a user who has upgraded to Outlook 2010 and attached to an internal Exchange 2003 SP2 server. They get errors more or less saying cannot send, contact your administrator and then a long error string whenever attempting to send. They receive just fine - but can't get any outbound flow.

We recreate the users profile on another Windows 7 machine with Outlook 2010 and it worked fine. Concerned this might be an issue that rears it's ugly head later or at some random time. We noted some KB docs about the issue recommending registry changes - we've reviewed and ensure these changes were made and still have the issue on the one machine.

Any thoughts?

  • 2
    The actual error message would be good. – Sam Cogan Feb 5 '11 at 20:15
  • @Sam: Bah... actual error message are irrelevant. Solving problems is all about wild speculation. >smile< (I am joking...) – Evan Anderson Feb 5 '11 at 22:58

W/o the actual error message it's fairly difficult to give an accurate diagnosis, but I'm going to invoke some psychic powers and see if I can come up with something useful for you.

I've had a couple of situations where fairly old Exchange 2003 installations had Outlook 2010 introduced and the users of Outlook 2010 reported problems sending messages. The root cause was that the named property quota had been reached on the Exchange 2003 server and Outlook 2010, requiring the ability to create some named properties, was failing in a very non-graceful manner.

Review the Application Event Log on the Exchange Server computer and look for event id 9667 from the source "MSExchangeIS". This error will show the details of the named property that Outlook 2010 is attempting to create.

You should do a couple of things:

  • You should install the hotfix described in this article and set the appropriate registry settings to prevent exhaustion of the named property quota with "promoted" Internet X-headers again.

  • Follow the steps outlined in this article to increase the named property quota.

This will permit Outlook 2010 to create the named properties it needs to function properly and will prevent future exhaustion of the named property quota by Internet X-headers being "promoted" into named properties.

You can read some good background about this the Exchange Team blog.

(As an aside, both Blackberry Enterprise Server and Microsoft's own ActiveSync also fail in non-graceful ways when not permitted to create named properties subsequent to their installation.)

  • Thanks for all the info Evan and sorry for the lack of specific error codes. You intuited correctly as the KB docs you referenced were indeed related to the issue. However, after much hear pulling one of our techs narrowed it down....it was the AVG 2011 Outlook Plug-In.... Needless to say that was eliminated from our master image going forward.... – FunctionOne Feb 7 '11 at 3:32

The cause of this issue turned out to be AVG 2011's Outlook Plug-In. When disabled Outlook returned to normal functionality.

Looked exactly like the issues we had researched and which Evan had so kindly shared above but it was actually AVG as the culprit.

Thanks Evan!

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.