Application doesn’t launch under FireDaemon
Often FireDaemon services are run off other local drives eg. E: F: etc. These drives could be a new local disk array, iSCSI targets or SAN LUNs. If you find your app is not launching under FireDaemon control then ensure you have checked that the Security permissions includes SYSTEM / Full Control. You need to check this as when you add a new drive to a machine and format with NTFS this permission is not automatically set. To check this:
- Go to My Computer and look for the local drive you want to check.
- Right click on the local drive and select Properties.
- Click on the Security tab
- In the list of “Group or user names” look for SYSTEM. If it is not there click Edit
- A new dialog box will be displayed titled “Permissions for E:”
- Click Add
- A new dialog box will be displayed titled “Select Users or Groups”
- In the “Enter the object names to select” type SYSTEM and click the Check Names button.
- Click OK
- Then in “Permssions for E:” dialog check Full Control
- Then click OK twice.
Your FireDaemon apps should launch correctly.
No comments yet.
Leave a comment
Recent Posts
- Passwordless root SSH Public Key Authentication on CentOS 6
- Setting up DHCP on an Enslaved VLAN Bridge on CentOS Linux
- Identifying BlueArc Mercury M100 Hardware Revision
- BlueArc EVS Routing
- Disabling CIFS Authentication on a BlueArc EVS In Standalone Security Mode
- Running TeamSpeak 3 Server As A Service With FireDaemon
- Configuring iSCSI on CentOS 5.6
- Disable pagefile – will it increase Windows Server performance?
- How do I increase my Game Performance
- Scheduling a Service to run once per day.