Increasing the database timeout can help resolve SelectQueryFailed: user requested cancel of current operation error messages.  Other solutions to these errors can include optimizing the query to exclude certain records, or even adding an index in some cases.


Setting the CommandTimeout to a value that is too high can significantly increase the amount of the time required for an offline sync to be performed.  As such, any changes should be tested in non-production environments first.  We generally do not recommend going over a value of 120 seconds.


DataSplice 5

  1. Login to the Admin Client and locate the DbPlugin item in the server settings
  2. Select the profile named maximo
  3. Find the CommandTimeout field (at the far right)
  4. Enter a new timeout value in seconds
  5. Save changes and restart the service for the changes to take effect


DataSplice 4, SQL Server

  1. Navigate to the Server folder and locate the file named DataSplice.Db.dll.config
  2. Open the file to edit
  3. Search for the first instance of system.data.sqlclient
  4. Find the next instance of CommandTimeout after that 
  5. Enter a timeout in seconds between the command timeout tags (will be blank by default)
  6. Save on completion and restart the service

DataSplice 4, Oracle

  1. Navigate to the Server folder and locate the file named DataSplice.Db.dll.config
  2. Open the file to edit
  3. Search for the first instance of system.data.sqlclient
  4. Find the next instance of CommandTimeout after that 
  5. Enter a timeout in seconds between the command timeout tags (will be blank by default)
  6. Save on completion and restart the service