Commented by: @hvlad

Try set IpcName = Global\FIREBIRD in firebird.conf

Commented by: m_Th (m_th)

I did.
Restarted the server.
Same result.
Perhaps is good to know:
If I log on in the Windows 2003 with remote connection then I receive the above error. If I run the fb_lock_print from the console of Win2003 then I receive the same error: "Unable to read lock table version 0."

hth.

Commented by: @hvlad

Are there connections at Firebird when you run fb_lock_print ?

Commented by: m_Th (m_th)

1.) Win XP - no connections: Unable to read lock table version 0. (A very cryptic error message IMHO - and also misleading)
2.) Win XP - connected clients: Ok. (the expected report is printed on screen)
3.) Win 2003 R2 - console: the same behaviour as 1.) and 2.)
4.) Win 2003 R2 - Using 'Remote desktop connection' which is shipped with Win XP:
Unable to access lock table.
C:\...<path>...\SERVER-A.lck
operating system directive CreateFile failed
-The requested operation cannot be performed on a file with a user-mapped
section open.

(As I noted above the firebird.conf has IpcName=Global\FIREBIRD and the server was restarted)

5.) Win 2003 R2 - Using another Remote desktop program (Goverlan 5.5) - same as 3.)

Summarizing:
a.) Provide a way for fb_lock_print to work with 'Remote desktop connection' which is the standard remote access feature for the Windows servers.
b.) If you can, please change those error messages in order to show (or a least indicate) the real cause of the error. (Someting like: "Unable to read lock table version 0. Perhaps there are no connections?")

hth.