If the Automation Engine OBGE cannot prepare view files for a file uploaded to WebCenter, the document will not get a thumbnail and the checking and registering failed icon will be displayed next to the document. This article describes how to troubleshoot a failed View Generation in WebCenter.
If the checking and registering does not fail, but remains pending, read this article to troubleshoot your issue:
To learn more about the reason why checking and registering failed, follow these steps:
Click the Document Name to go to the Document Details > click the Action History tab.
In the Action History table, the event View Generation is listed. It shows a line Check and register with a date and time.
In the Comment column, you can check whether the Prepare for Viewing task on the Automation Engine OBGE finished successfully or not.
Next to the status, there is a Show Task Details link. Click the link to see more details about why your task failed.
If the previous step did not provide sufficient information, launch the Automation Engine Pilot and connect to your OBGE server.
Upload the same file again in WebCenter, you should now see a new Prepare for Viewing task being launched on the OBGE server.
Whenever a task fails, inspect the Automation Engine log file.
If you did not find the answer yet, read through the Common issues below to check if any of them describes your specific problem. If this still does not help you, please contact our Support Organization. In your communication, include the WebCenter Task Details and the Automation Engine OBGE Prepare for Viewing task log file to enable us to help you more efficiently.
Verify whether the Automation Engine OBGE is in fact installed and configured correctly. For more details, check our Installation Guide.
Make sure that the BGMD service is started on the Automation Engine OBGE Server and verify that the JDF Hot Folder for the WebCenter FileStore is started. When in doubt, try (re)starting.
The Automation Engine OBGE cannot handle .jpg or .jpeg files with progressive compression. The WebCenter Task Details will show a message that indicates the file type is not supported: "The file is either damaged or not supported."
More detailed information can be found in the Automation Engine OBGE task log.
If you uploaded a progressive .jpg, resave it without the progressive compression and upload it again.
Any graphics file you upload needs to be self-containing. If fonts are not embedded, the Task Details will show: Substitution font <FONT NAME> can not be found and Font <FONT NAME> could not be parsed. For more information on this specific issue, see:
You uploaded a .zip file as Graphics, but one or more of the files inside the ZIP package contain a special characters such as an ampersand (&). To resolve the issue, rename the file(s), create a new .zip file and upload this as a new version.
UNC FileStore Path
During installation, the location of the FileStore folder needs to be specified using an UNC path (for example: \\COMPUTERNAME\FileStore). Make sure it does not point directly to a local drive.