Inflectra Customer Forums: Server raised fault: 'Database concurrency condition detected' (Thread) I am using the Web service to trying to update the TestSet, When I call TestSet_Update(testset), I got the error "suds.WebFault: Server raised fault: 'Database concurrency condition detected' . Any idea? all I did is: Call set=TestSet_RetrieveById(10), to get the RemoteTestSet record. And then I change the set.TestSetStatusName="Completed", After updating the value, I call client.service.TestSet_Update(set). I got the error message. 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/spiratest/issues-questions/908.aspxthreadId=908y gan (ygan@ftdi.com)concurrency Server raised fault: 'Database concurrency condition detected' I am using the Web service to trying to update the TestSet, When I call TestSet_Update(testset), I got the error "suds.WebFault: Server raised fault: 'Database concurrency condition detected' . Any idea? all I did is: Call set=TestSet_RetrieveById(10), to get the RemoteTestSet record. And then I change the set.TestSetStatusName="Completed", After updating the value, I call client.service.TestSet_Update(set). I got the error message. Fri, 16 May 2014 14:58:10 -04002014-07-09T07:35:43-04:00/Support/Forum/spiratest/issues-questions/908.aspxmessageId=1661David J (adam.sandman+support@inflectra.com) That means that the ConcurrencyDate you are passing back does not match the one you received ( That means that the ConcurrencyDate you are passing back does not match the one you received (or your SOAP library is changing its timezone).Fri, 16 May 2014 15:55:50 -04002014-05-16T15:55:50-04:00/Support/Forum/spiratest/issues-questions/908.aspx#reply1661messageId=1662y gan (ygan@ftdi.com)Thank for your answer. But Could you give me more clues? What I can do to solve this issue?Thank for your answer. But Could you give me more clues? What I can do to solve this issue?Fri, 16 May 2014 20:05:08 -04002014-05-16T20:05:08-04:00/Support/Forum/spiratest/issues-questions/908.aspx#reply1662messageId=1716David J (adam.sandman+support@inflectra.com) Hi Most likely the issue is either the timezone or rounding issues on the milliseconds, is t Hi Most likely the issue is either the timezone or rounding issues on the milliseconds, is there a way to set the timezone on the Python date object? Here's some pointers - http://reverb.findawayworld.com/development/easy-python-soap-with-suds-with-a-few-datetime-gotchas/ Try force-setting it to UTC? Regards Adam Thu, 26 Jun 2014 14:34:49 -04002014-06-26T14:34:49-04:00/Support/Forum/spiratest/issues-questions/908.aspx#reply1716messageId=1728Filip Baert (filip.baert@newtec.eu) Hi, we struggled with this suds issue for months. There is a bug in suds that cannot handle the Hi, we struggled with this suds issue for months. There is a bug in suds that cannot handle the milliseconds correctly. You cannot predict what value will be returned, even if the timestamp was only stored in a variable and later on read out. our solution is https://pypi.python.org/pypi/suds-jurko . There the issue is solved. this is what we used as installation for it (we are linux users): perform: wget http://bitbucket.org/jurko/suds/downloads/suds-jurko-0.6.tar.bz2 tar -xvf suds-jurko-0.6.tar.bz2 cd /usr/local/lib/python2.7/suds-jurko-0.6 python2.7 setup.py install hope that helps :-) Filip Wed, 09 Jul 2014 07:35:43 -04002014-07-09T07:35:43-04:00/Support/Forum/spiratest/issues-questions/908.aspx#reply1728