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 created a custom Resolver, 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
SendTimeoutandHttpConnectionTimeoutattributes of theSenderselement in your Transport Service configuration file, cd_transport_conf.xml, on the Content Manager server. This attribute value (in ms) defaults to the value 60000 in both cases. RWS recommends that you keep the timeouts as low as possible and never make your timeouts longer than 8 minutes (value 480000).To resolve this issue, do one or more of the following:- Improve your connection speed
- Increase the timeout value for each attribute in your Transport Service configuration file, cd_transport_conf.xml.
- The Transport Service is timing out connecting to the Discovery Service. This might happen if you are publishing a large volume of content, even in an outscaled setup (with multiple Content Deployer workers, multiple Publishers, or both). If this happens, open cd_storage_conf.xml in the Discovery Service configuration location for editing, and within the
DataSourceelement, add the following newPropertysubelement:<Property Name="loginTimeout" Value="120" />