Related to Max size of Content Porter Import and how can we increase it, I understand Content Porter uses the Core Service to export and import items between machines.

Is there any difference when running Content Porter on a local machine (i.e. laptop) versus on a DTAP (Dev, Test, Acceptance, or Production) server in terms of time outs?

Or in other words, can Content Porter use different Core Service endpoints based on where it runs? Based on below maybe we can configure a single endpoint for Content Porter?

The documentation describes a channel setting in the configuration:

Note that if you change this port number, you must also change the same value in the file web.config located in %TRIDION_HOME%\Content Porter\web\ImportExportService\. In that file, the port number is part of the URL in a url attribute in the following XML fragment:

  <wellknown type="comma-separated strings"
  url="http://localhost:50500/ProcessManager" />

The config "...also contains the Core Service client configuration for communication with the Content Manager. To configure the client, refer to the SDL Tridion platform documentation for more information."

Also when importing, does the size of the export package matter in terms of maxAllowedContentLength (IIS) and/or maxRequestLength (.NET)?


Based on Raj's answer and Bart's comment my misunderstanding was on the impact of the timeout settings. The package import, handled by .NET and IIS (and the above time out settings) is separate from the Core Service import/upload. See examples of the Core Service timeout settings in this separate answer.

1 Answer 1


maxAllowedContentLength matters because, your package is first uploaded on CMS machine, then import starts. i don't think timeout will differ as Package and ImportExportService exists on the same server in both cases.

  • So when Content Porter prepares the import package, is it the entire original export (ZIP) package regardless of what we select? Commented Jul 17, 2014 at 6:29
  • 1
    @AlvinReyes yes that is how the ImportExport service works indeed Commented Jul 17, 2014 at 7:05
  • Yes as @bart mentioned, entire CP package is uploaded & extracted @ contentporter\temp folder on server before actual import starts. then your selected items from that package is imported
    – Raj Kumar
    Commented Jul 17, 2014 at 7:38
  • Much clearer, thanks. Last point so it's clear for me: if the export package fails on import when remote to a target server, it would still fail if the export package was on the server, right? Does Content Porter use the Core Service (and the maxAllowedContentLength) for both creating the import package and then to make the items? I'll update the question with this comment thread. Commented Jul 17, 2014 at 17:10
  • 1
    As a follow-up, if doing a content port against, for example, localhost, you're still uploading "to the server" and the time-out settings in web.config for the Content Manager Explorer matter. Commented Dec 12, 2014 at 5:18

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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