Locking error "Failure getting record lock on a record from table" occurs in Crystal Reports when Default Isolation Level is set to Read Uncommitted

Feb 16, 2016
Knowledge

Title

URL Name

P119358

Article Number

000130786

Environment

Product: OpenEdge Version 10.x, 11.x Product: Progress Version: 9.x OS: Windows Other: Setting Crystal Reports 9, 10, 11 (XI) Transaction Isolation Level

Question/Problem Description

Locking error "Failure getting record lock on a record from table" occurs in Crystal Reports when Default Isolation Level is set to Read Uncommitted
Locking errors occurs when running reports

Steps to Reproduce

Clarifying Information

Using Crystal Reports to generate reports against a Progress database
Connection to the database is established using a Progress ODBC driver
ODBC DSN is configured with a Default Isolation Level of Read Uncommitted
Records used in the report are being queried by 4GL users at the time the reports are run

Error Message

Database Connector Error: 'HY000:[DataDirect][ODBC Progress OpenEdge Wire Protocol driver][OPENEDGE]Failure getting record lock on a record from table PUB.MyTable. [Database Vendor Code: -210015]' Failed to open a rowset. Query Engine Error Error 210015 Subclass Message: Failure getting record lock on a record table <table-name>

Defect Number

Enhancement Number

Cause

Crystal Reports 9, 10 and XI set their own Isolation Level, which may not be Read Uncommitted.

Resolution

IMPORTANT: This article contains information about modifying the registry. Before modifying the registry, make sure to back it up and understand how to restore the registry if a problem occurs.

1) Start Regedit
2) Go to:

Crystal Reports 9
HKEY_CURRENT_USER\Software\Crystal Decisions\9.0\Crystal Reports\Database\ODBC

Crystal Reports 10
HKEY_CURRENT_USER\Software\Crystal Decisions\10.0\Crystal Reports\Database\ODBC

Crystal Reports XI Release 1 and BusinessObjects XI Release 1

HKEY_LOCAL_MACHINE\Software\Business Objects\Suite 11\Crystal Reports\Database\ODBC

Crystal Reports XI Release 2 and BusinessObjects XI Release 2

HKEY_LOCAL_MACHINE\Software\Business Objects\Suite 11.5\Crystal Reports\Database\ODBC

Crystal Reports for Visual Studio .Net 2002, 2003

HKEY_LOCAL_MACHINE\Software\Crystal Decisions\9.0\Crystal Reports\Database\ODBC

3) If not exists yet create a "STRING value" called "IsolationLevel"

4) Change the value of "IsolationLevel" to 1

The possible values are:

1 (uncommitted read)
2 (committed read)
4 (repeatable read)
8 (serializable read).

Workaround

Notes

In Crystal Reports 10 and XI the IsolationLevel value is not set by default in the Registry, but Crystal Reports does check for this value.

References to Other Documentation

Progress Articles:
"Transaction Isolation Level: Proper Syntax and Definitions"

Keyword Phrase

Last Modified Date

11/20/2020 7:25 AM

Locking error "Failure getting record lock on a record from table" occurs in Crystal Reports when Default Isolation Level is set to Read Uncommitted

Files(0)

Was this article helpful?

Was this article helpful?

Locking error "Failure getting record lock on a record from table" occurs in Crystal Reports when Default Isolation Level is set to Read Uncommitted

Information

Related Articles