You receive an error message that states "The 'SendUsing' configuration value is invalid" when you use CDOSYS to send e-mail in Outlook 2002 (322338)

SYMPTOMS

If you use Collaboration Data Objects for Microsoft Windows 2000 (CDOSYS) to send mail from a computer that Outlook 2002 is installed on, you may receive the following error message:

Error Type: CDO.Message.1 (0x80040220)
The "SendUsing" configuration value is invalid.

CAUSE

This error occurs if the following conditions exist:

Your computer is running Microsoft Windows 2000 Server.
Either Outlook 2002 or Microsoft SharePoint Portal Server 2001 is installed on your computer.
Microsoft Exchange 2000 Server is not installed.
You are using CDOSYS to send mail, possibly using an Active Server Pages (ASP) page.
You do not use the CDO.Configuration object to set a smart host or port in your code.
The process that is running CDOSYS is running as an account that is not an administrator account. For example, if the process is running as an ASP page, the protection level is set to medium or high, which causes the code to run under the credentials of the IWAM_COMPUTERNAME account.

When you try to call the Send method, you receive the error message in the "Symptoms" section of this article.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack

The English version of this fix has the file attributes (or later) that are listed in the following table.

Component: Collaboration Data Objects (CDO)

File name	Version
Cdoex.dll	6.0.5770.96

WORKAROUND

To work around this problem, use one of the following methods:

Configure the Internet Information Services (IIS) Web page to run in "low" protection. This uses the credentials of the Inetinfo.exe process to run the ASP code.

-or-
Specify a smart host or port number before you send the message.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.