Dynamics Community Forum Thread Details

eConnect 2010 Timeout

Greetings,

We are using eConnect 11.0.1.0 to import 1800+ GL transactions into GP 2010. We are consistently receiving a SQL timeout error while creating the transactions and we have updated the services configuration file per Google searches to increase the ProcTimeout appSetting to ten minutes. This appeared to work but it was a coincidental fluke as the timeout error consistently pops up.

How can we increase the command timeout (or some other setting) to prevent these occurrences? Shrinking the sizes of the GL batches is not an option as we had the same process running in 9.0 without any complications.

Below is the Event log entry that tracks these occurrences.

Action:

Service Create Transaction

Current User Name:

TOPCO\GPEconnect

Input parameters:

Exception type:

System.Data.SqlClient.SqlException

Exception message:

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Stack Trace:

at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

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.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)

at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()

at Microsoft.Dynamics.GP.eConnect.EntityMessageProcessor.ExecuteSqlCommands(XElement transactionNode, EntityMessage message)

at Microsoft.Dynamics.GP.eConnect.eConnectMethods.ProcessMessageImport(EntityMessage message)

at Microsoft.Dynamics.GP.eConnect.eConnectMethods.EntityImportImplementation(String connectionString, String sXML, Boolean isTransaction)

at Microsoft.Dynamics.GP.eConnect.eConnectMethods.CreateTransactionEntity(String connectionString, String sXML)

at Microsoft.Dynamics.GP.eConnect.Service.CreateTransactionEntity(String ConnectionString, String sXML)

Hi William,

Would you care to post the code sample which creates the transactions? Creating a GL transaction should not exceed the default timeout of SQL Server. Let's focus on the root cause rather than try to extend the timeout to temporarily fix this issue.

I'm thinking that it could be one of a few things based on intermittent time-outs:

1. The integration code is passing too much into the web service at once, could be refactored.

2. Connectivity problem, or general database latency.

3. A third factor, or separate process is doing additional work as a result of this call.

Also, I understand that everything worked properly on version 9. That was two major versions ago and there can be many things changed or updated during a migration that can unexpectedly cause problems. Intermittent problems like these can be difficult to research.

Thanks,

Bryan

Quick Links

Leaderboard