Skip to main content

11.5.322256: ESXi 4.1 - ABR11.5 Can't see 1 of 14 virtual machines - missing system is a DC

Thread needs solution

Sorry to bother you folks; I figure I have just as good a chance of getting my problem resolved here as through paid support since my final case with them took nine months to resolve poorly. So enhance your calm, my expectations are well below the water line here.
------
VMWare ESXi 4.1
ABR11.5 Build 11.5.322256
Currently 14 virtual machines running across two physical hosts.
Last week I brought up a machine I planned to use as a DC for a development project; this went without much ado.
Once I had the system patch stable and ready for its next step, I went to setup its back plan. But wait, the system is not listed in the ABR11.5 build 11.5.322256 anymore! What is amiss?
1. Has the DC crashed? No.
2. Are there errors in the vCenter logs? No.
3. Is the ABR11.5 build 11.5.322256 management workstation in the same domain as the DC? No.
4. Is the vCenter Server in a domain? No.
5. Did you reboot the vCenter, the ABR11.5 build 11.5.322256 appliance and supporting workstation? Yes.

Suggestions or more information required? Let me know.

0 Users found this helpful

Hello Systems Support,

Thank you for posting this question in our forum. I am happy to assist you. 

There are various reasons that can cause this issue. One of the most common issues can be found in the related vmx file of the affected virtual machine. Please check, that the GUID of this machine inside the vmx file is in correct written. Please note that it is case sensitive and the most letters have to be in lower case not in upper case. You can find additional information in this article from our knowledge base. It describes this kind of situation but in vmProtect. The solution will match to your environment as well. See Solution C there.

If you need additional assistance, please  contact support. You will find all available support options in our Customer handbook.

If there is anything else we can do for you, please let me know.

Thank you.

Peter Vigoureux wrote:

Hello Systems Support,

Thank you for posting this question in our forum. I am happy to assist you. 

There are various reasons that can cause this issue. One of the most common issues can be found in the related vmx file of the affected virtual machine. Please check, that the GUID of this machine inside the vmx file is in correct written. Please note that it is case sensitive and the most letters have to be in lower case not in upper case. You can find additional information in this article from our knowledge base. It describes this kind of situation but in vmProtect. The solution will match to your environment as well. See Solution C there.

If you need additional assistance, please  contact support. You will find all available support options in our Customer handbook.

If there is anything else we can do for you, please let me know.

Thank you.

Thank you for your reply Peter,
I reviewed the article and this does not seem to be my issue, all of the UUIDs are unique and all of the UUIDs are lower case in their respecetive vmx files.

As far as support goes, that last case that took nine months to close carried over beyond the anniversary date of the renewal and my boss wasn't interested in paying for support that took up 387 hours of my time to resolve one case badly. Ergo, this is all that is left to me.

I'm guessing I may have to go to the Windows method of backups; those I can at least rely on.

Hello Systems Support,

Thank you for your reply.

I want to apologize for the problems with our support. If you have any concerns or feedback regarding our support department, then please feel free to forward this to this email address managers@acronis.com.

Your next option is always to update to the current build 11.5.32308, which have a lot of fixes implemented. How you can find the product to download is described in this article from our knowledge base.

If there is anything else we can do for you, please let me know.

Thank you.