Process ID Changes Every Few Seconds

If the process of your FireDaemon Service is changing rapidly, it’s probably because it’s crashing, not starting correctly or terminating.

Generally it can be a pain to troubleshoot this kind of problem, but there are a few things you can do to fix it:

1. Check the windows event logs, they usually reveal exactly what’s happening.
2. The local file system permissions might be wrong, see http://forums.firedaemon.com/system-permission-local-drives-t648.html for more information.
3. If the executable is on a mapped drive or UNC path, your path might be in the wrong format, see http://forums.firedaemon.com/do-use-mapped-drives-t38.html for more information.
4. Are you remotely connected via RDP?  Make sure the “Shadow Console” is enabled.  See http://forums.firedaemon.com/accessing-shadow-console-via-t397.html for more information.
5. If all else fails, then enable Debug Logging in the FireDaemon Service, let the service run a few times and then look at the debug log to see what’s happening.  If you don’t understand it, you can send a support ticket and attach the debug log to your ticket.