Microsoft KB Archive/816508

From BetaArchive Wiki

Article ID: 816508

Article Last Modified on 10/26/2006



APPLIES TO

  • Microsoft Exchange 2000 Server Standard Edition




SYMPTOMS

Replication between your Microsoft Exchange Server 5.5 computer and your Exchange 2000 computer stops. In Exchange System Manager, you may see that many duplicate MS Type proxy addresses have been added to some Exchange objects.

When Internal Processing logging is enabled on the Exchange Server computer, you may receive the following error message:

DRAERR_JetError = 22
-1026 =0xFFFFFBFE JET_errRecordTooBig, Record larger than maximum size

CAUSE

This problem may occur on a network that has replication between an Exchange Server computer and an Exchange 2000 computer because when an object on the Exchange computers is accessed, the Recipient Update Service appends a duplicate MS Type proxy address to the object. When many addresses are added to the object, the object becomes too large for the replication service. This stops replication of the Exchange object.

RESOLUTION

Cumulative Rollup Information

To resolve this problem, obtain the September 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:

824282 September 2003 Exchange 2000 Server Post-Service Pack 3 Rollup


Hotfix Information

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

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone 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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Component: Recipient Update Service

The global version of this fix has the file attributes (or later) 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
   -------------------------------------------------------
   21-Mar-2003  17:15  6.0.6444.0     69,632  Ccmproxy.dll 
   21-Mar-2003  17:15  6.0.6444.0  2,109,440  Cdoexm.dll 
   21-Mar-2003  17:14  6.0.6444.0  8,466,432  Exadmin.dll 
   21-Mar-2003  17:16  6.0.6444.0  1,867,776  Exmgmt.exe 
   21-Mar-2003  17:16  6.0.6444.0     73,728  Inproxy.dll 
   21-Mar-2003  17:16  6.0.6444.0  2,969,600  Mad.exe 
   21-Mar-2003  17:14  6.0.6444.0  4,648,960  Maildsmx.dll 
   21-Mar-2003  17:16  6.0.6444.0     77,824  Pcproxy.dll 
   21-Mar-2003  17:16  6.0.6444.0     94,208  X400prox.dll

Note Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the article number below 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 the Microsoft products that are listed at the beginning of this article.


Additional query words: kbExchange2000preSP4septbarFix RUS

Keywords: kbhotfixserver kbqfe kbqfe kbfix kbexchange2000presp4fix kbbug KB816508