To see the number of CALs Jiwa thinks is being used, you can run a query in SQL Server Management Studio identical to that which Jiwa uses:
- Code: Select all
SELECT hostprocess, MAX(hostname) hostname, COUNT(DISTINCT hostprocess) CALs
FROM Master.Dbo.SysProcesses
WHERE Program_Name = 'Jiwa Financials'
GROUP BY hostprocess
You should see results something like this:
- SQL Management Studio
If you're finding you only have 16 users but 20 CALs used, then it may be a case of Jiwa running in the background, or connections failing to close. If you're using RDS then as an administrator, look at the running processes and count the number of jiwa.exe's running - if you see more than you expect, then in some users sessions they may have a jiwa running in the background (may happen if the application crashes) - terminate that process and run the above query again to see if that reclaimed the CAL.
Restarting SQL Server will always result in all CALs being freed - perhaps that's an option - like a daily SQL Server restart at 5am. Often we've seen this behaviour when users are logged in for extended periods, so a daily SQL server restart (Stop and restart of the SQL service, not a reboot) may help.
Mike