Workaround:
Scenario 1: Remove all ampersands ('&') from the termbases file name and file path.
Scenario 2: Remove ampersands ('&') from the custom filter names in Multiterm Administrator > Public Objects
Note:The issue may also occur when using other XML entities below mentioned.