ASR Agent installation error: CRITICALEXCEPTION hit during prepare for install: System.IO.FileNotFoundException: Could not load file or assembly 'SystemRequirementValidator, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies

Question

When attempting to install the Classic Azure Site Recovery Mobility Agent on a windows vm on premise, i receive this error:

CRITICALEXCEPTION hit during prepare for install: System.IO.FileNotFoundException: Could not load file or assembly 'SystemRequirementValidator, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

Answer 1

Hello McDonald, Justin,

Before you start ensuring that the configuration server, scale-out process servers, and any master target servers that are a part of your deployment are updated as per your mobility agent version.

And another common reason for failure could be because of an unsupported operating system. Use a supported operating system for a successful installation of the Mobility service. Avoid the use of private patches.

To view the list of operating systems supported by Azure Site Recovery, see the support matrix document. additionally,

• ensure that all server configurations meet the criteria.
• Locate the installer for the server's operating system.

Additionally, the error you are encountering, "System.IO.FileNotFoundException: Could not load file or assembly 'SystemRequirementValidator, Version=0.0.0.0'", typically indicates that a required file or assembly is missing during the installation process of the Azure Site Recovery Mobility Agent. This can happen due to several reasons, such as:

1. Missing Dependencies: The installation might require certain dependencies that are not present on the system. Ensure that all prerequisite components are installed.
2. Corrupted Installation Files: The installation files for the Mobility Agent may be corrupted or incomplete. Re-downloading the installation package might help.
3. Permissions Issues: There could be permission-related issues preventing the installer from accessing necessary files. Ensure that you are running the installation with sufficient privileges.
4. Registry Issues: Sometimes, registry entries related to previous installations can cause conflicts. Cleaning up the registry or ensuring that no remnants of previous installations exist may resolve the issue. Open regedit.mscand check accordingly.
5. Compatibility Issues: Ensure that the version of the Mobility Agent you are trying to install is compatible with your operating system and environment.

If the issue persists, reviewing the installation logs located at C:\ProgramData\ASRSetupLogs may provide more detailed information about the failure.

For your reference: https://learn.microsoft.com/en-us/azure/site-recovery/vmware-physical-mobility-service-overview#install-the-mobility-service-using-command-prompt-classic

---

If the provided solution works for your query, please do not forget to Upvote it. this can be beneficial to other community members.it would be greatly appreciated and helpful to others.

Thanks