We have the possibility to login with 4 connections at the same time.
So when my colleague is logged in and his vpn crashes for some reason and het reconnects then he gets another entry in the tbati table.
So suddenly then there are only 3 connections possible. Later for some reason the vpn dies and again one connection is less.
This is a bug, finally all 4 connections are blocked.
Even when it is the same user every time. Please fix this buggy behaviour asap.
So far I manage by removing the connections by hand but that shouldnt be needed!!
This goes for Version 8.00.0014 but was the same on versions before.
Please fix this or allow a standard way to kill left over connections.
Hello,
I will discuss this issue with our team.
regards,
Bernhard Bernsmann
Hello,
let me get this straight, you own a license for 4 simultaneous connections, and when a particular connection drops the tool informs that you can only use 3 connections? I await your reply with the attached images exemplifying.
Thank you!
The fact is that when you don’t log off in a decent way and again login the old session will stay in the database and occupying a seat. It will not overwrite the old session. If you have one seat you are requested if the old session must abort. But if you have more seats it will only happen if you logon if all seats are taken. If you are user 2 and all seats are taken by user 1 then you cannot logon and you have to fix the sqlite database yourself.
Create a small blank application and onExecute event remove records from sc_tbati then deploy as a project.
For every problem there is always a solution.
Of course there is. (It’s what we did). But there should be a standard solution within the SC environment.
Hello,
The problem is that I need to simulate this problem in our system to be verified as a bug. And your problem occurs to the external fault Scriptcase (VPN), so this test can take as it cause a fall vpn is a little complicated and insecure.
Initially we try to simulate and if a bug is confirmed we will try to provide a solution soon.
Sorry for the inconvenience.
Thank you!