web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

User Session Limitation

(0) ShareShare
ReportReport
Posted on by 3,335

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

  • André Arnaud de Calavon Profile Picture
    307,314 Super User 2026 Season 2 on at

    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?

  • Jan M. Profile Picture
    3,335 on at

    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.

  • Jan M. Profile Picture
    3,335 on at

    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?

  • André Arnaud de Calavon Profile Picture
    307,314 Super User 2026 Season 2 on at

    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.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the August Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans