XFOR: Error 14 While Running Import in MS Mail

ID: Q215505

The information in this article applies to:

Microsoft Exchange Server, version 5.5

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

When a Microsoft Exchange Server computer is acting as a Microsoft Mail Directory Synchronization Server, you must perform the steps outlined in the following Microsoft Knowledge Base article to generate a Resync.glb file to synchronize MSMail requestors.

Q150976 XFOR: How to Create a Resync.glb File From an Exchange DSS

The user may receive the following error message on the MS Mail dirsync requester side when you run Import.exe to import the Resync.glb file.

Fatal error 14: "Error processing Resync.glb"

CAUSE

The problem occurs because DXA only pulls the highest IMPSEQ, SRVSEQ and REQSEQ numbers from the requesters you set in the registry when you follow the Microsoft Knowledge Base article Q150976.

RESOLUTION

To resolve this problem, obtain the latest service pack for Exchange Server version 5.5. For additional information, please see the following article in the Microsoft Knowledge Base:

Q191014 XGEN: How to Obtain the latest Exchange Server 5.5 Service Pack

The English version of this fix should have the following file attributes or later:

Component: Directory Synchronization

File name	Version
Dxa.exe	5.5.2524

WORKAROUND

To fix this problem, add the registry value below and use the Dxa.exe file from build 2524 or later. This fix will then allow DXA to pull the global highest IMPSEQ, SRVSEQ, and REQSEQ number when generating the Resync.glb file.

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

Start Registry Editor (Regedt32.exe).

Locate the following key in the registry:
```
      HKEY_LOCAL_MACHINE\SYSTEM\Currentcontrolset\Services\Msexchangedx
   
```
NOTE: The above registry key is one path; it has been wrapped for readability.

On the Edit menu, click Add Value, and then add the following registry value:


      Value Name: GlobalMaxSeqInResync
      Data Type:  REG_DWORD
      Value:      Default is 0

Quit Registry Editor.

If this value is present and set to 1 (TRUE), then at resync time, DXA will search for the highest IMPSEQ, SRVSEQ, and REQSEQ from amongst all the requestors that are registered on that DSS.

If this value is missing or set to 0 (FALSE), then DXA behaves as designed, that is, it only searches for the highest sequence numbers from the requestors that are asking for a resync.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 3.

Additional query words:

Keywords : exc55 EXC55SP3Fix
Version : winnt:5.5
Platform : winnt
Issue type : kbbug