Archive
Version mismatch with vmx86 driver
Well, it happened again. I upgraded VMware Workstation from 16.1.0 to 16.1.1. After rebooting I started a VM & got an error that said, “Version mismatch with vmx86 driver: expecting 401.0, got 308.0. You have an incorrect version of driver ‘vmx86.sys’. Try reinstalling VMware Workstation. Failed to initialize monitor device.”
I clicked OK & got another error that said, “Transport (VMDB) error -14: Pipe connection has been broken.”
The vmx86.sys file sounded familiar. Sure enough, I had a very similar problem last year & wrote a blog post about it.
https://patrickhoban.wordpress.com/2020/04/05/failed-to-start-the-vmware-authorization-service
Long story short, there’s an old version of the vmx86.sys file again. Do a repair on VMware Workstation, reboot, & try again.
Quick Post: MSVCR120.dll not found
Description – When running an OpenSSL command on Windows, you receive an error that says, “The code execution cannot proceed because MSVCR120.dll was not found. Reinstalling the program may fix this problem.”
Solution – Download & install “Visual C++ Redistributable Packages for Visual Studio 2013”. MSVCR120.dll is included in that package.
https://www.microsoft.com/en-ph/download/details.aspx?id=40784
Failed to start the VMware Authorization Service
When starting a VM I received an error that said, “VMware Workstation failed to start the VMware Authorization Service. You can try manually starting the VMware Authorization Service. If this problem persists, Contact VMware support.”
Looks like both the VMware Authorization Service & VMware Workstation Server service aren’t running.
I try to start VMware Authorization Service but get an error that says, “Windows could not start the VMware Authorization Service on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 6000009.”
Checking the Event Log I find one System event & three Application related events.
Event ID: 7024
Log Name: System
Source: Service Control Manager
Message: The VMware Authorization Service service terminated with the following service-specific error:
%%6000009
Event ID: 1000
Log Name: Application
Source: vmauthd
Message: Version mismatch with vmmon driver: expecting 385.0, got 308.0.
Event ID: 1000
Log Name: Application
Source: vmauthd
Message: Try reinstalling VMware Workstation.
Event ID: 1000
Log Name: Application
Source: vmauthd
Message:
Yes, the third application event really did have a blank message.
I don’t see any references in the registry or file system for anything named “vmmon”. I notice that the VMware Authorization Service depends on VMware vmx86 & it was running.
Get-Service -Name “VMware vmx86”
Below are the details for the VMware vmx86 service from the registry. Note that the ImagePath is “\SystemRoot\system32\DRIVERS\vmx86.sys”.
The properties of vmx86.sys show a File Version of 12.5.1.3 & build date of 6/19/2017. That seems pretty old for VMware Workstation 15.5 from 2020.
Let’s try a repair.
Using the PendMoves utility from SysInternals, it would appear the vmx86.sys file is going to be updated on reboot.
After the reboot, everything looks much better. Services are running.
vmx86.sys now has a file version of 15.0.0.84 dated 3/7/2020.
But most importantly, all VMs powered on properly.
What’s interesting about this issue is that about 5 months ago I upgraded from VMware Workstation version 12.5.7 to 15.5.1 & everything has been working. Which means that VMware Workstation version 15.5.1 works with vmx86.sys version 12.5.1.3. The issue started after upgrading from VMware Workstation 15.5.1 to 15.5.2.
If the repair doesn’t work for you, I also found a VMware KB article that walks you through manually removing the vmx86 service. In the end, you still have to reinstall.
Error Installing HP iLO Firmware Upgrade
When trying to install a firmware update for the HP Integrated Lights-Out 3 (iLO) you receive an error that says, “The software will not be installed on this system because the required hardware is not present in the system or the software/firmware doesn’t apply to this system.”
Looking in Device Manager, there is a device called Base System Device under Other devices.
Looking at the properties of Base System Device, the Device status says, “The drivers for this device are not installed. (Code 28).” On the Details tab the Hardware Ids property shows a value of PCI\VEN_103C&DEV_3307&SUBSYS_3309103C&REV_04.
The mystery device is the iLO 3 (CHIF). As of the date of this post, the latest version of the iLO 3/4 Channel Interface driver is 3.30.0.0. https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_e74f93921947408eb5de783d27
The installation is pretty quick & in my case did not require a reboot. Below are screenshots from the installation.
Next, install the iLO 3/4 Management Controller. As of the date of this post, the latest version is also 3.30.0.0.
https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_e196fcb67e1941de959751786f
Just like the interface controller, the installation is pretty quick & in my case did not require a reboot. Below are screenshots from the installation.
Now try the iLO firmware upgrade & it will work. Below are screenshots from the installation.
Quick Post: Error uninstalling CA iTechnology iGateway
Description
When uninstalling CA iTechnology iGateway you receive an error that says, “The iGateway can not uninstall because the following components are still using the iGateway: Spindles defined in Spin.conf. Please remove the above components before uninstalling the iGateway again.”
Solution
Browse to C:\Program Files\CA\SharedComponents\iTechnology & open spin.conf in Notepad.
Remove the line that says:
<Spindle Prefix=”/ITMClient” Directory=”” Spar=”ITMClient.spar” Description=”ITMClient” Version=”8.1″ Config=””>ITMClient</Spindle>
Save the file then try to uninstall again.
Error Changing Drive Letter
When changing the drive letter in Disk Manager you may receive an error that says, “The parameter is incorrect”.
This can happen is the pagefile is on that drive. Move the pagefile to a different drive, reboot, then try again.
Exchange is So Sensitive
After demoting a Domain Controller you get an error every 5 minutes on your Exchange Server that says, “SACL Watcher servicelet found that the SeSecurityPrivilege privilege is removed from account SID.”
Restart the Microsoft Exchange Active Directory Topology service (MSExchangeADTopology). Keep in mind this will also restart several other services that are disruptive to users so try to do this after hours.
As a side note to find which object the SID belongs to run LDP.exe & use the SID Lookup tool.
Windows Update Error Code 80070308
Warning: This post deals with editing the registry. If you don’t know what that is stop right here & ask someone else to help you. Using the registry incorrectly can cause serious problems that may require you to reinstall Windows. Use the registry at your own risk.
Description – When running Windows Update you receive an error that says, “Code 80070308”
Rebooting does not resolve the issue. Stopping the Windows Update service & deleting everything in C:\Windows\SoftwareDistribution does not resolve the issue.
Solution – Open Regedit & browse to HKLM\COMPONENTS. Delete the PendingRequired value name.
Click Yes when prompted then close Regedit.
Now run Windows Update again.
Now go get a beer & celebrate!
Error Deactivating DHCP Scope
On Windows Server 2008 R2 when using netsh to deactivate a DHCP scope you get an error that says, “The command needs a valid Scope IP Address”.
Try again using an elevated PowerShell prompt.
Installation hangs on “Windows Installer Coordinator”
When installing IBM i Access for Windows on a Windows Server 2008 R2 Remote Desktop Services host it may hang on a dialog box that says, “Windows Installer Coordinator. Please wait while the application is preparing for the first use”.
It’s weird that I’ve been using Windows Server 2008 R2 for so long & never ran into this issue.
Anyway, to resolve the issue open gpedit.msc (or create a GPO, whatever you prefer) . Browse to Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Application Compatibility. Set Turn off Windows Installer RDS Compatibility to Enabled. Now run the installer again.
Visitors
Patrick's Blog 