Inflectra Customer Forums: Database concurrency condition detected on testset update via SOAP api (Thread) We use SpiraTeam 3.1 at the moment and are experimenting with the SOAP API. All goes fine, but 1 thing came up: when performing a TestSet_Update to update the status (from eg not started to "in progress") all is ok. when doing the same action again to set the status to yet another value we get: Server raised fault: 'Database concurrency condition detected' and very consistent. First time no problem, second time always the same error. Is this a known issue or is there a workaround? thx, Filip en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spirateam/issues-questions/239.aspxthreadId=239Filip Baert (filip.baert@newtec.eu)Database concurrency condition detected on testset update via SOAP api We use SpiraTeam 3.1 at the moment and are experimenting with the SOAP API. All goes fine, but 1 thing came up: when performing a TestSet_Update to update the status (from eg not started to "in progress") all is ok. when doing the same action again to set the status to yet another value we get: Server raised fault: 'Database concurrency condition detected' and very consistent. First time no problem, second time always the same error. Is this a known issue or is there a workaround? thx, Filip Fri, 10 Feb 2012 15:16:13 -05002012-02-27T20:37:40-05:00/Support/Forum/spirateam/issues-questions/239.aspxmessageId=471David J (adam.sandman+support@inflectra.com)This is by design, you need to do a TestSet_RetrieveById first to get the refreshed data then call tThis is by design, you need to do a TestSet_RetrieveById first to get the refreshed data then call the TestSet_Update method. This ensures that you don't have outdated data.Fri, 10 Feb 2012 15:59:09 -05002012-02-10T15:59:09-05:00/Support/Forum/spirateam/issues-questions/239.aspx#reply471messageId=472Filip Baert (filip.baert@newtec.eu) ok, sounds reasonable, but unfortunately the RetrieveById does not solve the error. this is the c ok, sounds reasonable, but unfortunately the RetrieveById does not solve the error. this is the complete message from spirateam: s:Client Database concurrency condition detected Database concurrency condition detected at Inflectra.SpiraTest.Business.TestSet.Update(TestSetData testSetDataSet, Int32 userId, Nullable`1 intRollbackId) at Inflectra.SpiraTest.Web.Services.v3_0.ImportExport.TestSet_Update(RemoteTestSet remoteTestSet) DataAccessConcurrencyException this is our python code: testSetToExecute = getTestSetToExecute(automationHostName) =>> function gives 1 testset that meets specific filters. if(testSetToExecute is not None): testCasesToExecute = client.service.TestCase_RetrieveByTestSetId(testSetToExecute.TestSetId) testSetToExecute =client.service.TestSet_RetrieveById(testSetToExecute.TestSetId) testSetToExecute.TestSetStatusId = 2 #in progress testSetToExecute.TestSetStatusName = "In Progress" testSetToExecute.ExecutionDate = datetime.now() client.service.TestSet_Update(testSetToExecute) the last line fails with given error. thx for the help Filip Mon, 13 Feb 2012 12:36:10 -05002012-02-13T12:36:10-05:00/Support/Forum/spirateam/issues-questions/239.aspx#reply472messageId=477David J (adam.sandman+support@inflectra.com)Could it be that the LastUpdateDate is not being sent back correctly? That is what's used to verify Could it be that the LastUpdateDate is not being sent back correctly? That is what's used to verify that the data is current? Also do you have the latest patch for v3.1 applied?Mon, 27 Feb 2012 20:37:40 -05002012-02-27T20:37:40-05:00/Support/Forum/spirateam/issues-questions/239.aspx#reply477