Error with Core tasks results with, "The semaphore timeout period has expired" (4036274)

Semaphore timeout errors may occur when mounting a recovery point, during a rollback of a volume, or during a virtual export. Mounting a recovery point is required for File Recovery, Roll Backs, Virtual Standby and Export, and Mountability and Attachability Checks.

TevoMountReplay failed with error -2147024775 (0×80070079 – The semaphore timeout period has expired)

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. In Web UI select Configuration, click Settings, scroll down to Replay Engine Configuration and click change.
2. Set Read and Write Timeout to 15:00
3. Stop the Core Service. How To Stop or restart the Core Service (4034348) (quest.com)
4. Make the following registry edits. NOTE: When adjusting values related to AAV timeouts it may require a reboot of the core machine for changes to take affect:
   • HKLM\SOFTWARE\AppRecovery\Core\ExchangeServiceConfiguration\MountabilityCheckingProcessTimeoutMinutes set to 1440 (Decimal)
   • HKLM\SYSTEM\CurrentControlSet\Services\AAVDisk\Parameters\NetworkTimeout set to 1800 (Decimal)
   • HKLM\SYSTEM\CurrentControlSet\Services\AAVDisk\Parameters\AsyncNetworkTimeout to 1800 (Decimal)
5. In elevated Command Prompt run "sc stop aavdisk". If AAVDisk will not stop, you must reboot core machine. If it does stop run "sc start aavdisk" to start service.
6. Start the Core Service and resume jobs.

Solution 2:  Used in addition to other Solutions or applied singularly

1. Go to Configuration tab, Settings, Replay Engine Configuration, and select change.
2. Set IP Address to 127.0.0.1 (local host IP), select OK

Solution 3:  Used in addition to other Solutions or applied singularly

1. Check Page File settings. Verify they are set to automatic or between 1.5 – 3 X system RAM
2. If any changes are made you must reboot Core. Stop the Core Service. How To Stop or restart the Core Service (4034348) (quest.com)
3. Reboot Core, start the Core Service, and resume jobs

Solution 4:  Transfers fail between protected machine to the Core

1. The solution can be viewed in the KB article Error "The semaphore timeout period has expired" on Agent Transfers (4037019) (quest.com)

Solution 5:  Errors using the Local Mount Utility

1. The solution can be viewed in the KB article Semaphore Timeout when mounting recovery points using Local Mount Utility (4038438) (quest.com)