• State Verified Answer
  • Replies 15 replies
  • Answers 1 answer
  • Subscribers 14 subscribers
  • Views 5841 views
  • Users 0 members are here
Options
Related

How to show logs terminal server other then console session (intouch)

Roland

Hello,

We have set up a terminal server with terminal clients, system platform IDE 2023R2 SP1 (intouch). Can someone help me to get the logs of a client (sessionID).

I manage to get only log info from console (sessionID:0)  

With regards, 

Roland

  • 0 in reply to Richard Köhlerstrand

    I could not let this go so I had to set up a test scenario and the results are that 2023 R2 SP1 behaves differently here. 

    I set up a Windows Server 2020, enabled Terminal Server and took a snapshot of the server.

    Installed System Platform 2017 Update 3 SP1 and created an application that logs a message while running.

    When started on the console, it logs on session ID 0, as expected.

    I then log in using a Remote Desktop user and start the same application, and it IS logging the session ID based on the client IP. (as expected).

    But...

    When i revert my snapshot and install System Platform 2023 R2 SP1, do the same test and both sessions are logging on Session ID 0!

    So there seems to be something different in how InTouch behaves in the new version.

    The log does indicate something strange, 

    In 2023 there is a log message when view.exe is starting, and as you can see it indicates that it runs the application in Terminal Services Mode, but immediately the next row says 'Normal Mode', I have no idea if this relates, and in 2017 I don't recalling seeing these messages at all, so something has changed.

    I did try running the latest version with Patch 02 applied and the behavior is the same.

    So its time to create a ticket with AVEVA Techsupport to sort out if this is a bug or if some other dependencies has changed.

    I don't believe we will get much further on this here and I will of course report back any update.

    I hope the longer route to filter by Process ID is a valid workaround for you, but still as I understand it your initial issue is that it does not log at all from your session, I could not reproduce this and you have to sort that preferably with techsupport.

  • 0 in reply to Richard Köhlerstrand

    Oh, and yes, I did install System Platform in "Terminal Server, Remote Desktop - Installation Mode"

  • 0 in reply to Richard Köhlerstrand

    Thanks,

    There will be a hot fix in the future, a ticket is raised by Aveva techsupport

  • 0 in reply to Roland

    Thanks,

    I have also raised a ticket on this based on our findings, I will also update here with on the outcome witch should be the same response as you get. I have some upgrades in the pipeline that will be effected by this behavior. Thanks for identifying this issue!

    Have a great weekend!

  • 0

    As Roland mention, this has been identified as an issue by Aveva techsupport, (This is known issue for product version 2023 R2 SP1)

    So I would assume/hope it will be included in the next patch release or new version.

    If you want to get the fix you can contact techsupport and ask for "HF 23.2-IMS-4092155" that address the "Session id not showing" issue for version 2023 R2 SP1 P02. or reefer to that HF and request it for the version you are using.