Appendix A: Solving common problems 

We recommend that you monitor publishing jobs closely on a daily basis to correct problems with published documents or the publishing job configurations. This monitoring is needed because the Publisher depends on predictable behavior from third-party applications that are used in the rendering process.

In certain situations or for certain documents, it is possible that a third-party application may behave unexpectedly. This can result in the application waiting for additional user input. In these situations, you should stop the application and ensure that Dex.exe is still working properly.

Publisher does not automatically resubmit failed publishing jobs. You must manually resubmit failed publishing jobs as described in the BlueCielo Publisher User's Guide.

If resubmitting a publishing job repeats the problem, you might need to manually render the document while you troubleshoot the rendering problem. To prevent the Publisher from rendering the same document again (and repeating the problem), you can mark its registration in the Publisher database as obsolete as described in the BlueCielo Publisher User's Guide.

For help resolving common publishing and rendering problems, do the following in the order listed:

1. Examine the feedback property (if configured) of the failed documents for error messages.
2. Examine the document's registration in the Publisher queue as described in the BlueCielo Publisher User's Guide.
3. Examine the Publisher window during publishing job execution for errors as described in Monitoring a publishing job.
4. Examine the Publisher log files for errors as described in Viewing the Publisher trace logs.
5. Examine the Windows Application log in the Event Viewer for error messages.