Etap License Path Selection Verified Access

Here’s a brief technical write-up on the message "ETAP license path selection verified" in the context of ETAP (Electrical Transient Analysis Program) software licensing.


Part 8: Future of ETAP Licensing – What to Expect

As of the latest ETAP versions (20.8.0 and beyond), the company is gradually moving toward subscription-based named user licensing and cloud-hosted token verification. The classic hasplms server is being supplemented by direct HTTPS calls to ETAP’s authentication cloud.

In this new model, the “license path” becomes a URL like https://licensing.etap.com/api/v2/verify. The "ETAP license path selection verified" message will still appear, but it will now indicate an SSL/TLS handshake with a cloud server.

Prepare now by ensuring your corporate firewall allows outbound HTTPS to *.etap.com and that your system clock is synchronized via NTP (SSL certificates fail if time is off by more than 5 minutes). etap license path selection verified


Part 6: Advanced Insights – What the ETAP Logs Reveal

For the truly curious engineer, ETAP writes detailed license handshake logs. By default, logging is disabled. To enable it:

  1. Create a folder: C:\ETAP_Logs
  2. Set environment variable: ETAP_DEBUG_LICENSE=1
  3. Launch ETAP and reproduce the verification step.

You will see entries like:

[2024-01-15 14:32:11] INFO: License path selection initiated.
[2024-01-15 14:32:11] DEBUG: Parsing path "27000@192.168.1.100"
[2024-01-15 14:32:12] DEBUG: TCP socket to 192.168.1.100:27000 established.
[2024-01-15 14:32:12] INFO: ETAP license path selection verified. Server response: "OK 1.2.3"
[2024-01-15 14:32:13] DEBUG: Requesting feature "etap_main"...

If you see any line containing ERROR or TIMEOUT, you have found the exact reason for path verification failure. Here’s a brief technical write-up on the message


Steps for ETAP License Path Selection Verification

To verify the ETAP license path selection, follow these steps:

3.1 Using ETAP License Manager (The Recommended Method)

The ETAP License Manager is a standalone utility installed with every ETAP copy (Start Menu > ETAP > License Manager).

Steps:

  1. Launch ETAP License Manager as Administrator (right-click > Run as Administrator).
  2. Navigate to the “License Path” tab.
  3. Choose your license type:
    • Local License (Dongle): Select “Local” and click Apply. The path becomes local:.
    • Network License: Select “Network” and enter 27000@YourServerName. (Note: 27000 is the default port; confirm your server’s port).
    • Demo/File License: Browse to the .lic file.
  4. Click “Verify Path” button.
  5. A dialog box will appear. If successful, you will see: “ETAP license path selection verified – The license source is accessible.”

2.2 The Verification Workflow

Here is what happens behind the scenes when you launch ETAP:

  1. Step 1 – Path Reading: ETAP reads the license path from the system registry (HKEY_LOCAL_MACHINE\SOFTWARE\ETAP\Licensing) or an environment variable.
  2. Step 2 – Path Resolution: The software resolves hostname to an IP address via DNS or checks for a local USB dongle via the USB driver stack.
  3. Step 3 – Verification: A handshake occurs. The license server responds with a “hello” packet. A local dongle returns its serial number. This is when you see the “verified” message in debug logs.
  4. Step 4 – Feature Check: ETAP requests a specific feature (e.g., “etap_main,” “etap_arcflash”). If available, the license is acquired. If not, you get “No license available” despite the path being verified.

Understanding this sequence is paramount. A “verified” path is a green light for communication, not for usage.


2. What Triggers This Message?

This message typically appears:

  • During software startup.
  • After manually selecting a license path via the ETAP License Manager or License Selector utility.
  • When switching between different license types (e.g., standalone vs. network license).