Tag: user

Categories
T24 Temenos

Possible fixes for “Maximum T24 users already signed on” Error

First of all, this should never happen in a Production environment.

Maximum T24 users signed on
Maximum T24 users signed on

But in a Testing environment, it can. Let’s see how the tokens/sessions work in T24.
Whenever a T24 user logs in, a unique token id will be created in the F.OS.TOKEN and F.OS.TOKEN.USE tables. When the user logs off, the system will remove the id from the F.OS.TOKEN table. Theoretically.
The TOKEN will be removed from the table if:

  • The user logs out using the Sign off link.
  • The user signs off using the “LO” command command in the command line.
  • The record from F.OS.TOKEN gets removed when the time in TIME.OUT.MINUTES field in USER record is reached. If the TIME.OUT.MINUTES field in USER record is empty, then time specified in AUTOLOG.TIME.MINS field of SPF record is being used by the system.

In some cases, this does not happen and you may get the error message that you can see in the pic above. In my earlier post, I showed how to see how many sessions are active in the environment. If you know that many of the listed users are not working in T24 anymore or there is more than 1 entry for a user then you may do the following:

%TSA.SERVICE enquiry listing services that contains TOKEN in their ID.
RTN.CLR.EXP.TOKENS token cleaning service in R20
  • Check if there is token cleaning up service and it is running. The name of the service could be BNK/RTN.CLEAR.EXPIRED.TOKENS or RTN.CLR.EXP.TOKENS. This should clean the OS.TOKEN table. Please note that you may not find this service in every T24.
  • Check the TIME.OUT.MINUTES field on the USER configuration for each user. It is a bad practice to set this field to 999. In this case set a lower value like 5 minutes.

That’s all!
Cheers,

Categories
Microsoft Windows

Create a database and an user with SQL Server Authentication

Again dear Microsoft, why do you harden our life when you could make it easier?
Yesterday I was able to install Access Database Engine to connect the .ASP application to its database. But because getting

An unhandled win32 exception occurred in w3wp.exe

all the times, I thought it is time to change to MS SQL Express.

  • Installed MS SQL. Few GBs not much.
  • Installed SQL Server Management Studio (the installer is 830MB while MySQL Workbench installer is 23MB).
  • Migrated the data with SQL Server 2016 Import and Export Wizard. Was quite easy because I had already installed the Access Database Engine connector.

So I had everything to start using with the .ASP. But I knew I need a user for the connection.

The first of all only some documentation mentions that you have to enable SQL Server Authentication. Not having this option enabled you will get login failed. Beside that you are able to create the user add password add roles everything without a simple warning that you won’t be able to use it. Haha.

SQL Server Authentication

When set you have to restart the SQL agent. You can use SQL Configuration Manager for this. A tool designed for this. I could not find the service stop start within Windows.

#service mysql restart

Isn’t this more simple? Okay now You could use PowerShell for this.

Secondly, by default you can only create users with a password in a contained database. Why? Don’t know. Maybe life can be too easy.

So again asking stackoverflow what to do. Here is the solution:
exec sp_configure 'contained database authentication', 1
go
reconfigure
go

alter database YourDatabase
set containment = partial
go

Here we go. So now you are able to create a user with a password. Simple, isn’t it?

Finally you can test the connection by creating a TestConnection.udl file somewhere in your server. Then double click on it and test the connection with the specific user name and password.

TestConnection.udl properties

And all of these can be made with one single command in MySQL without any hocus-pocus:

>grant all on (databasename).* to 'username'@'localhost' identified by 'password';

Cheers.