NOW-proto worker has been terminated
We currently use RDM 2026.3.12 on our "normal" notebooks and the same version on our PAW.
From time to time the following error appears and stops all new connections from working:
"jump to connection failed: NOW-proto worker has been terminated."
There dont seem to be any related information in the application logs of the RDM running on the PAW.
But the application Log of our notebooks appear to have the following entrys:
[08.10.2026 09:07:27 - 2026.3.12.0 - 64-bit] suppressed error: Devolutions.NowClient.NowClientException: NOW-proto worker has been terminated.
at Devolutions.NowClient.NowClient.ThrowIfWorkerTerminated()
at Devolutions.NowClient.NowClient.SetRdmAppNotifyHandler(RdmAppNotifyHandler handler)
at Devolutions.RemoteDesktopManager.Business.NowAgent.NowAgent.SetRdmAppNotifyHandler(RdmAppNotifyHandler handler)
at Devolutions.RemoteDesktopManager.Business.NowAgent.NowAgent.StartAndWaitForRdmReady(Int32 timeoutSeconds, CancellationToken cancellationToken)
at Devolutions.RemoteDesktopManager.Business.NowAgent.NowAgent.Jump(Connection targetConnection, JumpedConnectionResult jumpedConnectionResult)
All Comments (2)
Hello,
Thank you for the details and the log excerpt.
This error means RDM on your notebook lost its link to Devolutions Agent on the PAW, so every new jump in that RDP session fails.
To clear it, disconnect the RDP session to the PAW and connect again.
Since you are already on the latest versions, we would like to look into this with our development team.
Next time it happens, please send us the Agent logs from the PAW and the exact time of the error.
Please also let us know if the same account is ever connected to the PAW in more than one session.
Finally, does the error tend to appear after the session was idle, locked, or reconnected?
Best regards,
Carl Marien
Hello,
Thank you for the details and the log excerpt.
This error means RDM on your notebook lost its link to Devolutions Agent on the PAW, so every new jump in that RDP session fails.
To clear it, disconnect the RDP session to the PAW and connect again.
Since you are already on the latest versions, we would like to look into this with our development team.
Next time it happens, please send us the Agent logs from the PAW and the exact time of the error.
Please also let us know if the same account is ever connected to the PAW in more than one session.
Finally, does the error tend to appear after the session was idle, locked, or reconnected?
Best regards,
Hey Carl @Carl Marien
sure i will provide the log if the error happens to appear again.
I use multiple Jump Sessions via the same PAW but never open multiple session to the paw from my notebook.
Honestly i cant exactly pin point when it happens but i would say it happens after unlocking my windows session or after a idle period of rdm.
I dont know if it matters, but we use Yubikeys for Login to the Notebook and the PAW.
Best regards,
Moritz Heppert