After Server Reboot Agent Will Not Start with Error, "AppAssure Agent Service on Local Computer started and then stopped." (4037750)

This problem will occur because:

1. Another process is using the port configured for the AppAssure Agent (default port is 8006 and configured at install)
2. The "ListenOnlyList" registry subkey has the wrong configuration or IP Address (seen in System Event Error 15005)

Windows Registry Disclaimer:

Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.

1. Verify that no other applications are running on the AppAssure port (default port is 8006):
   1. Open an elevated cmd prompt
   2. Issue command: netstat -aon | find "8006"
2. This can be Fixed by changing the port that Agent uses to communicate with core in 2 places on the agent's registry
   1. HKEY_local_machine>Software>AppRecovery>agent>InstallerParameter>Port adjust to 8011
   2. HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Agent\serviceHost\ServiceBaseAddress adjust to 8011
   3. If the port is not actively used by a process (identified by the PID) then the ListenOnlyList needs to be investigated
3. Investigate the ListenOnlyList:
   1. Open regedit
   2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters\ListenOnlyList
   3. Since modifying this registry could cause other functions or applications on your system from working properly through your network, please look into the following Microsoft article to address this issue as it lists the solutions. Further information can be found at the following Microsoft article: KB 890015.
4. If no errors are generated when attempting to start the agent service please verify that the Windows Application Logs are not full.  If they are full, please save the events and purge the log. It may also be beneficial to set the log retention policy to “overwrite events as needed” to ensure this problem does not recur.  Please see Set Log Retention Policy for more detailed information about log retention policies.
5. In the services console for the agent please ensure that the virtual disk service is enabled and started. Once that has been verified attempt to start the agent service.