Return
-
Title
Agent Service Starts and then Immediately Stops -
Description
When attempting to start the AppAssure agent service, the program begins to initialize but immediately stops thereafter.
Additionally, the following message may appear in your Windows System Events.
“The AppAssure Agent Service service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example the Performance logs and Alert Service”
The Event ID 100 might also while trying to start the service. This event has the following description:
"Error while trying to start Agent service: System.Net.HttpListenerException (0x80004005): The process cannot access the file because it is being used by another process at System.Net.HttpListener.AddAllPrefixes() at System.Net.HttpListener.Start() at Replay.ServiceHost.Implementation.Hosting.ListenerService.StartListening(Action`1 requestHandler, Func`2 errorHandler, Action`1 oneWayRequestHandler, IEnumerable`1 additionalUris) at Replay.ServiceHost.Implementation.Hosting.ServiceHost.StartListening() at Replay.ServiceHost.Implementation.Services.ServicesContainer.Start() at Replay.Agent.Service.Agent.Start() at Replay.Agent.Service.AgentService.OnStart(String[] args)" -
Resolution
Complete the following steps.
- Ensure that the system Application Events log is not full and is not set to Do not overwrite events.
- Right click the Application Log and select Properties to view and modify these options.
- Ensure that all of the agent’s dependencies are not disabled in services.msc and that they do not fail to start in system events. These dependencies are found in the Agent Service Properties/Dependencies Tab and may include the following.
- Cryptographic Services
- HTTP
- IPsec Policy Agent
- Network Connections
- Windows Event Log
- WinHTTP Web Proxy Auto-Discovery Service
- Review the system events for service start failure due to TCP Port 8006 being used in another process. Reinstall the agent if necessary, changing the agent port to an unused port, per netstat.
- To accomplish this, follow the steps in this KB article: Change agent ports for server protection.
- Ensure that the agent hardware meets the minimum requirements (4 GB of RAM).
- Ensure that the system Application Events log is not full and is not set to Do not overwrite events.