How can I adjust the timeout setting for the desktop windows client? I just imported about 6,000 customers into the system via SQL/CSV File as I read there is no built-in customer import, but now the Customers tab just times out trying to load the list. I can do a 'Tools --> Customer Portal --> Manage Customers' and that will list the customers no problem, but the Customers tab is now choking as noted.

 

Excerpt from error dialog:

************** Exception Text **************
System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
The statement has been terminated.
   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(TdsParserStateObject stateObj)
   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.ExecuteDbDataReader(CommandBehavior behavior)
   at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)
   at Axosoft.Common.Data.SqlHelper.ExecuteDataset(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters)
   at Axosoft.Common.Data.SqlHelper.ExecuteDataset(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters)
   at Axosoft.OnTime.DataLayer.Customers.GetCustomersTree(String search, CustomersTreeSearchField searchField, Boolean showAllContacts, Int32 pageNumber, Int32 rowCount)
   at Axosoft.OnTime.UserInterface.OnTimeUtils.CustomersTreeControl.RefreshTree()
   at Axosoft.OnTime.UserInterface.OnTimeUtils.CustomersTreeControl.RefreshData(Boolean suppressCountUpdate)
   at Axosoft.OnTime.UserInterface.OnTimeUtils.CustomersTreeControl.PerformSearch()
   at Axosoft.OnTime.UserInterface.OnTimeUtils.CustomersTreeControl.tsbClearSearch_Click(Object sender, EventArgs ea)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

---

-Patrick Hartnett
Perryman & Associates / Perryman Software

Well, no resolution or workaround, but here's the response from support in case anyone else runs into the issue:

"You can actually increase the time response from the OnTime database over to the windows client of OnTime by modifying the "Max Customers Tree Search Results" from 750 which is set by default to 500 or less. This option is currently only available within the actual OnTime 2007 web client under; Tools > System Options > General Settings. This option will also be added to the windows client in our upcoming future releases of OnTime."

---

-Patrick Hartnett
Perryman & Associates / Perryman Software

Hello Patrick,

I see that Dragan Marceta responded to your support email from yesterday. As he mentioned, that option will be added to the OnTime windows client in a future release of the application, but can be changed now in the Web client by going to "Tools > System Options > General Settings".

Let me know if you have any further questions.
 

---

Thank you,

Tom Harder
Axosoft Support
support@axosoft.com
1.800.653.0024 option 3
--'Fear the Bug' Podcast--

We are having the same issue here, but only with one individual.

She will try to search through all of the defects in OnTime and will get the error. If I do the same search, I don't get the error. Even more, if she runs her version of OnTime on my computer, she still gets the error. We tried creating a new account for her, but she still gets the error.

I went to Web client's General Settings changed the number from 750 to 500. Still no luck. I've read that there is somewhere that you can change the timeout seconds, but I'm not really sure where to go.

Can you help us out? We're still in OnTime 2007.

 

Thanks,

Cory