We have a client with Interbase 2009 SMP running on Windows 2008 SBS x64. License Manager shows 1x Interbase SMP 2009 Server Edition and 10 Users and 1x Interbase 2009 Additional 1 User License.We have reached a limit on the number of clients that connect and their app reports that Interbase is out of licenses.I have downloaded a util called ibconsvc that shows 20 connections (4 per computer) to the server. How many connections should we be able to have to this server and is there anything else I can do to troubleshoot this issue?Thanks.
.gif "Interbase")
Serial Key Idm
Terry Wilson wrote: We have a client with Interbase 2009 SMP running on Windows 2008 SBS x64. License Manager shows 1x Interbase SMP 2009 Server Edition and 10 Users and 1x Interbase 2009 Additional 1 User License. We have reached a limit on the number of clients that connect and their app reports that Interbase is out of licenses. I have downloaded a util called ibconsvc that shows 20 connections (4 per computer) to the server. How many connections should we be able to have to this server and is there anything else I can do to troubleshoot this issue? ThanksLegally, you have license for 11 human beings here. Of course, theInterBase server doesn't know anything about human beings, sotechnically the way it works is it allows 4 connections per userlicense.
InterBase calls a connection an attachment, so you should beallowed 44 attachments here. You can run InterBase server manager andServer Properties to see how many attachments there are currently.On rare occasions, I've seen the error maximum user count exceed whenthe maximum number of attachments was not reached. There are twoconditions I know of:1. Occurs with InterBase 2009 pre update 1.2.
Can be caused by a corrupted database. I've never reproduced thisscenario, but I've had enough people tell me about it, to believe it istrue. Everyone who has every reported this has never been willing toprovide their database and fixed their database in one way or another toresolve the problem.
What Is A Serial Key
Because we've never reproduced it, we have no wayto fix it. So, if you have a database that causes this problem, I'd loveto get.