Knowledge Base

XADM: In Public Folder Replication, MIME Header Added on Top of Freedoc Content

Article ID: 309215

Article Last Modified on 2/28/2007

APPLIES TO

Microsoft Exchange 2000 Server Standard Edition

This article was previously published under Q309215

SYMPTOMS

If a conflict is generated during public folder replication, a Multipurpose Internet Mail Extensions (MIME) header is added on top of Freedoc content, eventually making the document unusable.

NOTE: You can drag a file from a folder directly into a public folder without attaching it to a post message through Microsoft Outlook. This type of item is known as a Freedoc. It resides in one of the Exchange 2000 folders, but is not attached to a message.

The MIME header is added to the document when the following sequence of events occurs:

You create a folder in an Exchange 2000 public folder, and then add at least one more server in the public folder replica list.
You copy a document to that folder by means of the Installable File System (IFS), and then wait for public folder replication to take place.
You modify the file at both ends, and then wait for replication to take place.

You will see a conflict in Outlook Web Access (OWA) and the file cannot be opened at the one of the replicas (the one that received the change first).

You open file with IFS; if the document is a text document, the following lines are the MIME header that is inserted at the beginning of the file:

MIME-Version: 1.0
Content-Type: application/octet-stream;
    name="myfile.txt"
Content-Transfer-Encoding: binary
Content-Description: myfile.txt
Content-Disposition: attachment;
    filename="myfile.txt"
X-MimeOLE: Produced By Microsoft Exchange V6.0.5677.0
X-MS-UrlCompName: myfile.txt

NOTE: The problem with opening the Freedoc occurs only with the IFS or the OWA client; a Messaging Application Programming Interface (MAPI) client such as Outlook opens the Freedoc in conflict without a problem.

RESOLUTION

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

301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack

After installing Exchange 2000 Service Pack 2, the conflict document extension is changed to .eml. This allows any e-mail client to open it.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 2.

MORE INFORMATION

If you use OWA to post a message and modify its file name from both ends, instead of copying the document to the folder with IFS, you get three copies of the same message (but no conflict):

Original message with URL: //server1/apptlh/myfolder/myfile.txt that cannot be opened: HHTP/1.1 423 Locked
Message with new name from server1: //server1/apptlh/myfolder/myfile-channged1.txt, that can be opened
Message with new name from server2: //server1/apptlh/myfolder/myfile-channged2.txt, that can be opened

The problem described in this article exists both with MAPI and non-MAPI (application top-level hierarchy) public folders. Also, the problem exists only when the document is opened from IFS or OWA. In some cases, OWA opens the file and displays that MIME header exactly as opened from Microsoft Windows Explorer (drive M). In other cases, OWA opens the conflict message itself, which is shown empty because OWA seems unable to show the two Freedocs in conflict as attachments, which it does for regular posted messages in conflict. As mentioned earlier, Outlook opens the Freedocs in conflict without a problem.

Keywords: kbbug kbexchange2000sp2fix kbnofix KB309215

Microsoft KB Archive/309215

Contents