I'm not sure why, but I have a few Windows Server 2019 servers where the "Veeam Explorers Recovery Service" fails to start. Event Viewer doesn't really shed any light on the issue, as all it says is:
The Veeam Explorers Recovery Service service terminated with the following error:
An exception occurred in the service when handling the control request.
When I look at the Veeam.StandBy.Service log (C:\ProgramData\Veeam\Backup\ExplorerStandByService\Logs), I see this:
Error: Could not load file or assembly 'Veeam.SQL.StandBy.Service.Server, Version=184.108.40.206, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
But it doesn't seem to give me the file name that it is missing...
Anyone see this before or have any ideas before I open a ticket?
Most probably it's related to "Veeam.SQL.StandBy.Service.Client.dll" or "Veeam.SQL.StandBy.Service.Contract.dll" in this folder:
C:\Program Files\Veeam\Backup and Replication\Explorers\SQL
You may check "File version" field in file properties (Properties - Details) to see whether it matches the current version of Veeam B&R or not. However, I recommend to delegate troubleshooting task to our support team and to avoid unnecessary attempts to fix the issue as it can make the whole situation more complicated for our engineers who will analyze the issue. Please share a support case ID for our reference.
220.127.116.11 for both. I applied P20211123 earlier today, and don't know if this service was failing to start prior to that, but I'm guessing it was. And I know I saw this at another client location atleast 3 weeks ago...
Ok - found a file count discrepancy in "C:\Program Files\Common Files\Veeam\Backup and Replication\Explorers Recovery Service". On the server where it isn't starting, there are 123 items when viewed with Windows Explorer. On my NFR test box, there are 159 files in the same folder, for P20211123.
I'm not sure why this discrepancy is occurring though.