Salesforce

For the Web 8.5 Content Porter, administrator sees error Tridion.ContentManager.ImportExport.Packaging.OpenPackageException when moving large files

« Go Back

Information

 
TitleFor the Web 8.5 Content Porter, administrator sees error Tridion.ContentManager.ImportExport.Packaging.OpenPackageException when moving large files
URL Name000005835
SummaryWhen trying to import a large file in Content porter, we get an error :
12/4/2017 10:48:44 AM [Critical] Tridion.ContentManager.ImportExport.Packaging.OpenPackageException: Provided zip file c:\path\to\file\file.zip is not a valid ImportExport package.
at Tridion.ContentManager.ImportExport.Packaging.Package.Validate()
at Tridion.ContentManager.ImportExport.Packaging.Package..ctor(String packageLocation, String workingFolder)
at Tridion.ContentPorter.Presenters.SelectImportPackagePresenter.Validate()
12/4/2017 10:48:44 AM [Critical] Tridion.ContentPorter.Presenters.ValidationException: File c:\path\to\file\file.zip is not a package or package file is corrupted. ---> Tridion.ContentManager.ImportExport.Packaging.OpenPackageException: Provided zip file c:\path\to\file\file.zip is not a valid ImportExport package.
Scope/EnvironmentContent Porter 2013 / Content Porter Web 8.x
Question
How to configure Content Porter to allow large file import? 
Answer
These are the settings you should check for Content Porter:

1. Configuring IIS for large binaries:
http://docs.sdl.com/LiveContent/content/en-US/SDL%20Content%20Porter%20full%20documentation-v1/GUID-B9820F18-5DC9-46A6-B327-70C54036BF5B

As per the document, 209752100 refers to 200MB, for 2GB increase this value accordingly. If you don't find the web.config at "%TRIDION_HOME%\Content Porter\ImportExportService\", please make the change in "%TRIDION_HOME%\webservices\Web.config".

2. Transaction timeout in machine.config:

http://docs.sdl.com/LiveContent/content/en-US/SDL%20Content%20Porter%20full%20documentation-v1/GUID-D1C6115E-0E56-4153-9FE1-58E1D3DEE28F

3. Check the transaction timeout in Tridion.ContentManager.config:

<tridion.contentmanager>
...
<session transactionTimeout="3600" />
</tridion.contentmanager>

4. Also in Tridion.ContentManager.config, set the timeout on the <importExport> element:

<importExport maxProcessCount="1" workingFolder="
F:\Data\Tridion\ImportExport\Temp" processLogLocation="F:\Data\Tridion\log\ImportExport" transactionTimeout="3600" userReplyTimeout="3600">

5. In [TRIDION_HOME]\bin\TcmServiceHost.exe.config add a transactiontimeout <serviceTimeouts transactionTimeout="01:00:00" /> as below:

<configuration>
<system.serviceModel>
<behaviors>
<serviceBehaviors>
<behavior name="Tridion.ContentManager.ServiceHost.WindowsServiceHost.CoreServiceBehavior">
<serviceTimeouts transactionTimeout="01:00:00" /> <!-- ADD THIS NODE -->
<serviceMetadata httpGetEnabled="false"/>
<.../>
</system.serviceModel>
</configuration>

6. In [TRIDION_HOME]\webservices\Web.config add a transactiontimeout <serviceTimeouts transactionTimeout="01:00:00" /> as below:
<configuration>
<system.serviceModel>
<behaviors>
<serviceBehaviors>
<behavior name="Tridion.ContentManager.ServiceHost.IISHost.CoreServiceBehavior">
<serviceThrottling maxConcurrentSessions="100" maxConcurrentCalls="16" />
<dataContractSerializer maxItemsInObjectGraph="2147483647" />
<serviceMetadata httpGetEnabled="true" />
<serviceTimeouts transactionTimeout="01:00:00" /> <!-- ADD THIS NODE -->
<.../>
</system.serviceModel>
</configuration>

Save the files, restart all Tridion services, COM+ and IIS and then test again.

Also see KB article In Tridion Sites 9.1, how to modify various settings to extend core service timeouts

 
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by