Share via

Azure Site Recovery – "Invalid source config file provided" during UnifiedAgentConfigurator registration

shelly kapoor 0 Reputation points
2025-12-11T06:38:09.2433333+00:00

Hello Team,

While configuring Azure Site Recovery Mobility Service for VMware/EC2 replication, the following error appears:

UnifiedAgentConfigurator.exe /SourceConfigFilePath "config_fixed.json" /CSType CSPrime
Starting silent configuration.
Running configuration for VmWare
Starting registration for CSPrime
Source config file for registration - config_fixed.json
Preparing for registration
Invalid source config file provided.

Steps I already tried:

  1. Regenerated passphrase

Verified JSON format

Ensured correct path and permissions

Tried using MobSvc.passphrase

Environment:

ASR Mobility Agent version: (add your version)

Source machine OS: (Windows version)

Replication type: VMware → Azure

Question: What causes this "Invalid source config file provided" error, and how do I fix the configuration file so UnifiedAgentConfigurator accepts it?

Thanks!
Hello Team,

While configuring Azure Site Recovery Mobility Service for VMware/EC2 replication, the following error appears:

UnifiedAgentConfigurator.exe /SourceConfigFilePath

Steps I already tried:

Regenerated passphrase

Verified JSON format

Ensured correct path and permissions

Tried using MobSvc.passphrase

Environment:

ASR Mobility Agent version: (add your version)

Source machine OS: (Windows version)

Replication type: VMware → Azure

Question:
What causes this "Invalid source config file provided" error, and how do I fix the configuration file so UnifiedAgentConfigurator accepts it?

Thanks!

Azure Site Recovery
Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. Siva shunmugam Nadessin 3,345 Reputation points Microsoft External Staff Moderator
    2025-12-11T10:10:04.4733333+00:00

    Hello shelly kapoor,

    Thank you for reaching out to the Microsoft Q&A forum.

    Here are some troubleshooting steps and suggestions that may help resolve the issue:

    1. Configuration Compatibility: First, ensure that the settings in your config_fixed.json file align with the requirements listed in the Azure Site Recovery support matrix. If any parameters are outside the supported configurations, it could trigger this error.
    2. Check JSON Formatting: Even though you've mentioned you've verified the JSON format, it's a good idea to double-check for any syntax errors or missing fields that could be causing the UnifiedAgentConfigurator to reject the file. Online JSON validators can help ensure it's correctly formatted.
    3. Validate Path and Permissions: Make sure that the path to config_fixed.json is correct, and the account running the configuration has sufficient permissions to read the file. This includes checking for any hidden characters in the file path that might be causing issues.
    4. Agent Installation: Ensure that the ASR Mobility Agent is properly installed on the source machine. You can check the installation status in the Azure portal or by querying the services on the machine.
    5. Consult the Log Files: You may find additional diagnostic information in the log files located at %ProgramData%\ASRSetupLogs\ASRUnifiedAgentConfigurator.log. This file can provide specific insights on why the source config file was not accepted.
    6. Try Regenerating the Config File: If you suspect that there might be an issue with the existing config file, consider regenerating it following the steps in the ASR setup guidelines.
    7. Network Connectivity: Ensure that there are no network connectivity issues between the source machine and the ASR service.

    If these steps don’t resolve the issue, you may need to provide more context for further troubleshooting. Here are a few follow-up questions that could help clarify the situation:

    • What version of the ASR Mobility Agent are you using?
    • What operating system is the source machine running (include version)?
    • Can you share specific sections of the config_fixed.json file (anonymized if necessary) to review its structure?
    • Are there any specific error codes or messages in the logs that you can share?
    • Have you checked if there are any known issues or restrictions with the VMware/EC2 configuration you are using?

    I hope this helps you move forward with fixing the issue! Let me know if you need more assistance.

    References:

     

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.