17.12.2017 17:33, Jiří Činčura wrote:
I.e. it is failed to initialize shared memory for monitoring snapshot.
I can't explain how it is possible to initialize lock manager shared
memory
first and then fail to initialize shared memory for monitoring snapshot.
Need more time to investigate it.
Any progress on this?
Yes. I can explain how it happens but it will not solve your issue,
unfortunately.
In short: it could happen if Firebird service opens database and initialize
lock
manager, then embedded process opens same database and initialize monitoring
snapshot.
Then, when Firebird service need to open montoring shapshot's shared memory, it
fails,
because mapped file object already created in another (isolated) windows
session.
I already explained this issue in this list: look for then message
"SeCreateGlobalObjects, Vista's UAC and Firebird" at 7 Aug 2009. That message
at the
very end contains recommendations what to do in cases like yours:
----------
If some application using embedded engine needs to work with the same database
from different
users sessions (for ex. at terminal server) we could recommend following :
a) users from the Administrators group must run such application with elevated
privileges
b) standard users could be granted SeCreateGlobalObjects privilege directly or
by including them
into special users group which have this privilege granted.
----------
Hope it helps,
Vlad
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
