Documentation Center

If publishing fails after the Transporting phase

A publish transaction that manages to reach the 'Preparing for Deployment' phase and beyond has succeeded in sending a Transport Package across the wire to one or more destinations. You can try to deploy this Package in another environment.

By setting the Cleanup attribute to false in the WorkFolder element in your Transport Service configuration file, cd_transport_conf.xml, you can prevent your Transport Package (a zip file) from being deleted after it has been sucessfully sent to the destination(s).

You can then take the Transport Package and try to deploy it in a different environment. For example, if publish is failing in a production environment, you might want to try deployment in a development environment. If that deployment succeeds, the problem is in a difference between the two environments.

Overall ways of dealing with publish failures in the deployment phases of the publish pipeline are:
  • Check the configuration files for the Content Deployer and the Storage Layer on your deployment system. Typical configuration problems include different configuration files in different environments, and different Storage Layer configuration files in different places in the deployment/Content Delivery system.
  • Check your logs. By default, the Logback logging system creates individual logs for the individual parts of Content Delivery, such as the Content Deployer log, cd_deployer.<TIMESTAMP>.log, as well as one overall log called cd_core.<TIMESTAMP>.log containing all those logs.