Automation Core error messages during processing
To be able to execute the automation, the system expects a Publish XML file containing all settings. This file could not be located, read or parsed. Is it present, not locked, a valid XML file, … ?
To be able to execute the automation, the system expects a Publish XML file containing all settings. This file could not be parsed. Is it a valid XML file?
To be able to execute the automation, the system expects a Publish XML file containing all settings. This file could not be read or parsed. Is it not locked and a valid XML file, … ?
A Publish configuration can be configured to use information from a trigger file. However, the XML trigger file could not be read.
A Publish configuration can be configured to use information from a trigger file. However, the CSV trigger file could not be read or parsed.
A Publish configuration can be configured to use information from a trigger file. However, the CSV trigger file could not be read or parsed because de CSV column separator is not filled in in the publish XML file.
The automation requires at least one main workspace folder. There is no main workspace name filled in in the publish XML file.
The system could duplicate the main workspace folder. Does the workspace exists in the workspaces folder? Does the name match the name configured in the publish script?
The EasyCatalog plugin on the server was not able to set main workspaces root folder. Does it exist?
The EasyCatalog plugin on the server was not able to load the main workspace. Does it exist?
The main data file, used to connect to the main workspace, could not be located. Is the file missing? If a fixed data file path is configured in the publish XML file, make sure the file can be accessed.
The EasyCatalog plugin on the server was not able to connect the workspace to the configured datasource. Make sure the file can be accessed.
The EasyCatalog plugin on the server was not able to synchronise the datasource with the workspace.
The EasyCatalog plugin on the server was not able to purge any deleted records in the workspace.
The main workspace could not be loaded on the server.
The EasyCatalog plugin on the server was not able to create/load a view for the configured workspace.
The additional workspace could not be loaded because it is marked as invalid.
The additional workspace could not be loaded. Does it exist? Does the name of the workspace math with the configuration in the publish configuration?
The additional workspace could not be loaded. Does it exist? Does the name of the workspace math with the configuration in the publish configuration?
The server could not duplicate template file. Does it exist? Does the name of the template file match with the configuration in the publish configuration? Is it locked?
The template name is missing in the publish configuration.
The server could not duplicate the library file. Does it exist? Does the name of the library file match with the configuration in the publish configuration? Is it locked?
The library file name is missing in the publish configuration.
The EasyCatalog plugin on the server was not able to modify the workspace field content.
The server could not modify the configured workspace file. The configured file is missing.
The EasyCatalog plugin on the server was not able to close the dataview.
The EasyCatalog plugin on the server was not able to purge/delete the workspace.
The server could not delete the temporary workspace folder.
The server was not able to duplicate the workspace configuration file.
The server could not duplicate the workspace config file. The name is not present in the publish configuration.
The EasyCatalog plugin on the server was not able to apply the configuration on the workspace.
The configured workspace configuration file is missing.
The configured pagination file is missing.
The EasyCatalog plugin on the server was not able to apply the template file path pagination option.
The EasyCatalog plugin on the server was not able to apply a pagination option.
The server was not able to delete a file.
The EasyCatalog plugin on the server encountered an error during the pagination process.
The EasyCatalog plugin on the server was not able to apply the pagination option.
The server encountered an error while running an external javascript.
The server could not run the external javascript. The configured script is missing.
The server encountered an error while running an external script.
The server could not run the external script. The configured script is missing.
The configured script is not supported on the server OS and could not be executed.
The configured script is not supported on the server OS and could not be executed.
The configured script is not supported on the server OS and could not be executed.
The configured script is not supported on the server OS and could not be executed.
The EasyCatalog plugin on the server encountered an error during the pagination process.
The server could not paginate the data onto the page. The configured target text frame is missing.
The EasyCatalog plugin on the server encountered an error during the pagination process.
The configured EC library file seems to be missing. Is the name correct?
The EasyCatalog plugin on the server encountered an error during the pagination process.
The configured EC library file seems to be missing. Is the name correct?
The EasyCatalog plugin on the server encountered an error during the pagination process.
The configured EC library file seems to be missing. Is the name correct?
The configured pagination type is not supported in the scripting. Currently only types 0,1,2,4 and 7 are supported.
The server failed to export the result as PDF-file. The target folder doesn’t exist or is missing.
The server failed to export the result as PDF-file. The target folder is not configured in the publish configuration.
The server failed to export the result as PDF-file. The PDF preset is not configured in the publish configuration.
The server failed to export the result as PDF-file. The name for the PDF-file is not configured in the publish configuration.
The server failed to export the result as PDF-file. The name for the PDF-file is not configured in the publish configuration.
The server failed to export the result as PDF-file. The configured PDF-preset is missing.
The server failed to save the result as Indesign-file. The target folder doesn’t exist or is missing.
The server failed to save the result as Indesign-file. The “make unique” property is empty or missing in the configuration.
The server failed to save the result as Indesign-file. The target folder property is empty or missing in the configuration.
The server failed to save the result as Indesign-file. The “make unique” and/or “target folder” path property is empty or missing in the configuration.
The server failed to save the result as Indesign-file. The name for the Indesign-file is not configured in the publish configuration.
The server failed to save the result as Indesign-file. An error occurred. Have the server and target location enough free space?
The server failed to create a package. An error occurred. Have the server and target location enough free space?
The server failed to create a package. The target folder doesn’t exist or is missing.
The server failed to create a package. The target folder doesn’t exist or is missing.
The server failed to create a package. The name for the package is not configured in the publish configuration.
The server failed to export the result as JPEG-file. The target folder doesn’t exist or is missing.
The server failed to export the result as JPEG-file. The “make unique” property is empty or missing in the configuration.
The server failed to export the result as JPEG-file. The target folder property is empty or missing in the configuration.
The server failed to export the result as JPEG-file. The “make unique” and/or “target folder” path property is empty or missing in the configuration.
The server failed to export the result as JPEG-file. The name for the JPEG is not configured in the publish configuration.
The server failed to export the result as JPEG-file. The name for the JPEG is not configured in the publish configuration.
The server failed to export the result as JPEG-file. Target JPG file already exists but can’t be deleted.
The server failed to export the result as JPEG-file. Have the server and target location enough free space?
The server failed to export the result as PNG-file. The target folder doesn’t exist or is missing.
The server failed to export the result as PNG-file. The “make unique” property is empty or missing in the configuration.
The server failed to export the result as PNG-file. The target folder property is empty or missing in the configuration.
The server failed to export the result as PNG-file. The “make unique” and/or “target folder” path property is empty or missing in the configuration.
The server failed to export the result as PNG-file. The name for the PNG is not configured in the publish configuration.
The server failed to export the result as PNG-file. Target PNG file already exists but can’t be deleted.
The server failed to export the result as PNG-file. An error occurred. Have the server and target location enough free space?
After applying the configuration on the dataview, no rows are present. De result does not contain any data which can be used for paginating the document.
The server could not locate the template file. Does it exist? Does the name of the template file match with the configuration in the publish configuration?
The server could not remove the workspace lock of an additional workspace.
The server could not remove the workspace lock of an additional workspace. The max. attempts have been reached.
The server could not use the additional workspace. The max. attempts have been reached. The lock file is still present.
The server could not copy a file. Is the file locked?
The configuration contains a JSON variable, but the configuration also disables the reading and parsing of the JSON file. Please resolve this conflict. Don’t use a JSON variable or enable the JSON parsing in the publish configuration.
The configuration contains a XML variable, but the configuration also disables the reading and parsing of the XML file. Please resolve this conflict. Don’t use a XML variable or enable the XML parsing in the publish configuration.
The configuration contains a CSV variable, but the configuration also disables the reading and parsing of the CSV file. Please resolve this conflict. Don’t use a CSV variable or enable the CSV parsing in the publish configuration.
The EasyCatalog license is no longer valid on the server, but the serial number is also missing in the publish configuration. Auto activation can’t be executed.
The EasyCatalog license is no longer valid on the server, and could not be activated.