- Customer sees Publisher error such as "Waiting for Publish" and publishing a content item fails.

Administrator can enable Publisher debug logging by doing the following.  Note that Publisher debug logging is very verbose and will slow down the Publisher, also will fill up the hard drive... so it should not be enabled for an extended period.  It is helpful to minimize other Publisher traffic during this time.

To enable, do the following:
1. On CM server or Publisher server (if outscaled), go to the SDL Web Content Manager MMC > Publisher Settings, and see if "Activate logging of publisher actions" is set to true.   Change value to true if it is not.

2. If it is, then Publisher activity will be written to the TcmPublisher.log file in the %TRIDION_HOME%/log folder (this is hardcoded and cannot be changed), and review log after reproducing the offending publish action.
3. After the offending action is captured, disable Publisher logging.
4. Also review the Tridion Windows Event log, as often Publisher configuration issues will be logged there.


Alternatively, can do the following to debug Publisher from the command line.
http://blog.guusbeltman.nl/post/2017/12/23/tridion-publishing-in-debug-mode

Note that for Tridion Sites 9.0 and later product versions, the MMC is not available and Publisher debugging cannot be enabled this way.  For these product versions, see KB article For Tridion Sites 9.1, how to enable Publisher debugging?