Sage CRM 2017: Using Sysadmin

Hints, Tips and Tricks

Technical Hints Tips and Tricks that cover customization and development using Sage CRM. API usage and coding are covered.

Sage CRM 2017: Using Sysadmin

  • Comments 10
  • Likes

Sysadmin is a little known but useful path flag that can be used in Sage CRM to list the current logged on users.  It can also be used to manage current logged on sessions.

In path looks like


If you attempt to use this when not on the server you will get the message "Must be on server to run sysadmin".

If you on the CRM server when you enter the path then this is the screen you get:

You can see that you will have a listing of all logged on sessions.  In the image above it can be seen that the System Administrator seems to be logged on twice.  In fact the second log on is a webservices session and that can be seen from the information in the column containing the User Agent and IP.

If you click on the hyperlinked name, it seems to take you to a logon screen but in fact it has just logged out that user.

If you know the active sessionid then users can be logged out using the path


  • If you're not on the server and you have NT Authentication allowed in IIS, then you will be challenged for NT user details with rights to the registry (if your domain login doesn't have them already).

    There's also a lesser known one called /usercount which is only used with load balancing and multi-server systems. It returns a comma separated list of users, preceeded by the number of users.

  • You could appear to be logged in three times in the /sysadmin page if you're using the Outlook plugin as well as IE and webservices. If you only use synchronisation in Outlook and don't use it as a browser, then the actions column will be blank and the last action will appear to be some time in 1899.

  • Is it possible to make n asp page in the CRM witch can give us the list of the connected users ?

  • That information should already be available in the Users area.

  • What if I am on the server and I still get the "Must be on server to run sysadmin" message?  I tried http://servername/installname/eware.dll/sysadmin.  I also tried http://ip/installname/eware.dll/sysadmin.

  • Hi Chris P, I'm getting the same error message as yours while I'm at the server. Did you able to solve the problem? What is your solution? Thanks.

  • If you can see the SID then the command is:


  • For the "Must be on server to run sysadmin" message, sometimes it worked for me when the hostname changed to IP address (private IP if server configured with public IP) or vice versa in the URL.

  • What do the EOC, ROC, ACC, MDC mean?

  • Adam

    EOC, ROC, ACC, MDC stand for

    eWare Object Count

    Record Object Count

    *Active* Connection Count (it’s labelled GSQLConnectionCount internally, so concurrent DB connections)

    Metadata Count

    These are counts that had most importance in very early versions of the product.  They were used to help troubleshoot COM customisations.

    The ACC many be helpful if you are troubleshooting a DB problem.