Frequently Asked Questions
Frequently Asked Questions
Import of replication fails instantly because of malformed index.xml
Posted by Zachary Wick (M-Files) on 28 June 2019 08:40 PM

Import of replication fails instantly because of malformed index.xml

Version 1.0 | Last Updated 5 March 2019

1     Overview / Work Notes

A one time import of a replication package fails instantly. The index.xml file is 5 MB big. This is much too big and should be more around 2 KB. The issue can be found if you open up the index.xml file with Notepad++. There are NULL characters appended and prepended to the file increasing the size and causing the import job to fail instantly. No root cause was found for why the NULL characters were there, but it appears to be an issue with transferring the file over FTP.

2     Solution / Workaround

There are two solutions here:

  1. Repeat the export job and verify that the index.xml file is of the appropriate size.
  2. Manually modify the index.xml file to remove the NULL characters and make the index.xml file valid.
(0 vote(s))
This article was helpful
This article was not helpful

Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments:
CAPTCHA Verification 
 
Please enter the text you see in the image into the textbox below. This is required to prevent automated registrations and form submissions.

Help Desk Software by Kayako case