Page 1 of 2

Solved. Bug, important: one db cannot connect to server, asking for license

Posted: Tue Jul 28, 2020 10:47 am
by Trinitylab
Hi,
EPIM 9.2
Win 10 guest connecting to Win 8.1 host, both x64.
Strange:
on Win 10 I have two instances running.
From one I can connect to DB1 via server.
From the other I am trying to connect to DB2, which worked fine for years, and I get the message:
EPIM-BUG-licenseneeded.JPG
It does not make any sense. If I don't have the license, I could not connect to DB1.
Anyway, cannot work.

Re: Bug, important: one db cannot connect to server, asking for license

Posted: Tue Jul 28, 2020 10:51 am
by Trinitylab
Looks like only one DB triggers that bug, say DB2.
I opened DB3 and it works smoothly.

Re: Bug, important: one db cannot connect to server, asking for license

Posted: Tue Jul 28, 2020 11:36 am
by Trinitylab
Does anybody have a clue what that might be?

Re: Bug, important: one db cannot connect to server, asking for license

Posted: Tue Jul 28, 2020 3:23 pm
by Trinitylab
@admin, would you have a look at the problem?
What I can add is it did not exist before 9.x

Re: Bug, important: one db cannot connect to server, asking for license

Posted: Tue Jul 28, 2020 8:49 pm
by admin
My first step would be to sync the DB2 into the new one using EPIM Sync. Will it help?

Re: Bug, important: one db cannot connect to server, asking for license

Posted: Tue Jul 28, 2020 9:33 pm
by Trinitylab
Works! Thank you!
How do you think, would it be reasonable to do the same with every other db we have, just to "refresh" them?

Re: Solved. Bug, important: one db cannot connect to server, asking for license

Posted: Wed Jul 29, 2020 8:03 am
by admin
Awesome, thanks for the confirmation!

I wouldn't recommend doing anything with the DB if it's working normally. As EPIM employs some internal DB checking/optimization mechanisms on a regular basis anyway. That particular issue was related to a fix we introduced some time ago and which seemingly didn't apply to the DB2 correctly.

Re: Solved. Bug, important: one db cannot connect to server, asking for license

Posted: Wed Jul 29, 2020 8:05 am
by Trinitylab
OK, thank you, got it.

Re: Solved. Bug, important: one db cannot connect to server, asking for license

Posted: Fri Sep 04, 2020 1:44 pm
by Trinitylab
Hello, it's the same, now I can see two users in DB, however there is only one connected.

Will do the sync as above, which is workaround, but the problem persists.

Re: Solved. Bug, important: one db cannot connect to server, asking for license

Posted: Mon Sep 07, 2020 2:48 pm
by admin
Please copy-paste the "This database was opened in" values from File->Database Management. Thanks!

Re: Solved. Bug, important: one db cannot connect to server, asking for license

Posted: Mon Sep 07, 2020 2:53 pm
by Trinitylab
Hello admin.
The workaround worked, this is this new DB, synced earlier (as above) to new,
Opened in:
9.3, 9.0
but it was used, gosh, since 5.x some.

Re: Solved. Bug, important: one db cannot connect to server, asking for license

Posted: Tue Sep 08, 2020 9:58 am
by admin
In this case the problem shouldn't have happened.. If you still have the previous database, please delete all the data from it, leaving just users with their rights intact and forward to us, will check it out. Thanks!

Re: Solved. Bug, important: one db cannot connect to server, asking for license

Posted: Tue Dec 08, 2020 4:14 pm
by Trinitylab
It persists.
I have noticed that this might be something with Firebird. (?)
Simply, when DB on the guest PC is closed in an irregular way (lost wi-fi connection or similar), then 2 users are still shown on the host PC using that DB. No way to kill one of them. Looks like Firebird does not see that the other PC is disconnected.

Re: Solved. Bug, important: one db cannot connect to server, asking for license

Posted: Fri Dec 11, 2020 2:12 pm
by admin
Will check that out, thanks for the update.

Re: Solved. Bug, important: one db cannot connect to server, asking for license

Posted: Mon Dec 14, 2020 2:00 pm
by admin
Firebird uses a standard TCP/IP connection, which is considered to be broken only after 2 hours by default system settings. That's a bit too much. Attached is the reg file that changes this setting to 5 mins, run it and it should fix the problem with ghost users in the database.