FIX: The Mail Profile combo box is disabled when you use Enterprise Manager to view SQL Server agent properties, and you receive an error message when you try to use the xp_sendmail stored procedure from a DTS package in SQL Server 2000

This article describes the following about this hotfix release:

• The issues that are fixed by this hotfix package
• The prerequisites for installing the hotfix package
• Information about whether you must restart your computer after you install the hotfix package
• Information about whether the hotfix package is replaced by any other hotfix package
• Information about whether you must make any registry changes
• The files that are contained in the hotfix package

In Microsoft SQL Server 2000 Service Pack 3 (SP3), when you use Enterprise Manager to view SQL Server agent properties, the Mail Profile combo box that displays profiles is disabled. Additionally, when you try to use the xp_sendmail stored procedure from a DTS package, the operation may fail, and you receive an error message in the DTS package logs that is similar to the following: This problem occurs when you run all the following programs from the same server computer:

• SQL Server 2000 SP3 or SQL Server 2000 Service Pack 3a (SP3a)
• Microsoft Office Outlook 2000 or Outlook 2002
• Microsoft Exchange Server 2003

For a list of all publicly released SQL Server 2000 Post-Service Pack 3a hotfixes, see the following article in the Microsoft Knowledge Base:

When you install Exchange Server 2003, the Mapi32.dll file that is located in the System32 folder of the computer is updated to version 6.5.6944.0 from version 1.0.2536.0 or an earlier version. However, version 6.5.6944.0 of the Mapi32.dll file may not be compatible with MAPI functions such as the MAPILogon, MAPILogoff, and MAPISendMail functions. This incompatibility causes problems to occur with SQL Server Agent mail.

Note SQL Mail behaves as expected when you use version 6.5.6944 of the Mapi32.dll file.

Service pack information

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

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have Microsoft SQL Server 2000 Service Pack 3 (SP3) installed to apply this hotfix.

For more information about how to obtain SQL Server 2000 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry after you apply this hotfix.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

SQL Server 2000 32-bit versions

Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in SQL Server 2000 Service Pack 4.

For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the terminology that Microsoft uses when it corrects software after the software is released, click the following article number to view the article in the Microsoft Knowledge Base: