Blog

Tuesday, March 05, 2013

FireDaemon Service does run and 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. 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
  3. The local file system permissions might be wrong, see http://forums.firedaemon.com/threads/system-permission-on-local-drives.648/ for more information.
  4. If the executable is on a mapped drive or UNC path, your path might be in the wrong format, see http://forums.firedaemon.com/threads/how-do-i-use-mapped-drives-and-or-unc-paths.38/ for more information.
  5. Are you remotely connected via RDP?  Make sure the "Shadow Console" is enabled.  See
    http://forums.firedaemon.com/threads/accessing-the-shadow-console-via-remote-desktop-rdp-using-mstsc-admin-or-console.397/ for more information.
  6. 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.
Comments
Post has no comments.



Captcha Image

Recent Posts



Tags


Archive

    Sign up for Product Updates and Discounts
    Captcha Image
    ×