# Error 110: root element expected

**URL:** <https://forum.xbench.net/t/error-110-root-element-expected/361>\
**Category:** Technical Support\
**Created:** [May 22, 2018, 10:23am UTC](https://forum.xbench.net/t/error-110-root-element-expected/361 "2018-05-22T10:23:54Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![RSL](https://avatars.discourse-cdn.com/v4/letter/r/bc8723/32.png) [@RSL](https://forum.xbench.net/u/RSL)\
**Post date:** [May 22, 2018, 10:23am UTC](https://forum.xbench.net/t/error-110-root-element-expected/361/1 "2018-05-22T10:23:54Z")

</div>

Hi all,  
When trying to upload a .xlf.docx file as XLIFF File, the following error appears:

Error 110: root element expected

I need some help to overcome this error, please.

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![Manuel](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.xbench.net/manuel/32/163_2.png) [@Manuel](https://forum.xbench.net/u/Manuel)\
**Post date:** [May 23, 2018, 4:49pm UTC](https://forum.xbench.net/t/error-110-root-element-expected/361/2 "2018-05-23T16:49:14Z")

</div>

Hi,

If I got it right, it is a Word document generated from a XLF file and hence it is like an uncleaned Trados .doc, .docx, or .rtf file with bilingual segments. Have you tried loading it as a Trados Word File instead of as a XLIFF file?

If that doesn’t work, try saving said DOCX file as a RTF and then loading it on Xbench.

Either way, wouldn’t it have been easier to work directly with the “original” XLF file in your favorite CAT tool instad of converting into a bilingual Word file?

Hope this helps!

---

<div class="post-metadata">

**Author:** ![RSL](https://avatars.discourse-cdn.com/v4/letter/r/bc8723/32.png) [@RSL](https://forum.xbench.net/u/RSL)\
**Post date:** [May 23, 2018, 6:22pm UTC](https://forum.xbench.net/t/error-110-root-element-expected/361/3 "2018-05-23T18:22:16Z")

</div>

Dear Manuel,  
Thank you very much for your answer!  
The file is generated as .xlf.docx file (I did not convert it nor did any formatting). This is the bilingual document one gets with CafeTran Espresso, this way (xlf.docx file), with no prior conversion from a different format.  
I tried to load it as a Trados Word File and, although it actually loaded it, the following error appears:

There are no bilingual segments to QA in the files or directories selected

I will try converting it to RTF file to see if it works, thanks again, Manuel.

---

<div class="post-metadata">

**Author:** ![Manuel](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.xbench.net/manuel/32/163_2.png) [@Manuel](https://forum.xbench.net/u/Manuel)\
**Post date:** [May 24, 2018, 7:11am UTC](https://forum.xbench.net/t/error-110-root-element-expected/361/4 "2018-05-24T07:11:42Z")

</div>

Morning, RSL,

OK, I barely know CaféTran nor how many people use it, but what do know is that this CAT software has been on the market for years and that there is a more than considerable number of people using it on a regular basis (with potentially a large amount of them using Xbench as well).

What I mean with this is that if the ApSIC guys have not created a specific file format for CT files so far and there have not been any specific requests to do so in this forum, it is probably because CT already offers an option to load their bilingual files on Xbench.

As a matter of fact, I did some quick searches out of curiosity and I found the following links that might help you with your problem (as well as with potential issues you might have when loading CT’s XLF on Xbench):

[https://cafetran.freshdesk.com/support/discussions/topics/6000054003](https://cafetran.freshdesk.com/support/discussions/topics/6000054003)

[https://groups.google.com/forum/#!topic/cafetranslators/O\_SLn\_hO3jc](https://groups.google.com/forum/#!topic/cafetranslators/O_SLn_hO3jc)

Hope it helps!

Have a nice Thursday,

---

<div class="post-metadata">

**Author:** ![RSL](https://avatars.discourse-cdn.com/v4/letter/r/bc8723/32.png) [@RSL](https://forum.xbench.net/u/RSL)\
**Post date:** [May 24, 2018, 7:34am UTC](https://forum.xbench.net/t/error-110-root-element-expected/361/5 "2018-05-24T07:34:26Z")

</div>

Thanks, Manuel!  
As a matter of fact, after posting this thread I checked that CT produces an XLF file (but got some other errors when loading it into Xbench) and got in touch both with CT and Xbench developers and none of them know or have tried to integrate both tools (although this might be tried in the near-middle future).  
I really appreciate your help and efforts, Manuel, thanks so much!

---

<div class="post-metadata">

**Author:** ![Manuel](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.xbench.net/manuel/32/163_2.png) [@Manuel](https://forum.xbench.net/u/Manuel)\
**Post date:** [May 24, 2018, 8:09pm UTC](https://forum.xbench.net/t/error-110-root-element-expected/361/6 "2018-05-24T20:09:52Z")

</div>

You’re welcome. I’m glad if I could be of any help. This forum is meant for us to help each other! 🙂

Sorry to hear that you still have problems with CT’s bilingual files ☹ .

Anyway, I’m sure both Igor Kmitowski and the ApSIC guys will eventually help you find a solution for your issue. I’ve only heard very positive things about CT developer and, if the ApSIC crew did find a way to load the strange MXLIFF files from Memsource on Xbench, I’m certain they will be more than able to help you in the short/mid-term with CT’s XLIFF files.

Have a good one!
