FireDaemon

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:

1. Go to My Computer and look for the local drive you want to check.
2. Right click on the local drive and select Properties.
3. Click on the Security tab
4. In the list of “Group or user names” look for SYSTEM. If it is not there click Edit
5. A new dialog box will be displayed titled “Permissions for E:”
6. Click Add
7. A new dialog box will be displayed titled “Select Users or Groups”
8. In the “Enter the object names to select” type SYSTEM and click the Check Names button.
9. Click OK
10. Then in “Permssions for E:” dialog check Full Control
11. Then click OK twice.

Your FireDaemon apps should launch correctly.

Tags: application doesnt launch, firedaemon, system permissions

Giving A Normal User Rights To Control A Service With subinacl

Normally starting and stopping a service requires administrator privileges, but you can assign a normal user the right to control an individual service. You do this with the subinacl.exe utility included in the Windows Resource Kit. You can also download it here:

http://www.microsoft.com/downloads/details.aspx?FamilyID=e8ba3e56-d8fe-4a91-93cf-ed6985e3927b&displaylang=en

To give the user “John” the right to start and stop the TestService service, log on as administrator and run the following command:

subinacl /SERVICE “TestService” /GRANT=john=TO

You can also give a user right to control a service through the use of Group Policies:

http://support.microsoft.com/default.aspx?scid=kb;en-us;288129

Correcting Clock Rollbacks / Rollforwards

If you modify your system clock whilst running FireDaemon in evaluation mode you might encounter this error:

Your system clock appears to have been set back, possibly in an attempt to defeat the security system on this program. Please correct your system clock before trying to run this program again. If your clock is correct, please contact the author of this program for instructions on correcting this error (report code 0,2853,2488).
› Continue reading

Tags: correcting clock rollbacks/rollforwards, firedaemon

PanelDaemon Won’t Install

When installing PanelDaemon, do you get errors like “The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2769. The arguments are: WEBCA_EvaluateURLsNoFail”

If so, then it is because you have no websites set up in IIS. First set up a website instance and then try the installation of PanelDaemon again.

If you have further problems, check out the installation guide at http://www.paneldaemon.com/manual/

Network Shares and FireDaemon

You can run an executable as a service under FireDaemon even if that executable resides on a network drive.

In order to run an executable off of a network drive the following must occur or be true:

1. The executable must be placed in a directory that is shared out

2. The executable can be normally referenced via mapped drive (eg. L:\path\file.exe) or via UNC path (eg. \\server\share\path\file.exe).

3. Mapped drives or UNC paths can only be used if the service is run as a nominated local or domain user (see next point).

4. If you intend to run the service as a nominated local or domain user then that user has must have permission to access the network resource (ie. share) in question. Further, if you want your application to Interact With The Desktop then you need to ensure that the local or domain user is in the Administrator’s group.

5. If you want to use a mapped drive then you are going to have to setup a Pre-Service Program to complete the mapping.

6. The application working directory can be either a mapped drive or UNC path – however, if a UNC path is used, a trailing slash (\) must be supplied (eg. \\server\share\path\).

See http://forums.firedaemon.com/do-use-mapped-drives-t38.html for more information.

Tags: firedaemon, network shares, UNC path

Unable to install FireDaemon

If you’ve ever encountered an error like “Installaware Wizard: Setup database not found” while trying to install FireDaemon or other applications, the reason is because your MSI database might be corrupt.

The MSI database stores information about all installed MSI applications.
› Continue reading

Tags: corrupt msi database, firedaemon, install error

Pre-Post Service Executable’s die before they run

If your Pre-Service or Post-Service executable is dying before it has a chance to run, the problem is that the execution time is too low. By default, it is set to 3000ms (3 Seconds). Try setting it to something higher (you might have to keep increasing until you find the proper time).

Tags: execution time, firedaemon, post-service, pre-service