Documentation Center

If publishing fails in the Transporting phase

Failure in the 'Transporting' phase typically indicates a configuration problem or a customization problem.

Possible explanations for a 'Transporting' failure are:

  • The transaction publishes to nonexistent or unreachable destinations. For example, a URL or FTP address was mistyped; the port configured is not open; or a secure transport was attempted without having imported a valid certificate on the system(s) that contain the Publisher(s).

  • You have a proxy server set up but failed to configure it in the Publication Target.

  • You do not have a Sender configured in your Transport Service configuration file cd_transport_conf.xml, located on your Content Manager server, for the protocol you are using.

  • You have create a custom Resolver, Rendered, Protocol Schema and/or Sender, but the code for these items is buggy or the customizations have not been set up properly. Consider deactivating these items and trying a publish without them.

  • Your file is too large and/or your connection is too slow to send out the Transport Package within the configured timeout period as configured in the SendTimeout attribute of the Senders element in your Transport Service configuration file, cd_transport_conf.xml, on the Content Manager server. This value (in ms) defaults to the value 60000.

    To resolve this issue, do one or more of the following:
    • Improve your connection speed
    • Increase the timeout value in your Transport Service configuration file, cd_transport_conf.xml.