Deadlocks With Read Repeatable Isolation Level

If a custom business object uses an isolation level of read repeatable to access a SQL Server, and the business object is called simultaneously by two clients that send a query and update in the same transaction, a deadlock is possible. Remote Data Service is built to allow one of the processes to time out to release the deadlock, but this will fail the update for that client.

You can add a registry entry on the Web server to modify the length of the timeout. The default is 30 seconds (or 30,000 milliseconds).

To modify the timeout value

1. From the Start menu, click Run.
   
   
2. Type RegEdit and click OK.
   
   
3. In the Registry Editor, navigate to the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W3SVC\Parameters key.
   
   
4. Select the Parameters key. From the Edit menu, point to New, and select DWORD Value.
   
   
5. In the Name column, type ADCUpdateTimeout and press Enter.
   
   
6. Double-click the new entry. In the Edit DWORD Value dialog box, enter the new value in milliseconds in the Value data box. The value must be greater than or equal to zero.