When I upgraded from vCenter 4.1 to 5.0, upon connecting back to the vCenter Server I noticed that one of my VM's was showing as invalid. I checked the .vmx file and it was corrupt. The bad news is that this particular VM is our main production SQL server but the good news is the VM is still running with no problems.
I can fix the .vmx with no problems by creating another one but does anyone know why this would have happened in the first place? Has it happened to anyone else?