Troubleshooting
My extension connects but API calls are being rejected. What should I check?
The most common causes are:
-
Missing right in the LIC file — Every API method the Module calls must be listed under
<Rights>in the LIC file as a<Method>or<Scope>entry. Check the API reference page of the failing function for the required method name, then add it to the LIC file. -
WinGuard API access right not granted — Even if a method is listed in the LIC file, WinGuard has its own per-Extension access rights layer (read, write, control). If an Extension-specific access rule was created in WinGuard without explicitly granting the needed right, the call will be blocked. The required access right is documented in the remarks section of each API function’s detail page.
-
Skill version mismatch — Using an API feature introduced in a newer Skill version than the one declared in
<Compatibility>can result in errors or silent failures. -
Wrong station — In multi-station setups, confirm the Module is connected to the station where the queried data actually resides.
→ See Licensing for the LIC <Rights> reference and How does licensing and signing work? for the full two-layer permission model.
WinGuard refuses to start my extension. What are the common causes?
| Error / symptom | Likely cause and resolution |
|---|---|
| “Unsigned license or invalid signature” | The LIC file has no Advancis signature and the developer license is not active. Enable the developer license on the WinGuard instance or obtain a signed LIC file. |
| “Module not found in system license” | The Module code in the LIC file is not registered in the WinGuard system license. Contact Advancis. |
| “Required/Provided skills are incompatible” | The WinGuard version does not support the Skill version declared in <Compatibility>. The error response includes a skills map showing which versions WinGuard actually supports. Adjust your declaration accordingly. |
| “JWT expired” or “JWT already used” | The JWT has expired or was already consumed in a previous connection attempt. Generate a fresh JWT for each new connection. |
| Module starts but immediately disconnects | The Manifest XML is malformed, a required XML definition file is missing, or the declared Skill version is incompatible with the installed WinGuard version. Check the WinGuard and Extension log files for details. |
| “Too many connections” | The system license restricts the number of simultaneous connections for this Module code. |
→ See WebSocket IPC: Connection errors for the full error reference and Manifest for Manifest structure requirements.