The SAD_ScSaveGatewayTrackingData function returns an 0x0000bf69 error

In Exchange 2000 Service Pack 3 (SP3), the SAD_ScSaveGatewayTrackingData function returns an 0x0000BF69 error when it is called from any process that is not running as LOCAL_SYSTEM on the target server. This function is called by gateways to pass message tracking event information back to Exchange 2000.

The following event may also appear in the application event log:

Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 5007
Date: 1/31/2004
Time: 3:29:59 PM
User: N/A
Computer: EXCHSRV1
Description: An error occurred during the message tracking decode operation. Function:ScSaveGatewayTrackingDataEx . <<0x80070005 - Access denied.>>

In Exchange 2000 SP3 and later, an extra check was inserted to make sure that only processes that are running as LOCAL_SYSTEM on the Exchange Server computer can use this API. This article includes a hotfix that provides a registry key that restores the original behavior.

Cumulative patch information

To resolve this problem, obtain the March 2003 Exchange 2000 Server Post-Service Pack 3 (SP3) Rollup. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Component: MAD

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. Note Because of file dependencies, this update requires Exchange 2000 SP3. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.

To configure the message tracking API from an account that is not a LOCAL_SYSTEM account:

1. Start Registry Editor.
2. Locate and then click the following key in the registry:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeSA\Parameters
3. On the Edit menu, click Add Value, and then add the following registry value:
   Value name: Allow Message Tracking DoS
   Data type: REG_DWORD
   Value data: 1
4. Quit Registry Editor.

If this value either does not exist or if it is set to 0, remote access to the API is denied and an 0x0000BF69 error is returned.