[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Lock wait timeout of 1800 seconds expired (8812)

Status
Not open for further replies.
M

mfurgal

Guest
Hi Dmitri: The most likely cause is a table lock on the MSSQL side. Make sure all client have their ISOLATION LEVEL set to READ UNCOMMITTED. Also, make sure there are no unique indexes (other than the prrowid index) on the MSSQL side. Mike -- Mike Furgal Director – Database and Pro2 Services PROGRESS Bravepoint 617-803-2870 mfurgal@progress.com

Continue reading...
 
Status
Not open for further replies.

Similar threads

P
Question Lock wait timeout of 1800 seconds expired (8812)
Replies
8
Views
2K
Rob Fitzpatrick
Rob Fitzpatrick
M
  • Locked
[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Pro2 ReplQueue Record Locks
Replies
0
Views
418
mfurgal
M
M
  • Locked
[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Extent management on replication enabled database
Replies
0
Views
471
mfurgal
M
M
  • Locked
[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Lock wait timeout of 1800 seconds expired (8812)
Replies
0
Views
441
mfurgal
M
M
  • Locked
[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Lock wait timeout of 1800 seconds expired (8812)
Replies
0
Views
384
mfurgal
M
Top