Print This FAQ

<<Back To Faq 4.2.7

Complete FAQ Listing

4.2 Namespace/COM/DLL Related Exceptions

4.2.1 Error loading type library/DLL.
4.2.10 "Could not access 'CDO.Message' Object - Part 8
4.2.11 "Could not access 'CDO.Message' Object - Part 9
4.2.12 "Could not access 'CDO.Message' Object - Part 10
4.2.13 "Could not access 'CDO.Message' Object - Part 11
4.2.2 The "SendUsing" configuration value is invalid.
4.2.3 The scary "Could not access 'CDO.Message' object"
4.2.4 "Could not access 'CDO.Message' Object - Part 2
4.2.5 "Could not access 'CDO.Message' Object - Part 3
4.2.6 "Could not access 'CDO.Message' Object - Part 4
4.2.7 "Could not access 'CDO.Message' Object - Part 5

* You Are Here *

Scroll To Answer

Discuss

4.2.8 "Could not access 'CDO.Message' Object - Part 6
4.2.9 "Could not access 'CDO.Message' Object - Part 7

4.2.7 "Could not access 'CDO.Message' Object - Part 5 Printer Friendly Email This FAQ Discuss

Ok, here is another gem. I hadn’t heard of this one before. It seems that the CDO.Message exception can also be thrown if you set MailMessage.Priority = MailPriority.High, and do NOT have ADO installed on the server.

It seems that the Priority property depends upon ADO. Kudos to CrystalTech, and David Good.

Here is the complete post regarding this tip.
http://dotnetjunkies.com/weblog/harpua/posts/5190.aspx#5799

Cheers!
Dave

The formatted version of this faq can be found at http://www.SystemWebMail.com/faq/4.2.7.aspx