Microsoft KB Archive/329773

= The SAD_ScSaveGatewayTrackingData function returns an 0x0000bf69 error =

Article ID: 329773

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Exchange Server 2000 Service Pack 3

-



This article was previously published under Q329773





SYMPTOMS
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.>>



CAUSE
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:

813840 March 2003 Exchange 2000 Server Post-Service Pack 3 Rollup

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 Exchange 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:

http://support.microsoft.com/contactus/?ws=support

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.

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.   Date         Time   Version            Size    File name --  09-Oct-2002  18:29  6.0.6341.0         69,632  Ccmproxy.dll 09-Oct-2002 18:28  6.0.6341.0      8,450,048  Exadmin.dll 09-Oct-2002 18:30  6.0.6341.0         73,728  Inproxy.dll 09-Oct-2002 18:30  6.0.6341.0      2,969,600  Mad.exe 09-Oct-2002 18:29  6.0.6341.0      4,644,864  Maildsmx.dll 09-Oct-2002 18:30  6.0.6341.0         77,824  Pcproxy.dll 01-Aug-2002 06:37  6.0.6300.1         84,480  Spuninst.exe 09-Oct-2002 18:30  6.0.6341.0         94,208  X400prox.dll 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:

301378 How to obtain the latest Exchange 2000 Server service pack



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



MORE INFORMATION
To configure the message tracking API from an account that is not a LOCAL_SYSTEM account:  Start Registry Editor. Locate and then click the following key in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeSA\Parameters

 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

 Quit Registry Editor.</li></ol>

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.

Additional query words: kbExchange2000preSP4marchbarFix XADM

Keywords: kbhotfixserver kbqfe kbbug kbexchange2000presp4fix kbfix kbqfe KB329773

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.