Subject: Systa exits before responding – still occurring with latest version 26.0.2.0 (Adobe AIR)
Hi Wyatt,
Following your suggestion, I've now updated both Systa and TurboActivate to the latest versions, but unfortunately the problem persists.
Running systa.exe directly in PowerShell confirms:
systa (NodeJS / Adobe AIR helper process) version: 26.0.2.0
TurboActivate library version: 26.0.2.0
The problem
Our Adobe AIR application, Hitmix Bingo, was working perfectly for this customer on Sunday, 1 November, but suddenly stopped working on Monday, 2 November, without any changes to the application.
The error appears immediately on startup:
The systa process ended before the response could be delivered.
We've enabled application logging and confirmed that the initial licensing check fails:
inside applicationComplete(), ta.IsGenuineEx(30,7,false);
inside onIsGenuineEx(), returned value
evt.ErrorObj = Error: The systa process ended
before the response could be delivered.
and evt.uintResponse = 0
We've also tried manually entering the customer's product key, but CheckAndSavePKey() produces exactly the same error.
Troubleshooting completed
- Updated both Systa and TurboActivate to version 26.0.2.0.
- Confirmed that Systa launches successfully from the application.
- Used Microsoft Process Monitor to establish that Systa exits with status
0, rather than crashing. - Confirmed that all required licensing files are present.
- Checked Windows Defender, Event Viewer and Reliability Monitor without finding any relevant crashes or security blocks.
- Tried running the application as administrator.
- Verified WMI functionality and Windows time synchronisation.
- Reinstalled/updated the application without success.
One complication
Unfortunately, the developer who originally created Hitmix Bingo is no longer working with us, and we don't have access to the original ActionScript source code.
We do have the compiled SWF and can replace the Systa and TurboActivate binaries, but modifying the ActionScript licensing integration would be difficult.
My questions are:
- Given that Systa exits with status
0 but fails to respond to both IsGenuineEx() and CheckAndSavePKey(), what could be causing this? - Is there a way to enable additional diagnostic logging directly within Systa to identify why it terminates?
- Could corrupted locally stored activation data cause this behaviour, and is there a safe way to investigate without losing the customer's activation?
- Are the latest Systa and TurboActivate binaries backward compatible with older Adobe AIR/ActionScript integrations?
As we've now updated both components to the latest versions and the issue remains, I'd really appreciate any further guidance.
Many thanks,
Nick
Hitmix Bingo