12

As it is not possible to copy across publications, Just By renaming the publications for your operations you can do this. Mapping xml is also the option for this but renaming seems to be more comfartable. 1.Rename 04a --> temp 2.Create Content Porter Package 3.Rename temp --> 04a 4.Rename 04e --> temp 5.Import package in to temp 6.Rename temp -->...


10

Like premkumar subramanian's answer says, the logs raise an error on saving a publication item. Try importing with the Dependency Filters set to exclude everything. The dependency filter setting makes sure only those items which you select (the pages) are imported. This also means you need to make sure that all dependencies of the pages you are importing ...


9

There are some guidelines for configuring Content Porter for first time use in the SDL Tridion Live Content document here (login required). If you are using IIS 6 then you will need to change the metabase property called AspMaxRequestEntityAllowed As Bart says, if you are using IIS 7 then you need to increase the maxAllowedContentLength attribute. ...


9

You might first need to try the following. If you are running Content porter 2009 SP1 with Tridion 2011 SP1, you should consider the hotfix indicated HERE. Check if your Content porter server is started in your content manager box Initiate content porter from the content manager box (from the above I understand that it is Windows 2008 R2), you should not ...


9

You mention cd_licenses.xml but the TDSE object is specified in your error message, which sounds like it's from the Content Manager and you have also tagged Content Porter which, again, is on the Content Manager side. Did you also renew your license.xml file on your Content Manager? From the online documentation (requires login) cd_licenses.xml contains ...


8

In this situation, I generally recommend (do read the disclaimer ;) ) the following as a release / content refresh cycle: Ensure that the BluePrints really are the same in terms of inheritance and Publication Titles; Content Port system items from Dev to Stage from the top of the BluePrint down in separate Content Porter packages in the following ...


7

Indeed it is not a usual scenario, here some options. CM Side If you don't care about loosing the data in a lower environment, you can just restore a full database backup from a higher environment. You can rely on your database technology to synchronize data for instance SQL Server Integration Services. For this option you will need to get familiar with ...


7

The error message says that saving the Publication was not successful. But your objective was to port the pages. Pls. make sure that you selected only those items which you wanted to content port.


7

The Import Export API was introduced in Tridion 2013 SP1. Previous versions have to make use of Content Porter. See also this documentation page (requires login)


6

This appears to be similar to the SDL HTTP 401.1 error message might occur when accessing Template Builder Custom Page Knowledgebase article in which it recommends using 'Anonymous Authentication'. There are a couple things that you could check on top of what you have listed.... 1.Check that the 'Client' folder also has just 'Anonymous Authentication' ...


6

The simplest thing to try is doing a non-transactional import. The message seems to be indicating that the problem is to do with the transaction. If you really need to do transactional imports (we managed for years without them), then I'd suggest making smaller imports until you get down to a scope that succeeds. In any case, trying to identify the ...


6

What version of Content Porter are you trying to work with? If you're using Content Porter 2009 SP1 with Tridion 2011 SP1 HR1, then you will have this issue. CP 2009 SP1 is only good up to Tridion 2011 GA. For Tridion 2011 SP1, you need to be on CP 2009 SP2. Is it possible you grabbed the wrong installable from your company's archive? The CP 2009 SP1 ...


6

If you want to sync your Production environment back to Dev and Test and need it to be an exact copy, then the best thing you can do is make a backup of the Production CMS database and restore that on the Dev envrionment. The only thing you will miss at that point is the what is actually published (the published state is there, but the actual files on your ...


6

Have you removed the lock files after putting the new license in? Do a search for the lock files (search .ez* ) and remove all of them, then restart the server.


6

This is how I would go about resolving this: Write a CoreService app that looks through every component searching for fields containing a TcmUri; Convert that TcmUri to a WebDavUrl by loading the target object and getting it's WebDavUrl (some smart caching suggested here) Save/Update the components (probably before step #1) make sure my code still works ...


5

The maximum size you can import is really depending on two factors, #1 the requestLimits set, and #2 your network. The latter is not something which you can really set, some packages are just too large to be handled in a reasonable way over some networks. This should not be a problem if your network is setup correctly, so lets focus on #1 for now. You ...


5

I've seen this error when you are trying to import using one version of Content Porter but the Content Porter version on the server is different. Making sure these are matched up solved the problem.


5

In my experience with Content Porter it's nearly always something to do with Keywords... Double check your keywords and schemas have been imported into the correct level - (I'm assuming when you say you broke the export/import into chunks you mean schema/keywords, then design, then content, then website levels etc.)... Check you don't have any local ...


5

I have noticed that there are two different Tridion.Common.dll files. One exists in the GAC (if you are working on a tridion server), and one exists in the Content Porter installation folder (start->sdl tridion->content porter program folder) You'll see that the dll in the GAC has version 6.1.0.25, while the one in the CP folder has version 2.0.139.0. In ...


5

It looks like the content you are migrating is not in sync with the Schema it is based on. I would do a where used in the Schema the component is based on and check-out/check-in all the components to sync them up with the latest version of the schema. If you have event system or workflow, I recommend you disable them before going through this process. If ...


5

Basically whenever you see the message: The configuration file has been changed by another program. That is an indication that the config file has been changed but not all SDL Tridion services have been restarted after that change. The restarting of the services is required because at first start of a service it reads the configuration file and caches ...


5

The most important thing to understand about Content Porter is that it is just a tool, it cannot perform wonders, it just automates what you can manually do yourself. With the added benefit that it should in most cases be faster than copying all items over manually. The second most important thing to know about is what I like to call the "chicken and egg ...


5

Unfortunately, in your scenario (where for long time no sync has been done), in my experience I have never seen a error free porting with Content Porter unless you have kept all the details of changes in individual building blocks. For you first query - How are you planning to export/import components/pages/templates in a new folder? Per my knowledge, CP ...


5

in your statement I am just importing some pages in one publication at a time The error log indicates your settings are (at the very least) also attempting to import the respective Components (probably) attached to the Pages. Assuming you've considered the implications of 'creating' content in the parent Publication(s)... The line (Cause=true) The ...


5

You mention you have SDL Tridion version 2011 SP1 and you are trying to install Content Porter 2013. As listed in its release notes, Content Porter 2013 will work on the following SDL Tridion CMS versions: 2009 SP1 2011 SP1 Hotfix Release 1 (aka. 2013 SP1 HR1) 2013 So the error you got while trying to install Content Porter 2013 was correct, you seem to ...


5

Would you like to check if on the local environment where the things are working have this hot-fix applies - CP_3.1.0.75095 - Cumulative Hotfix. You can get more details about this hotfix HERE Apparently it seems to be a known issue with CP 2009 SP1 and in my case this issue got resolved once I applied the above said hot fix.


5

It seems conflict issue of older and new dlls. Restart your Tridion services and reset the IIS pool of SDL Tridion website. Please also refer below links MSDN StackOverflow


5

There are 2 ways you can approach this: 1: assuming your data model stays same in terms of schema, you can write custom content migration utility which will pick up data from an old version and then create components pages etc using core service with the data you want to migrate to the new version. 2: you can do an in-place upgrade to 2011 SP 1 first on ...


5

SOLVED! I don't know why, but one multimedia type has a repeated file extension (ttf,TTF), and this make the import to fail this way.


4

The usual scenario (with a DTAP - Dev, Test, Acceptance, Production, or similar set up) is to use Content Porter when moving towards P (Production) and database restores going the other way. Mostly you should be aiming to move things like Schemas, templates etc. with Content Porter. You can move content too, and this makes sense for things like layout images ...


Only top voted, non community-wiki answers of a minimum length are eligible