Hi Zac,

I assume you are using the free version? Does the error only occur in the UmbracoLog table or is the error shown also? It could be in the free version that I try to get the parent to determine the document location, sinc I don't specify the parent it could be that you get this error in the logfile. I will sure fix this for the next service release.

If the importer reports that you got errors during the import I'm curious about your datasource structure. Does it include a column name "Parent" in that case? And if so does it help when you change that to a different name "ParentColumn" for instance?

I'm really curious why this happens so hope to hear from you.

Thanks,

Richard

Hi Richard,

  Thanks for the quick response.  I am using the free version (was testing it prior to buying).

  There is an error that displays on the import page that says to check the umbraco log but doesn't provide any details (no rows are imported).  

  The datasource import is very simple (and doesn't include anything named parent or any other umbraco field names).  We're basically importing node name and state.

  If you have a money back guarantee on the CMSImport, I'll try the paid version but am apprehensive since the free version won't do anything for me currently.

Thanks

Zac 

Hi Zac,

Thanks for your answers. Weird just did an import to be sure and didn't get these errors on the free edition. I assume you are using Sql Server also. If so I assume you have the following tables in your database:

• CMSImportCustomRelation
• CMSImportMediaRelation
• CMSImportRelation
• CMSImportScheduledItems
• CMSImportScheduledTask
• CMSImportState

If so I'm very curious about your datasource. If it would be possible to send this to richard[at]soetemansoftware[dot]nl I can have a look? The Umbraco Deli (Marketplace) gives you a 14 day money back guarantee but I much rather give great support :)

Thanks,

Richard

Hi Richard,

  I just sent you an email with full error details.  Let me know if you have any questions.  

Thanks

Zac

Sae thing here. I'm also using free version. Same answers as above. Here's the log:

Error during load umbraco.DataLayer.SqlHelperException: Umbraco Exception (DataLayer): SQL helper exception in ExecuteReader ---> System.Data.SqlClient.SqlException: Invalid column name 'parent'. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at umbraco.DataLayer.SqlHelpers.SqlServer.SqlServerHelper.ExecuteReader(String commandText, SqlParameter[] parameters) at umbraco.DataLayer.SqlHelper`1.ExecuteReader(String commandText, IParameter[] parameters) --- End of inner exception stack trace --- at umbraco.DataLayer.SqlHelper`1.ExecuteReader(String commandText, IParameter[] parameters) at CMSImportLibrary.DAL.State.(Guid ) at CMSImport.Controls.ImportSteps.ConfirmSelectedOptions.(StringBuilder , Guid ) at CMSImport.Controls.ImportSteps.ConfirmSelectedOptions.(ImportState ) at CMSImport.Controls.ImportSteps.ConfirmSelectedOptions.InitializeState(ImportState state) at CMSImport.Controls.ImportSteps.ConfirmSelectedOptions.InitializeStepControl(ImportState state) at CMSImport.Controls.CMSImport.() at CMSImport.Controls.CMSImport.(Int32 ) at CMSImport.Controls.CMSImport.OnPreRender(EventArgs e)

Hi,

Sorry I didn't post the temp solution to the forum. An error in the table create script is causing this issue. What you need to do is open the database using sql managament studio search for the above mentioned cmsimport tables (since they are not prefixed with dbo they can be at the bottom of the list as well) Delete those tables and install the tables using the correct sql create script that can be downloaded here

Hope this helps you,

Richard

Hi Richard.

I am experiencing this problem with the latest version of CMS Import. Unfortunately the link to generatecmsimporttables.rar is no longer valid. 

I have trawled "the Internets" ;-) for the file, but no such luck.

Can you supply me with a working link?

Much appreciated

/Dan

Hi Dan,

The complete script is mentioned in the manual also. Download the manual via the documentation page on www.cmsimport.com.

Hope this helps,

Richard

Hey Richard

Thanks a bunch ;-) (RTFM) :-P

I've been experiencing similar problems when uploading a simple .csv file. In my case the cause seemed to be the fact that no CMSImport databases were created during CMSImport installation at all. After manually creating the databases using the SQL scripts in the manual, I received the following error message:

'Filegroup reference and partitioning scheme' is not supported in this version of SQL Server.'

I'm using Umbraco 4.11.1 hosted on Azure (using an Azure SQL Server database). After some Googling I found out that removing all "ON [PRIMARY]" parts from the script was the solution. Execution of this modified script successfully created the databases.

So the current version of CMSImport seems to be not compatible with Umbraco hosted on Azure out of the box. Until the next update the solution above can help you out.

Thanks Robin for mentioning this, weird that Azure has a different syntax from Normal Sql :-(

Your welcome. It's strange indeed. But nevertheless, it works great now and I've just bought the pro version!

I'm just now running into the Azure SQL issue. Thanks a ton, Robin!  You've saved me a lot of time and heartache :)

You're welcome Scot! Glad to here it helped you!

is working on a reply...