Salesforce

WorldServer 11.7.x - error when importing an *. sdlftssettings file 'The referenced embedded content doesn't exist in the system. Please import the embedded content first or adjust your configuration settings.'

« Go Back

Information

 
Article TypeSolution Article
Scope/EnvironmentSDL WorldServer
Symptoms/Context
We have exported a Custom XML (Embedded Content Processor) file type configuration from our WorldServer 11.7.x environment and we have made some changes in Trados Studio. When we try to import the changed Studio configuration file (*.sdlftssettings), we receive this error:

The referenced embedded content doesn't exist in the system. Please import the embedded content first or adjust your configuration settings.

User-added image
Resolution
If you want to modify a Custom XML (Embedded Content Processor) file type configuration that uses a specific processor (with a specific name and configuration, not the default one), make sure to follow the steps described in this article:

How to modify a Custom XML (Embedded Content Processor) File Type configurations where an embedded content processor is used starting from WorldServer 11.7?

 
Root Cause
In order to modify a Custom XML (Embedded Content Processor) file type configuration where in the Embedded content section, the option Process embedded content using the following processor is enabled and a specific processor is selected/activated, it is important to first export the relevant embedded content processor from WorldServer, import it into Studio and then export the file type configuration. If this is not done, after importing the *. sdlftssettings file into Studio, if you go to the Embedded content section of the file type configuration, you will see the reference to the processor, but you will also see that Studio marks it as Not Available.
Here is an example of how this would look like:

User-added image

Because of this issue, importing the *.sdlftssettings file back to WorldServer will fail with the error.
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by