Question & Answer
What causes the issDaemon service to terminate with service error 4294967295?
This issue stems from a corrupted issDaemon.policy file.
Follow the steps below to reset the issDaemon.policy file from an existing copy:
- Open services.msc and stop the issDaemon service.
- Go to the \Program Files\ISS\issDaemon\ directory.
- Rename the issDaemon.policy file to issDaemon.policy.old.
- On the Application Server machine, browse to the \Program Files\ISS\SiteProtector\Application Server\temp\Sensor Controller\EventCollector_ @x.x.x.x\ directory.
- Find the file ending with .daemon.
Note: If this file does not exist in this directory, check in \Program Files\ISS\SiteProtector\Application Server\temp\Sensor Controller\AgentManager_ @x.x.x.x\ as this is the same .daemon file as in the EventCollector directory.
- Copy this file to the \Program Files\ISS\issDaemon\ directory and rename it to issDaemon.policy so that it replaces the original file. If the agent exists on a different server, you must copy the file from the Application Server to the other server.
- Start the issDaemon service.
If the SiteProtector Sensor Controller service is not running, follow the steps below:
- Stop the issDaemon service.
- Stop the SiteProtector Application Server service.
- Copy \Program Files\ISS\SiteProtector\Application Server\License\Repository\LicRep.xml to a different location.
- Start the issDaemon and SiteProtector Application Server services and check to see that LicRep.xml was recreated.
All services should now start successfully and the agents should return to an active state.
16 June 2018