3

Can we get more information/root cause whenever an item publishing fails apart from error message shown on Tridion UI. I want to write a custom code to get more information on error rather than checking log files.

6

Here are the logs which are helpful during publish and their configuration:

Event Viewer:
Tridion
Tridion Content Manager

Logfiles on CM/Publisher Servers:

%TridionHome%\log\TcmPublisher.log
%TridionHome%\log\cd_transport.log

LogFiles on Deployers:

cd_deployer.log
cd_core.log

Configuring logging level and their locations:

Modify the logback.xml under %TridionHome%\config on CM and Publisher servers to specify logging location and level

Modify the logback.xml under %httpupload%\bin\config on Deployer servers to specify logging location and level

Thus far I haven't felt a specific need to log what Tridion already logs in these logs. The information is sufficient to debug most issues. Also, templating logs are a place where you can hook in logs you want from your TBBs, since you want to log during publish.

| improve this answer | |
3

The information about root causes is to be found in various log files. Depending where something goes wrong, you will need to look either in the Windows event logs on the publisher server, the transport log, or in the logs of your upload application, such as the deployer log.

So actually, checking logs is what you'll need to do. The information will most likely be in there, although sometimes it helps to set the logging level to debug if you're troubleshooting something difficult. If you want to check them programmatically, there's nothing to stop you doing that.

| improve this answer | |
  • And if you make something funky, take a look at the alchemywebstore.com to write your customization in :) – user219 Jul 31 '15 at 8:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.