Symptoms
A DB stored procedure calls the same web service N times and does some updates.
For each successful call the web service is called once.
The problem is.
The call to web service is successful and is logged to the k2 DB but K2 rolls backs the transaction for some reason and the logs are lost.
There should be an option to run SQL Smart Object without K2 transaction.
Diagnoses
After having a look at the K2 HostServer logs and the SQL profiler there was large amount of deadlocks and timeouts which then rolls back the transaction and the log data is lost
Resolution
The client elected to close ticket. After Investigation it was found there was Time out and Deadlock issues on the SQL server. the customer was able to find as workable workaround for this scenario.
The issue was resolved internally.
