I am getting below error while I am trying to content porter from my DEVtridion to TEST tridion.

Unable to save Publication (tcm:0-230-1).
Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

Error Code:
0x8004033F (-2147220673)

Call stack:

If I see content portar logs, I can find these:

<tcm:Line ErrorCode="8004033F" Cause="true">
        <![CDATA[Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.]]>
    <tcm:Line ErrorCode="8004033F" Cause="false">
        <![CDATA[A database error occurred while executing Stored Procedure "EDA_PUBLICATIONS_FINDBPCONFLICTS".]]>

What could be the reason, why my content portar is not able to get sql connection of my TEST server, however same package is going perfectly on my LIVE Tridion.

  • What do you mean by DevTridion to Test Tridion? I guess you must be using the Content Porter Client installed on your personal machine and from there you are connecting; if it is otherwise, kindly clarify. Commented May 8, 2013 at 11:23
  • Yes...connecting from client only...DEV Tridion is my develpoment Tridion and Test Tridion is where I need to port my content from DEV Commented May 8, 2013 at 11:26
  • 1
    My guess is that Content Porter has nothing to do with it. Have you tried to update publication tcm:0-230-1 on your Test Tridion environment directly?
    – Quirijn
    Commented May 8, 2013 at 11:58
  • Is your Tridion CM and DB are on the same server machine or different machines? Also, are the Dev and Test servers (both CM and DB) are in same network domain or in different domain? Moreover, is it possible for you to log in to the Test Server CM machine and try running the Content Porter client from there and see if it works Commented May 8, 2013 at 12:04
  • @Quirijn, I am able to add/delete/update on my tcm:0-230-1, strangly same pacakge is working fine for LIVE Commented May 8, 2013 at 12:05

2 Answers 2


Following could be the reason:

  1. Health of your DB (or few tables in concern) is very low - Check the health of your Test DB by running DBCC commands and other maintenance script as mentioned in the SDL Tridion Manual for DB maintenance
  2. Ports for your DB are not open - Ensure by looking at the storage config/SDL Tridion Configuration manager, what is the actual DB id is and what is the port assigned to it. If it is different than the one assigned to the Dev DB, then ensure that it is open
  3. There may be issue with your SQL Server Network Configuration - Either you can compare the SQL Server Network Configuration by using SQL Server Configuration Manager for DEV DB and Test DB or you may seek help by reviewing through your DBA. Additionally, you may try running your Content Porter on the Test Server itself to check whether it works in this mode.
  • what about <![CDATA[A database error occurred while executing Stored Procedure "EDA_PUBLICATIONS_FINDBPCONFLICTS".]]> Commented May 9, 2013 at 7:26
  • I would not recommend, but if possible, try executing the EDA_PUBLICATIONS_FINDBPCONFLICTS stored procedure directly on the SQL Query Editor on the DB server with parameters for your scenario and few other scenarios and see if it gives you errors for all of them or only for your specific scenario...then check the DB logs or error that is presented on the SQL Query Editor, I hope that might give your more information to go forward in this issue Commented May 9, 2013 at 7:35

Ensure you configure these settings (absolutely necessary and from the manual):

2.4.2 Changing the timeout value for transactions

Content Porter allows users to perform a transactional import that Content Porter can roll back if it fails. As a Content Porter import can often take longer than the default system timeout setting of 30 minutes. it is recommended to change the default timeout to provide sufficient time for transactional import.


Changing the timeout depends on your installed versions of Content Manager:

  • On a machine which is running Content Manager Server version 2009 SP1, Content Porter uses the COM+ transaction timeout, as configured in Windows Component Services, to detect if a transaction times out. This timeout setting is set to 1800 seconds (30 minutes) by default.
  • On a machine which is running Content Manager Server version 2011 SP1, Content Porter uses .NET transactions as configured in the .NET Framework. This timeout setting is set to 10 minutes by default.

On a machine which is running Content Manager Server version 2011 SP1, change the .NET system transaction as follows:

a. Navigate to your %WINDIR%\Microsoft.NET\Framework \v4.0.30319\Config folder.

b. Open machine.config in a text editor.

c. Add the following section to set the maxTimeout to 1 hour:

   <machineSettings maxTimeout="01:00:00" />

d. Modify the System.Transactions section by setting the allowExeDefinition attribute (from MachineOnly) to MachineToApplication:

    <sectionGroup name="system.transactions" type="System.Transactions.Configuration.TransactionsSectionGroup,
 System.Transactions, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089, Custom=null">
   <section name="defaultSettings" type="System.Transactions.Configuration.DefaultSettingsSection,
 System.Transactions, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089, Custom=null" />
      <section name="machineSettings" type="System.Transactions.Configuration.MachineSettingsSection,
 System.Transactions, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089, Custom=null"
 allowDefinition="MachineOnly" allowExeDefinition="MachineToApplication" />

e. Reboot the server to apply changes.

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.