Importing Members, I get the error below. The hotels property in question is a Multinode Treepicker of Document Type Hotels. Am successful importing if I leave out hotels or if I pass a Null value for hotels.
Have upgrade CMSImport to CMSImport PRO 3.7.4 and get the same issue (was on 3.2). I feel like I had this issue a while back, but can't recall how it was resolved. This only appears to be happening on our staging box. Production box for the time being, seems fine.
Error while importing data for property 'hotels', datasource record email = '[email protected]', Error :The wait operation timed out
Error while importing data for property 'hotels', datasource record email = '[email protected]', Error :The wait operation timed out
Error while importing data for property 'hotels', datasource record email = '[email protected]', Error :The wait operation timed out
Error while importing data for property 'hotels', datasource record email = '[email protected]', Error :The wait operation timed out
Error while importing data for property 'hotels', datasource record email = '[email protected]', Error :The wait operation timed out
Bit from the log file:
2018-04-06 13:48:49,639 [P25400/D29/T25] ERROR CMSImportLibrary.Providers.ImportProviders.Member.MemberImportProvider - CMSImport:CMSImport: A record failed to import for aliashotels
System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
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 Umbraco.Core.Persistence.PetaPocoCommandExtensions.<>cDisplayClass50.
For testing purposes, I am just importing 5 records. Hotels is imported as comma separated values. And only one of these records imported has more than one to import. But even when I force it to just be one, it still seems to time out.
Prior to the import, I have a stored procedure that gathers the hotels node id's in Umbraco that then are assigned/attached to the Members for whatever hotels they work with and made into comma separated values.
The data is added to a staging table of data to be imported for whatever Members need to be added/updated if their information is different in Umbraco when compared to the source.
The import then just does a simple select statement on the staging table. Most Members will just have one node id. But we have a few that have many node ids (100+). But the five I'm testing at the moment, just have one id.
Well that explains. I was assuming you have used the mntp advanced settings that just is using the advanced options from cmsimport. But I think retrieving the data from sql server takes a long time. What I would to is increase timeout to sql server and maybe cache the result so it only needs to be retrieved once.
If you want me to look at the implementation send an email with code to [email protected].
And I'll look into having the SQL stuff done. But from what I understand, our SQL production box should be set up the same way and it is importing fine.
Also looks like the MNTP we are using is obsolete now, so maybe that's partially related.
Execution Timeout Expired when importing Members
Importing Members, I get the error below. The hotels property in question is a Multinode Treepicker of Document Type Hotels. Am successful importing if I leave out hotels or if I pass a Null value for hotels.
Have upgrade CMSImport to CMSImport PRO 3.7.4 and get the same issue (was on 3.2). I feel like I had this issue a while back, but can't recall how it was resolved. This only appears to be happening on our staging box. Production box for the time being, seems fine.
Error while importing data for property 'hotels', datasource record email = '[email protected]', Error :The wait operation timed out
Error while importing data for property 'hotels', datasource record email = '[email protected]', Error :The wait operation timed out
Error while importing data for property 'hotels', datasource record email = '[email protected]', Error :The wait operation timed out
Error while importing data for property 'hotels', datasource record email = '[email protected]', Error :The wait operation timed out
Error while importing data for property 'hotels', datasource record email = '[email protected]', Error :The wait operation timed out
Bit from the log file:
2018-04-06 13:48:49,639 [P25400/D29/T25] ERROR CMSImportLibrary.Providers.ImportProviders.Member.MemberImportProvider - CMSImport:CMSImport: A record failed to import for aliashotels System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action
1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry) 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 Umbraco.Core.Persistence.PetaPocoCommandExtensions.<>cDisplayClass50.Hi Charles,
CMSImport queries items by name. Can it be that the resultset it has to process is too large?
Best,
Richard
For testing purposes, I am just importing 5 records. Hotels is imported as comma separated values. And only one of these records imported has more than one to import. But even when I force it to just be one, it still seems to time out.
Hi Charles,
I mean where MNTP is getting the values from?
Best,
Richard
If I understand you correctly...
Prior to the import, I have a stored procedure that gathers the hotels node id's in Umbraco that then are assigned/attached to the Members for whatever hotels they work with and made into comma separated values.
The data is added to a staging table of data to be imported for whatever Members need to be added/updated if their information is different in Umbraco when compared to the source.
The import then just does a simple select statement on the staging table. Most Members will just have one node id. But we have a few that have many node ids (100+). But the five I'm testing at the moment, just have one id.
Hi Charles,
Well that explains. I was assuming you have used the mntp advanced settings that just is using the advanced options from cmsimport. But I think retrieving the data from sql server takes a long time. What I would to is increase timeout to sql server and maybe cache the result so it only needs to be retrieved once.
If you want me to look at the implementation send an email with code to [email protected].
Best,
Richard
Dumb question, but MNTP advanced settings?
And I'll look into having the SQL stuff done. But from what I understand, our SQL production box should be set up the same way and it is importing fine.
Also looks like the MNTP we are using is obsolete now, so maybe that's partially related.
is working on a reply...