Tag Archive for bug

Fix for VMware Remote Console unrecoverable error: (vmrc)

Uber quick post here with a very simple fix.

I got the following error when upgrading my C# viclient from 5.5 to 6.0 and connecting to my new vSphere 6 vCenter instance, and even when connecting to older ESXi hosts directly. (Yes I’m a bit old school – not a web client fan even after several years!).

The following error was observed after connecting and authenticating to vCenter, when the screen was populated with objects. I also could not then connect to any VM console as it said it was disconnected.

---------------------------
VMware Remote Console Error
---------------------------
VMware Remote Console unrecoverable error: (vmrc)
GetProcAddress: Failed to resolve ENGINE_load_aesni: 127
You can request support.  

To collect data to submit to VMware technical support, run "vm-support".
We will respond on the basis of your support entitlement.

 
It turns out that this is an issue with the remote console plugin. All I needed to do to fix it was:

  1. Rename the following folder C:\Program Files (x86)\Common Files\VMware\VMware Remote Console Plug-in 5.5 to anything you like (e.g. VMware Remote Console Plug-in 5.5-backup)
  2. Uninstall the vSphere 6.0 viclient
  3. Reinstall the vSphere 6.0 viclient
  4. Finito!

Simple fix for a silly little bug which is most likely related to me running an older version of VMware Workstation on my machine (in my case v8 but it could apply to any older version potentially).

NanoLab – Part 5 – Intel NUC BIOS Update Issues FwUpdateFullBuffer

Having taken delivery of a new Intel NUC D34010WYKH this week, I followed the usual (and Intel recommended process) of upgrading the firmware / BIOS to the latest version. As it happens, this was version 0030 (WY0030.BIO). This was installed using the standard USB with a .BIO file, and press F7 method as there was obviously no OS installed.

Unfortunately having installed this version, building and booting the ESXi host, I was getting some very strange network issues. Specifically no DHCP address being picked by the host, but a manual IP would ping intermittently (around 10-15% of the time). Not good. In addition there were some very odd behaviours observed in the BIOS such as not booting from USB consistently, hanging when I hit ctrl-alt-del and others.

My guess was that this was a firmware related issue, so I decided to roll it back to an earlier version. I started with 0026 by installing the firmware using the same F7 method above. This is when I got an error message which stated FwUpdateFullBuffer followed by several numbers (no screenshot I’m afraid). At this point, the firmware update bombed out. Really not good!

Repeating the activity only achieved the same result, even with different firmware versions and install methods (such as a bootable USB drive with FreeDOS and iFlash2.exe).

After a bit of searching I found the following BIOS recovery mode instructions for situations when you have a screwed up BIOS:

  1. Copy the recovery file (*.bio) to a bootable USB device.
  2. Plug the USB device into a USB port of the target Intel NUC.
  3. Shut down the computer and unplug AC power.
    jumper
  4. Open the chassis and remove the yellow BIOS Configuration Jumper. See the Technical Product Specification for the location of this jumper.
  5. Power the system on.
  6. Wait 2-5 minutes for the update to complete.

    Intel NUC BIOS Recovery from 0030 to 0025

    Intel NUC BIOS Recovery from 0030 to 0025

  7. The computer will either turn off when the recovery process is completed or it will prompt you to turn off the computer.
  8. Remove the USB device from the USB port.
  9. Replace the BIOS Configuration Jumper.
  10. Restart the computer.

Following the above, I have updated my Intel NUC D34010WYKH to version 0025 and have found it to be reasonably stable so far, and definitely works with ESXi.

Obviously follow any of the above suggestions at your own risk. I cannot be held responsible if your NUC becomes a BRICK, but hopefully this will save people some time and frustration, as this was several hours of messing around in my case!

%d bloggers like this: