Problems with RSA Archer services
I have problems with RSA Archer services.
Sometimes the services stay "hung up", that is to say, it seems that they are in Running status because is indicated in the services tool, but it is not really so, since they are not running.
I also have problems stopping or starting a service, especially the "RSA Archer Job Engine" service. An error message appears when stopping or starting and we have to restart the machine to solve it. I attach the error message.
Could anyone help me? I have also written to the RSA support.
Thank you in advance.
- Community Thread
- Forum Thread
- Job Engine
- RSA Archer
- rsa archer services
- RSA Archer Suite
IIya Khen, the problem is that the RSA Archer Job Engine service doesn't work and I try to stop it but I can't. Also, when I stop the service, I try to start it, but is imposible.
On the other hand, I have another concern, but I forgot to put it before.
My main concern is that RSA Archer Job Engine service often stops by itself without any action taken by the user (that is, without forcing a reset or similarwise). Configuration service keeps however running, so RSA Archer platform seems to work normally but for datafeed, calulations and other jobs.
Cannot really say anything. Either you have some maintenance work or scheduled job running on server, which treats RSA services as something not needed, or services are corrupted.
Also, possible that environment is corrupted too.
In both cases, you need to work with IT team, then check all the logs, collect env information and provide to RSA support.
This requires environmental debugging, I would say.
You may also try to resintall services to see if helps.
And start with the ACP (Defined in the Archer Control Panel location) logs, they may reveal critical failures already.
Have you checked the Windows Event Viewer? This might provide a clue as to what's going on with the service. I've seen this before but it never affected jobs running in Archer...only when trying to do a restart of the service or a clean stop of all the services. As you've noted, restarting the server resolved the issue.
Let us know what you find out.