-
-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shared memory area is probably already created by another engine instance in another Windows session, failed to create database #7522
Comments
It is side effect after fix for #7122, looking for solution. |
Don't you think that this bug needs more attention? It's one of the basic uses of backing up the database. Every customer backing the databases this way in FB 2.5 the next day he installs Firebird 3.0 finds out (if he is a responsible Firebird admin ;)) that backups stopped being performed, reads this message and it doesnt give gim any idea what it is about. |
LibreOffice has a building issue , might be related to this fix https://ci.libreoffice.org/job/gerrit_windows/161172/consoleFull#1408899889d893063f-7f3d-4b7e-b56f-4e0f225817cd |
It produces another error message, as I see in log:
Does anybody reads that logs and look into firebird.log for details ? |
|
The second log contains
Looks like someone (build script ?) set
|
…a is probably already created by another engine instance in another Windows session, failed to create database
Please see #6937, and our discussion there about the specific use case in LibreOffice, which requires a per-process lock. |
Hello. I'm not sure whether this is a bug. If so, please tell me what Im doing wrong. Tried on latest snapshot 3.0.11.33666-0 x64 Windows
gbak.exe -c path_to_gbk path_to_fdb
gbak error Shared memory area is probably already created by another engine instance in another Windows session, failed to create database
It only works when I add localhost: to the fdb path.
The text was updated successfully, but these errors were encountered: