RASInsider
← All articles
April 9, 2026 / Tools / Troubleshooting / 2 min read

RAS Log Decoder — Decode your Parallels RAS logs instantly

RAS Log Decoder — Decode your Parallels RAS logs instantly

// TOOLS / LOG-DECODER

RAS Log Decoder

Reading a raw Parallels RAS log is tedious. The format mixes hexadecimal module codes, thread and process identifiers, timestamps, and messages that can span tens of thousands of lines. The RAS Log Decoder parses all of it instantly — without sending any data to a server.

→ Open the RAS Log Decoder


What the tool decodes

Every Parallels RAS log line follows a structured format that the official documentation does not fully detail. The decoder extracts all fields:

  • Level (E / W / I / D / T) — Error, Warning, Info, Debug, Trace — color-coded at a glance
  • Module hex code — the hexadecimal component identifier, translated into a readable name from 107 referenced modules
  • Component name — PUBAGENT, HTML5GW, PA_SAML, ENROLLSERVER, HALBAGENT, SCARDHOOKER…
  • Date and time in separate columns for faster reading
  • Session ID (S/) and Correlation ID (C/) when present — essential for tracking a user session across log files

Supported formats

The decoder handles all three log formats produced by Parallels RAS:

  • Standard format — controller.log, gateway.log, redundancy.log, EnrollServer.log, tsagent.log, vdiagent.log and all classic UTF-16LE logs
  • HTML5GW format — HTML5GW.log, with its specific date format and decimal module codes
  • MSI/Windows format — RASMsi.log, which mixes standard RAS lines with native Windows MSI traces

100% local processing

Your logs contain Active Directory usernames, internal IP addresses, machine names and sometimes authentication information. None of this data leaves your browser: decoding runs entirely in client-side JavaScript. The RASInsider server receives nothing.

How to use it

  1. Open your log file in any text editor (Notepad++, VS Code…)
  2. Copy the lines you are interested in — a few dozen or several thousand, it doesn’t matter
  3. Paste into the decoder’s text area
  4. Click Decode
  5. Filter by level (E/W/I/D/T) and by module to quickly isolate what is causing the issue
  6. Use Last ⇥ to jump directly to the end of the log — that is usually where the error is

RAS logs are UTF-16LE on Windows. Copy them from your usual text editor, the decoder handles encoding automatically.


→ Open the RAS Log Decoder

Want to see RASInsider first in Google’s Top Stories?Add RASInsider as a preferred source on Google

Did this article help?