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 :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Details Regarding SysU...
Microsoft Dynamics AX (Archived)

Details Regarding SysUserLog table in AX 2012 R3 CU11

(0) ShareShare
ReportReport
Posted on by Muneeb 895

Hi,

I am using AX 2012 R3 CU11.

I have a requirement wherein I need to collect the data from the table SysUserLog, I have few queries which are detailed in the below snapshot,

4331.SysUserLogEntryTypes.jpg

For the field "ClientType", besides having Client, Server & WorkerThread records, is there a possibility of any other type of record as the enum 'ClientType' used contains in all 5 values for this field ? 

Would appreciate for the quick response.

Sincerely,

Muneeb

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Vilmos Kintera Profile Picture
    Vilmos Kintera 46,149 on at

    The other two session types are COMObject and ServerCompileAll. Calling another application or getting called from outside via the COM interface would create sessions of that type. Excel for example is accessed via COM, however I do not see user log entries recorded for those connections in the table. Also using the cross-reference tool indicates that it could be a web session connection as well, for example if you check \Classes\Global\webSessionClient method. You can find out a bit about calling AX through COM:

    msdn.microsoft.com/.../jj677289.aspx

    The other one is for some sort of server-side full compile, but there are no references to that using xRef - it is not called, unless the AX kernel does it somewhere which is hidden from us.

    The Server entries are not relevant, because server uptime is recorded in SysServerSessions table, so putting a record in the userlog does not really makes sense to me.

    Worker threads are spawned and closed in a short period of time, and if the process would have to wait until you write the logout time in a new transaction/user connection in the log table, that would delay the process and destroy the purpose of being flexible when spawning new threads for processing distributed workloads.

  • Vilmos Kintera Profile Picture
    Vilmos Kintera 46,149 on at

    Can you please make sure you tick the checkboxes for helpful answers next to each post, so the topic gets resolved? Thank you.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
CP04-islander Profile Picture

CP04-islander 39

#2
Michel ROY Profile Picture

Michel ROY 14

#3
imran ul haq Profile Picture

imran ul haq 8

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans