6/9/2024 7:08 AM | |
Joined: 4/12/2018 Last visit: 11/18/2024 Posts: 203 Rating: (12) |
i am running the Session Monitor on the Comos on the SQL Server but I am not seeing all users? am I missing something? |
6/24/2024 11:19 AM | |
Joined: 6/30/2014 Last visit: 11/14/2024 Posts: 464 Rating: (90)
|
Hi, Good question, it could have different reasons. Important information: remember that the Session Monitor consumes a lot of resources of your network, so you should know/consider it, to avoid issues with the users... I have downloaded the documentation (so called DokuPack) from here, for the latest COMOS version: In that package, there is one PDX file, I have run it. Please feel free to do the same, just as a suggestion (to see all the results) In that search field, I have searched for the right keywords for your post: attached here you can see the results, in a screenshot. Maybe that helps you, maybe it answers your question. A colleague of mine wrote the following information, which I share with you here: The visibility of users and workstations in the COMOS Session Monitor can depend on several factors related to the database and network settings:
If you are using MS SQL Server with an iDB of at least database version 25, only users that are logged into the same database are visible in the session monitor. If you are using MS Access, visibility in the session monitor extends to users of all COMOS databases that exchange data in the same network.
The session monitor requires MultiCast messages to function properly.Ensure that your network supports and is configured for MultiCast messaging. It is also important to terminate other applications that may impose high performance loads on the network, as the session monitor uses resource-intensive network functions.
Make sure you have correctly initiated the session monitor by selecting "Extra > Monitoring > Session monitor" from the menu bar and clicking the "Start logging" button. Check the "Last update" time to ensure that the session monitor is actively updating its logs. If you have checked these settings and still face issues, it might be beneficial to verify the network's ability to handle MultiCast messages or consult with your network administrator to ensure all configurations are correctly set up for COMOS session monitoring ==> Now, in case you are sure that you have found a point which should be checked by the developers of COMOS, you may open a ticket: https://support.industry.siemens.com/cs/ww/en/view/109474501 ==> Just in case you would like to enhance the behavior of COMOS, you also may open a ticketing mentioning that you have an Enhancement Request (they call it ER). Allow me to suggest confirming the affected COMOS version, how it is and how it should become… with as many information as possible, describing the scenario and wish with simple words to avoid misunderstanding with their product manager. ==> If you think that the documentation should be edited: you also may open a ticket mentioning what is, from your point of view, missing. Surely you will confirm that the effort on your side will not be too big: just let them know what your issue or suggestion is, they will be glad to do the job All the best, SuperPippo |
Last edited by: SuperPippo at: 06/24/2024 11:24:12 |
|
Follow us on