MachineWithSameBiosIdAndFqdnAlreadyExists

Question

I have been unable to enable replication on one single machine (out of 25+). I have found the following error in the ASRUnifiedAgentConfigurator log:

ERROR 7476 3592 1610 RcmClientLib::RcmClientProxyImpl::ProcessErrorResponse: request completed with non-XML response. HTTP response code: 409, response data :

<RcmError xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/RcmContract">

<ActivityId>85e1e0c4-3c0f-4df0-a88e-71ff6ba4f4d0</ActivityId>

<ComponentErrorCode i:nil="true" />

<ComponentErrorMessage i:nil="true" />

<ComponentErrorPossibleCauses i:nil="true" />

<ComponentErrorRecommendedAction i:nil="true" />

<ComponentErrorSeverity i:nil="true" />

<ComponentId i:nil="true" />

<ConsumerId i:nil="true" />

<ErrorCode>MachineWithSameBiosIdAndFqdnAlreadyExists</ErrorCode>

<ErrorSeverity>Error</ErrorSeverity>

<IsComponentReportedError>false</IsComponentReportedError>

<Message>Installation of mobility agent failed as prerequisites are not met.</Message>

<PossibleCauses>The operation failed due to an internal error.</PossibleCauses>

<RecommendedAction>Retry the operation. If the issue persists, contact support. Learn more (https://aka.ms/BIOSID_conflict).</RecommendedAction>

<ErrorCategory>ClientError</ErrorCategory>

<IsRetryableError>false</IsRetryableError>

<MessageParameters xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays" />

<ComponentErrorMessageParameters xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays" />

</RcmError>

I have gone through the same log for every other machine and have not found a duplicate BIOS ID or FQDN. 95 percent of the VMs are hosted in VMware. There are no duplicate UUIDs. Is there a place to check on the replication appliance to see if there's a duplicate entry that can be removed?

Also, I went to the link mentioned in the error log (https://aka.ms/BIOSID_conflict), and it did not provide any information for the modernized experience. Any help would be greatly appreciated since this particular device is very critical.

Answer 1

Hi @Derek Keith

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

Check your Azure Site Recovery settings. Go to the Recovery Services Vault in the Azure portal and look through the Replicated Items section. Search for the machine causing the issue and ensure there are no duplicate or orphaned entries. If you find any, remove them. If you're using an on-premises replication appliance, it might be holding onto cached data that’s causing this conflict. You can clear the cached data from the ASR management console to refresh the system.

And check again the machine’s BIOS ID and FQDN. Run the command wmic bios get serialnumber on the affected machine to verify the BIOS ID and ensure its unique. Also, confirm that the machine’s FQDN is properly configured and hasn’t been used before. Afterward, try uninstalling and reinstalling the mobility agent on the machine. Sometimes this helps fix the error by resetting the configuration.

If you have any concerns, please do through this link: -

https://learn.microsoft.com/en-us/azure/site-recovery/

https://learn.microsoft.com/en-us/azure/site-recovery/vmware-physical-azure-troubleshoot-process-server

If you have any further queries, do let us know

---

If the answer is helpful, please click "Upvote it"