Passed the VCP-DCV exam yesterday!
When trying to log into the AutoLab vCenter server with the vi-admin account you get an error that says, “The vSphere Client could not connect to vc.lab.local. You do not have permission to login to the server: vc.lab.local”.
Cause – The vi-admin account does not have Administrator permissions in vCenter.
Solution – Log in using the email@example.com account with a password of VMware1.lab. That account info is missing from the AutoLab documentation. Once logged in you can assign the vi-admin account Administrator permissions to vCenter.
When installing Windows Server 2012 R2 on a VM (vSphere or Hyper-V) configured for EFI you may receive the following error when booting to the ISO. “Windows failed to start. A recent hardware or software change might be the cause. To fix the problem… File: \EFI\Microsoft\Boot\BCD. Status: 0xc000014c. Info: The boot Configuration Data for your PC is missing or contains errors.”
When loading the VMware Paravirtual SCSI driver you receive an error that says, “No new devices drivers were found. Make sure the installation media contains the correct drivers, and then click OK.”
The installation cannot load any SCSI driver & says, “A media driver your computer needs is missing.”
“No device drivers were found. Make sure that the installation media contains the correct drivers, and then click OK.”
Cause – Corrupted ISO
Solution – Re-download the ISO & try again. In my experience ISOs can become corrupt if you pause them when downloading.
In the vSphere Web Client when navigating to Manage>Settings>General on the vCenter server the page says “Loading” but never loads.
To resolve the issue restart the VMware vSphere Web Client service.
Description – When upgrading vCenter Operations Manager (vCOps) from 5.8.0 to 5.8.1 you get an error as the PAK file is being uploaded just before the EULA screen should appear.
The error in red is long as can be. Here is just a snippet of the first few lines.
If you go back & try again you will notice that the path says C:\fakepath\VMware-vcops-5.8.1-1637685.pak regardless of the path to the file. In my case the PAK file is in C:\Temp.
Cause – Incompatibility with Internet Explorer 11.
Workaround – Use Firefox to upgrade vCOps. Now when you try the update it just says VMware-vcops-5.8.1-1637685.pak. But this time after clicking Update the update proceeds as normal.
C:\fakepath sounds a little fishy. Now surely VMware didn’t do that on purpose.
Description – When powering on a vApp you receive an error that says, “Cannot initialize property ‘vami.netmask0.VM_1’. Network ‘VM Network’ has no associated network protocol profile.”
Cause – The IP Pool is not associated to a Virtual Machine Port Group.
Solution – Open the IP Pool settings & select the Associations tab. Put a check by the network that the vApp will run on (e.g. VMNetwork) & click OK. Now power on the vApp.
Description – After installing the vSphere Web Client version 5.5.0a you notice the following issues:
- You get a “Page cannot be displayed” error when opening the vSphere Web Client.
- The VMware vSphere Web Client service will not start.
- You have an Event ID 7024 in the System Log that says, “The VMware vSphere Web Client service terminated with the service-specified error Incorrect function..”
Cause – This can happen if there is not enough RAM in the vCenter Server.
Solution – Have at least 4GB of RAM in the vCenter Server.
There was also a very similar issue in version 5.1.0 where the vSphere Web Client service would not start. In that case it had to do with the directory where the client was installed. In 5.1.0 the default path is C:\Program Files\VMware\Infrastructure\vSphere WebClient. In 5.5.0a the default path is C:\Program Files\VMware\Infrastructure\vSphereWebClient. (No spaces in vSphereWebClient). If you are having this issue with 5.1.0 have a look at KB2012473.
Today I passed the VCA-Cloud exam. I also passed the VCA-DCV on 10/15/2013 & the VCA-WM on 10/20/2013.
Now on to the VCP5-DCV!
Description – When connecting to a server’s console you receive an error that says, “Unable to connect to the MKS: Failed to connect to server esxi01.laptoplab.net:902”
Cause – This is due to a DNS problem where the computer connecting to the console cannot resolve the name for the ESXi hosts. This is likely to happen in a lab environment. If this is happening in a production environment then you need to troubleshoot why you cannot resolve the names for your ESXi hosts. May be a sign of a bigger problem.
Solution/Workaround – Create HOSTS file entries for the ESXi hosts management IPs.
- Download the ESXi ISO.
- Download UNetbootin.
- Insert a blank USB thumb drive & format it using FAT32.
- Run UNetBootin.
- Select Diskimage.
- Select ISO from the dropdown.
- Click the ellipse button & browse to the ESXi ISO.
- By Type select USB Drive.
- By Drive select the letter for the USB thumb drive.
- Click OK.
- If you get a message saying E:\menu.c32 already exists click Yes to All.
- When it is finished click Exit.
- Insert the USB drive into the host & boot from USB.
- From the boot menu select the ESXi installation option & press Enter
- Finish the installation just like any other ESXi install