Web developers wiki ASP.NET Sitecore Sharepoint Kentico by Evident Interactive

Kentico: site import produces an empty site

Modified: 2012/06/06 12:30 by vanthoog - Categorized as: Kentico
The following applies to Kentico v5.5 R2. It probably also applies to previous versions, although this has not been tested. At this point in time it is unknown whether it applies to v6.0 or not.

Suppose you have a Kentico installation containing multiple sites. Suppose you have created a new site (using existing templates, i.e. without changing any code) on a test environment and you are going to migrate this site to the production environment by using Kentico’s export/import feature.

When you do the import on the production environment, one of the following happens.

Scenario 1: The following error messages are returned at the end of the import process:

ERROR: Error importing 'Document relationships' objects (cms.relationship 0)
Message: ImportProvider.UpdateObject: Cannot translate columns 'LeftNodeID;RightNodeID', import the dependent objects first. Stack Trace: at CMS.CMSImportExport.ImportProvider.UpdateObject(SiteImportSettings settings, IInfoObject infoObj, Boolean siteObject, DataSet ds, TranslationHelper th, Boolean updateChild, Int32 targetSiteId, ProcessObjectEnum process, Hashtable importedParentIDs, ArrayList postProcessList)
at CMS.CMSImportExport.ImportProvider.ImportObjects(SiteImportSettings settings, DataSet ds, String objectType, Boolean siteObjects, TranslationHelper th, Boolean importChild, ProcessObjectEnum processType, Hashtable importedParentIDs)

ERROR: Error importing documents
Message: ImportProvider.UpdateObject: Cannot translate columns 'LeftNodeID;RightNodeID', import the dependent objects first. Stack Trace: at CMS.CMSImportExport.ImportProvider.ImportObjects(SiteImportSettings settings, DataSet ds, String objectType, Boolean siteObjects, TranslationHelper th, Boolean importChild, ProcessObjectEnum processType, Hashtable importedParentIDs)
at CMS.CMSImportExport.ImportProvider.ImportObjectType(SiteImportSettings settings, String objectType, Boolean siteObject, TranslationHelper th, ProcessObjectEnum process, Hashtable importedParentIDs)
at CMS.CMSImportExport.ImportProvider.ImportDocumentsData(SiteImportSettings settings, TranslationHelper th)

Scenario 2: No error message is returned by the import process but the imported site contains only one document being the root document.

This problem is caused by the fact that the root document of the site is missing from the export file. You can check this by performing the following steps:
1. Unpack the export file (which is a normal zip-file).
2. Go to the folder “Data\Documents”.
3. Open the file “cms_document.xml.export”, which is a xml-document.
4. Look for a node called “”. It is usually the last node in the xml-document. If this node is missing, it is the cause of this problem.

To solve this problem the export-file must be recreated in such a way that the root document is included. To do this perform the following steps:
1. Go to test environment.
2. Go to “Site manager” – Development – “Document types” – Root.
3. Click on the tab “Sites”.
4. Add your site to the list.
5. Recreate the export-file.

Now, when you import this export-file on the production environment, the complete site including all documents will be imported.

 © Evident Interactive BV