Search

Language:  

Available article translations:

Collecting Detailed Logs from Parallels Remote Application Server v15

APPLIES TO:
  • Parallels Remote Application Server

Information

This article describes how to enable detail logging on each Parallels Remote Application Server 15 component

Note: Please grant Users group Full Control permissions under "C:\ProgramData\Parallels\RASLogs\devredir.log" and "C:\ProgramData\Parallels\RASLogs\shell.log" files before registry change.

Detailed logging for Publishing Agent:

  1. In the registry editor go to

    HKEY_LOCAL_MACHINE\SOFTWARE\Parallels\2XController 
    

    Note: (For 64bit operating systems check the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Parallels\2XController key)

  2. Create a new DWORD key called LogLevel. Assign it a decimal value of '6'. Click OK.

  3. Create a new DWORD key called Debug. Assign it a decimal value of 1. Click OK.

  4. Create a new DWORD key called ConsoleLogLevel. Assign it a decimal value of 6. Click OK

  5. Create a new DWORD key called MoreDetails. Assign it a decimal value of 1. Click OK

    Note: To apply these settings all you need to do is press apply from the console. You don't need to restart the publishing agent.

  6. Reproduce the issue and collect a copy of the RASLogFile from the installation directory > AppData folder.

Detailed logging for Terminal Server Agent

  1. In the registry editor go to

    HKEY_LOCAL_MACHINE\SOFTWARE\Parallels\TSAgent
    

    Note: (For 64bit operating systems check the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Parallels\TSAgent key)

  2. Create a new DWORD key called LogLevel. Assign it a decimal value of '6'. Click OK.

  3. Create a new DWORD key called Debug. Assign it a decimal value of 1. Click OK.

  4. Create a new DWORD key called ConsoleLogLevel. Assign it a decimal value of 6. Click OK

  5. Restart the 2X Terminal Server agent service.

  6. Verify that logging enabled in the Console > Farm > Settings > right click on required Terminal Server Agent > Enable Logging

  7. Reproduce the issue and collect a copy of the TSAgent from the installation directory > AppData folder that is located on appropriate Terminal Server.

Detailed logging for Gateway Agent

  1. In the registry editor create a key

    HKEY_LOCAL_MACHINE\SOFTWARE\Parallels\2XProxyGateway 
    

    Note: (For 64bit operating systems check the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Parallels\2XProxyGateway key)

  2. Create a new DWORD key called LogLevel. Assign it a decimal value of '6'. Click OK.

  3. Create a new DWORD key called Debug. Assign it a decimal value of 1. Click OK.

  4. Create a new DWORD key called ConsoleLogLevel. Assign it a decimal value of 6. Click OK

  5. Reproduce the issue and collect a copy of the RASLogFile from the installation directory > AppData folder.

  6. Reproduce the issue.

  7. Please send us a copy of the RASLogFile from the installation directory > AppData folder.

Detailed logging for Guest Agent

  1. Connect to the VM via HTML5 Gateway.
  2. Enable Debug on the client machine by doing as follows:
    • Navigate to the registry under HKLM > Software > Parallels > GuestAgent
    • Create DWORD: Debug with a value of 1
    • Create DWORD Loglevel with a value of 6
    • Create String File; with a value of C:\guestlog.txt
    • All Logging will be created to the outlined txt file.
  3. Compress log file to archive.

Logs from Parallels Client

To enable client logging in Parallels Client go to Options > 'Enable logging'.

The log file log file will be in:

    "C:\Users\%username%\Application Data\2XClient\ClientLog.txt"

To enable detailed logging on the client:

  1. Verify that Client logging is enabled(RAS Client go to Options > 'Enable logging').
  2. Close RAS Client completely.
  3. In Registry Editor go to

     HKEY_CURRENT_USER\Software\Parallels\AppServerClient.
    
  4. There is LogLevel value which is 3. Change it to 6.

  5. Start Parallels Client and reproduce the issue.

  6. The log file will be in users Application Data\2XClient, e.g: "C:\Users\%username%\Application Data\2XClient\ClientLog.txt"

Alternatively, you may use scripts  to set detailed logging:

  1. Folderpermissions.sh – set permissions on files 
  2. Controller.sh – detailed log for Publishing Agent
  3. GW.sh – detailed log for Gateway
  4. RDS – detailed log for RD session host
  5. AllinOne.sh – detailed log for all components and set files permissions.

#- INTERNAL (content below this line is not visible in published article) -

Elevated cmd commands:

NOTE: After enabling L6 via cmd, services need to be restarted, same as in manual procedure.

NOTE: If regedit is already open at the relevant key, new values will be visible after refresh (F5).

Publishing Agent

x64

Add:

