Salesforce

WorldServer 11.7.3 - how to avoid errors at "Segment Asset", "Save" or during the import of a Return package similar to Unable to find configuration: 'Default' (or other configuration names) for filter: 'HTML 5' or 'Plain text"

« Go Back

Information

 
TitleWorldServer 11.7.3 - how to avoid errors at "Segment Asset", "Save" or during the import of a Return package similar to Unable to find configuration: 'Default' (or other configuration names) for filter: 'HTML 5' or 'Plain text"
URL Name000019506
SummaryTo prevent these errors to happen (or to resolve them), the resolution to the errors is always to export and import the Embedded Content Processors and the File Types as objects and then import them back. This needs to be done only once, ideally directly after the upgrade to WorldServer 11.7.3.
Scope/EnvironmentWorldServer
Question
After the upgrade to WorldServer 11.7.3., customers have reported issues happening for some projects and files at Segment Asset or Save, or during the import of a Return package for projects created before the upgrade.

The error always mentions Unable to find configuration and points to configuration names that may vary. It could be the Default configuration or it could be a configuration with a specific name. The error also mentions a filter. It could be HTML 5 or Plain Text. Several versions of these errors have been documented in these articles:

WorldServer 11.7. - XML Task goes into Autoerror at "Segment Asset", "Save" or during the import of a Return package: Unable to find configuration: 'Default' for filter: 'HTML 5'
WorldServer 11.7.x - Task goes into Autoerror at Segment Asset or during import of Return package - Unable to find configuration: 'Embedded Content Plain Text v 1.0000 (ConfigurationNamexxx)' for filter: 'Plain Text')
WorldServer 11.7.x - XML Task goes into Autoerror at Segment Asset step: Unable to find configuration: 'Html Embedded Content 5 2.0.0.0 (AEM Content)' for filter: 'Embedded Content Html 5 Processor')

In some cases, the error is slightly different:

WorldServer 11.7.3 - Errors exporting projects to WSXZ packages and importing return packages ' Could not process FTS request'
Answer
To prevent these errors to happen (or to resolve them), the resolution to the errors is always to export and import the Embedded Content Processors and the File Types as objects and then import them back. This needs to be done only once, ideally directly after the upgrade to WorldServer 11.7.3. Please follow these steps:
 

In WorldServer, export File Type configuration and Embedded Content Processor as objects and import them right back

1- In WorldServer, go to Management > Administration > Export Objects, and in the Drop-down menu next to Object Type, select File Types

2- In the list of File Types, select these 3 Content Embedded Processors: 
HTML 5
Plain Text
Microsoft Excel 2007-2019. 


By selecting the upper level, you will export all configurations, including the Default ones for each of these Embedded Content Processors. As you can see below, the Embedded Content Processors are listed one below each other. The list might seem confusing because you will also find another instance of HTML 5 and Microsoft Excel 2007-2019: those are File Types that have the same names so make sure to select as displayed below:

User-added image

3- Scroll down to the bottom and click on Next

4- In the Export Options page, select the option Primary objects only and click on Export. The Export Object Definitions window will appear and a file called ExportObjectDefinitions.tml will be exported. This is the name assigned to the file automatically. In the Export Object Definitions window, click Ok. Save the TML file to your local computer.  Note: when saving it, you can change its name, but make sure to keep the extension *.tml.

5- Go to Management > Administration > Import Objects, click on Choose File, browse to the TML file that you have exported in step #4 and click Upload File

6- Now activate the File Type. If you click on the + sign to expand it, you will see the configurations you have exported and that you are about to import back. In the example below, only the Default ones were exported as there were no custom ones.  Click Next

User-added image

7- Select Primary Objects only, click Import, and Ok

User-added image


8- Go back to Management > Administration > Export Objects and select File Types in the Object Type list, and then export all the other file types except for the three you already exported.
Note: in case you have Legacy/Idiom Filters enabled in your environment, you should de-select those as well as they do not need to be exported and re-imported. (i.e, XML (NT) Filter, Office 2007 Filter, PPT Filter etc). 


User-added image

9- Scroll down to the bottom and click on Next

10- In the Export Options page, select the option Primary objects only and click on Export. The Export Object Definitions window will appear and a file called ExportObjectDefinitions.tml will be exported. This is the name assigned to the file automatically. In the Export Object Definitions window, click Ok. Save the TML file to your local computer.  Note: when saving it, you can change its name, but make sure to keep the extension *.tml.

11- Go to Management > Administration > Import Objects, click on Choose File to browse to the TML file exported in step 10. Select it and click on Upload File.

12- Your TML file is uploaded and the corresponding file type configurations will appear if you click on the + sign. Now select it and click Next

User-added image

13- Select again Primary Objects only and click Import. Click Ok to confirm the import.

User-added image

14- Now you have exported and imported back the Embedded Content Processor and the File Type configurations. The export/import operations will fix the issue.

15- If you have tasks in Autoerror, complete the Autoerror or repeat the action that was previously failing (like the Import of a Return package). The action will be successful.



 
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by