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:
- Check the Windows event logs. They usually reveal exactly what's happening.
- Try running your service as the user you installed the application as. This user should be a local or domain administrator. To change the service's user credentials, set them in the Login section in the Settings tab: /manual/SettingsTab.html
- The local file system permissions might be wrong. See our article on file system permissions for more information and how to correct your permissions.
- If the executable is on a mapped drive or UNC path, your path might be in the wrong format. See our article on using mapped drives and UNC paths for more information and how to run an executable on another drive.
- Are you remotely connected via RDP? Make sure the "Shadow Console" is enabled. See our article on viewing interactive services via RDP for more information.
- 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're still not sure what's going no, you can send a support ticket and attach the debug log to your ticket.