REG ADD HKLM\Software\Wow6432Node\Parallels\2XController && REG ADD HKLM\Software\Wow6432Node\Parallels\2XController /v LogLevel /t REG_DWORD /d 6 && REG ADD HKLM\Software\Wow6432Node\Parallels\2XController /v Debug /t REG_DWORD /d 1 && REG ADD HKLM\Software\Wow6432Node\Parallels\2XController /v ConsoleLogLevel /t REG_DWORD /d 6

Delete:

REG DELETE HKLM\Software\Wow6432Node\Parallels\2XController /v LogLevel && REG DELETE HKLM\Software\Wow6432Node\Parallels\2XController /v Debug && REG DELETE HKLM\Software\Wow6432Node\Parallels\2XController /v ConsoleLogLevel

x32

Add:

REG ADD HKLM\Software\Parallels\2XController && REG ADD HKLM\Software\Parallels\2XController /v LogLevel /t REG_DWORD /d 6 && REG ADD HKLM\Software\Parallels\2XController /v Debug /t REG_DWORD /d 1 && REG ADD HKLM\Software\Parallels\2XController /v ConsoleLogLevel /t REG_DWORD /d 6

Delete:

REG DELETE HKLM\Software\Parallels\2XController /v LogLevel && REG DELETE HKLM\Software\Parallels\2XController /v Debug && REG DELETE HKLM\Software\Parallels\2XController /v ConsoleLogLevel

Terminal Server

x64

Add:

REG ADD HKLM\Software\Wow6432Node\Parallels\TSAgent && REG ADD HKLM\Software\Wow6432Node\Parallels\TSAgent /v LogLevel /t REG_DWORD /d 6 && REG ADD HKLM\Software\Wow6432Node\Parallels\TSAgent /v Debug /t REG_DWORD /d 1 && REG ADD HKLM\Software\Wow6432Node\Parallels\TSAgent /v ConsoleLogLevel /t REG_DWORD /d 6

Delete:

REG DELETE HKLM\Software\Wow6432Node\Parallels\TSAgent /v LogLevel && REG DELETE HKLM\Software\Wow6432Node\Parallels\TSAgent /v Debug && REG DELETE HKLM\Software\Wow6432Node\Parallels\TSAgent /v ConsoleLogLevel

x32

Add:

REG ADD HKLM\Software\Parallels\TSAgent && REG ADD HKLM\Software\Parallels\TSAgent /v LogLevel /t REG_DWORD /d 6 && REG ADD HKLM\Software\Parallels\TSAgent /v Debug /t REG_DWORD /d 1 && REG ADD HKLM\Software\Parallels\TSAgent /v ConsoleLogLevel /t REG_DWORD /d 6

Delete:

REG DELETE HKLM\Software\Parallels\TSAgent /v LogLevel && REG DELETE HKLM\Software\Parallels\TSAgent /v Debug && REG DELETE HKLM\Software\Parallels\TSAgent /v ConsoleLogLevel

Gateway:

x64

Add:

REG ADD HKLM\Software\Wow6432Node\Parallels\2XProxyGateway && REG ADD HKLM\Software\Wow6432Node\Parallels\2XProxyGateway /v LogLevel /t REG_DWORD /d 6 && REG ADD HKLM\Software\Wow6432Node\Parallels\2XProxyGateway /v Debug /t REG_DWORD /d 1 && REG ADD HKLM\Software\Wow6432Node\Parallels\2XProxyGateway /v ConsoleLogLevel /t REG_DWORD /d 6

Delete:

REG DELETE HKLM\Software\Wow6432Node\Parallels\2XProxyGateway /v LogLevel && REG DELETE HKLM\Software\Wow6432Node\Parallels\2XProxyGateway /v Debug && REG DELETE HKLM\Software\Wow6432Node\Parallels\2XProxyGateway /v ConsoleLogLevel

x32

Add:

REG ADD HKLM\Software\Parallels\2XProxyGateway && REG ADD HKLM\Software\Parallels\2XProxyGateway /v LogLevel /t REG_DWORD /d 6 && REG ADD HKLM\Software\Parallels\2XProxyGateway /v Debug /t REG_DWORD /d 1 && REG ADD HKLM\Software\Parallels\2XProxyGateway /v ConsoleLogLevel /t REG_DWORD /d 6

Delete:

REG DELETE HKLM\Software\Parallels\2XProxyGateway /v LogLevel && REG DELETE HKLM\Software\Parallels\2XProxyGateway /v Debug && REG DELETE HKLM\Software\Parallels\2XProxyGateway /v ConsoleLogLevel



1d70d1f9c41d01c5f7202a4290e434e1

FEEDBACK
Was this article helpful?
Tell us how we may improve it.
Yes No