Hi
We cannot open more than five user sessions. Next access will produce the Eventlog error
Object Server 03: The database reported (session 2 (-AOS-)): [Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot insert the value NULL into column 'LOGINDATETIMETZID', table '[dbname].dbo.SYSCLIENTSESSIONS'; column does not allow nulls. INSERT fails.. The SQL statement was: "{call CREATEUSERSESSIONS(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}"
The table SysClientSessions was cleand up.
Thanks for any help.
*This post is locked for comments
Hi Jan,
There is no functional support for synchronizing this table separately. You can try to create a script where only one table will be synced. You can also try a full database sync anyway. Also review if the stored procedures are correct. Compare them with another R3 environment.
It seems that a new record could not be inserted by the stored procedure, an existing could be updated. So there is not a limit to five, just for the existing records.
If column is set not null, the error will be for the next column. Means the record is empty and the default constraints should send the value, but there are none.
As this table is a system table the hole db must sync or how to do it for this table type?
Hi André
There was a fresh install of R3 and Datamigration with R2 DB. System runs normal, just these limit. There are enough Disk/Memory and only one AOS.
Hi Jan,
Out of the box, there is not a real session limit. Have you tried to restart the AOS? Since when did this issue occur? Did something change in between? Is it impacting your production or another environment? If production, on all AOS machines or just one?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,228 Super User 2024 Season 2
Martin Dráb 230,056 Most Valuable Professional
nmaenpaa 101,156