Commented by: Sean Leyne (seanleyne)

"Remote Access Management Service" is only active on hosts which also have Remote Desktop Services/Terminal Services active, which is not a typical Firebird install environment.

Please try the Startup Type = "Automatic (Delayed Start)" setting in the Services Control Panel, on the Firebird service, and report back.

Commented by: KS (karlox)

We already tried with Startup Type = "Automatic (Delayed Start)". It led to the error to occur less frequently, but it still happened.

Commented by: Sean Leyne (seanleyne)

As I see it, as you point out, the problem is with your specific installation not with the Firebird engine. So, I don't believe that this issue should be considered a high priority change.

You could create a function to install/register the Firebird service or use the "SC.exe" command-line utility [https://support.microsoft.com/en-us/help/251192/how-to-create-a-windows-service-by-using-sc-exe ], to add the dependency on the "Remote Access Management" service. In this case, Windows would only start the Firebird engine after that service had been started.

Commented by: KS (karlox)

We also discussed the idea of defining a service dependency, but there are a number of concerns:

1. We don't want Firebird to be stopped when the "Remote Access Management" service is being stopped. I think this is what would happen with the dependency.
2. The "Remote Access Management" service may be present on the computer or not. Our setup would need to detect that etc., which may be not easy with the setup tools we're using.
3. Also, the "Remote Access Management" service might be added (or removed) later when our setup has completed already.
4. We're not even sure if that dependency would really resolve the problem in all cases. It may depend on the timing or the internal activities of the services after startup, not simply a question of the startup order.

Commented by: @hvlad

The patch was developed and tested by ticket author himself.
Thanks for contributing !