Import error - SiteRootCreationSettings

Szymon Mosiolek asked on March 6, 2017 11:52

Hi,

I try with different configuratons to import site but always get error "SiteRootCreationSettings" below is full error log for import.

Is something wrong with my setting or just Kentico is corupted?

ERROR: Error during import process Message: Value cannot be null. Parameter name: settings

Exception type: System.ArgumentNullException Stack trace: at CMS.DocumentEngine.TreeProvider.CreateSiteRoot(SiteRootCreationSettings settings) at CMS.DocumentEngine.DocumentImport.CreateSiteRoot(SiteImportSettings settings, DataSet dsDocuments, TreeProvider tree) at CMS.DocumentEngine.DocumentImport.ImportDocuments(SiteImportSettings settings, TranslationHelper th, List1& importedDocumentIDs, TreeProvider tree) at CMS.DocumentEngine.DocumentImport.ImportDocumentsData(SiteImportSettings settings, TranslationHelper th) at CMS.DocumentEngine.DocumentImport.ImportObjectTypeBefore(Object sender, ImportDataEventArgs e) at CMS.Base.AbstractHandler.CallEventHandler[TArgs](EventHandler1 h, TArgs e) at CMS.Base.AbstractHandler.Raise[TArgs](String partName, List1 list, TArgs e, Boolean important) at CMS.Base.AdvancedHandler2.RaiseBefore(TArgs e) at CMS.Base.AdvancedHandler2.RaiseBefore(TArgs e) at CMS.Base.AdvancedHandler2.StartEvent(TArgs e, Boolean allowEvent) at CMS.CMSImportExport.ImportProvider.ImportObjectType(SiteImportSettings settings, String objectType, Boolean siteObject, TranslationHelper th, ProcessObjectEnum processType, List`1 importedParentIds) at CMS.CMSImportExport.ImportProvider.ImportObjectsDataInternal(SiteImportSettings settings)

ERROR: Error importing pages Message: Value cannot be null. Parameter name: settings

Exception type: System.ArgumentNullException Stack trace: at CMS.DocumentEngine.TreeProvider.CreateSiteRoot(SiteRootCreationSettings settings) at CMS.DocumentEngine.DocumentImport.CreateSiteRoot(SiteImportSettings settings, DataSet dsDocuments, TreeProvider tree) at CMS.DocumentEngine.DocumentImport.ImportDocuments(SiteImportSettings settings, TranslationHelper th, List`1& importedDocumentIDs, TreeProvider tree) at CMS.DocumentEngine.DocumentImport.ImportDocumentsData(SiteImportSettings settings, TranslationHelper th)

ERROR: Error creating root of the site. Message: Value cannot be null. Parameter name: settings

Exception type: System.ArgumentNullException Stack trace: at CMS.DocumentEngine.TreeProvider.CreateSiteRoot(SiteRootCreationSettings settings) at CMS.DocumentEngine.DocumentImport.CreateSiteRoot(SiteImportSettings settings, DataSet dsDocuments, TreeProvider tree)

Correct Answer

Mark Bognar answered on March 20, 2017 19:30

I had the same issue. I've installed Kentico with no sites and when importing a site from another install the same Error message was displayed. (Kentico 10)

Solution:

  1. I had to create a new site in the sites module with the New site wizard. (Note: I set the site display name and code name to what I was importing.)
  2. When importing I pointed to the newly created (blank) site by selection Import objects into an existing site option.
1 votesVote for this answer Unmark Correct answer

Recent Answers


Trevor Fayas answered on March 6, 2017 15:07

Are you importing on an initial site creation, or trying to import into an existing site?

0 votesVote for this answer Mark as a Correct answer

Szymon Mosiolek answered on March 6, 2017 15:09

I installed fresh Kentico without any site in it and try import site to be first in new system

1 votesVote for this answer Mark as a Correct answer

Chetan Sharma answered on March 7, 2017 12:44

Well you could try installing one of the starter sites using Kentico's web templates and see if the installation was correctly done.

If that goes well then it could be case that your package is corrupt.

0 votesVote for this answer Mark as a Correct answer

Greg Woz answered on September 12, 2017 10:52 (last edited on September 12, 2017 10:57)

I experienced the same problem. When I installed Kentico 10, first thing I did was to change the Global Settings of all projects. I switched default Culture to Polish and changed SEO options to use Alias instead of Document Root. Then I experienced the problem.

I managed to solve it by reverting the global settings to default as they were after installation. Then the import went well. No more issues.

I suggest to set English - United States (don't set Default culture for Global settings because master template will throw an error)

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.