Event ID 100 Reported from vmauthd on Windows Vista Host after switching to Workstation 6.0.1

[Bleistein]

We were running VMWare Workstation on a Windows Vista (Ultimate) Host. Version 6.0.0 worked without generating error events in the event log. After switching to Version 6.0.1 (and using our previously working VM's the following event is recorded in the event log everytime we start VMWare workstation for every known virtual machine:

Cannot connect to VMX: .vmx

Log Name: Application

Source: vmauthd

Event ID: 100

We enabled logging for the vmauthd process and got the following log entries:

Sep 21 08:52:00.088: app| Log for VMware Workstation pid=4708 version=6.0.1 build=build-55017 option=Release

Sep 21 08:52:00.091: app| Hostname=MAC

Sep 21 08:52:00.091: app| Log file is vmauthd.log

Sep 21 08:52:00.333: app| totalPhysicalMemoryInBytes = 3202101248, totalPhysicalMemoryInPages=781763

Sep 21 08:52:00.333: app| Slack(1024) Skip (1)

Sep 21 08:52:00.333: app| minPercentTotalMemForMonitor=50

Sep 21 08:52:00.333: app| minTotalMemForMonitorInPages=390881

Sep 21 08:52:00.334: app| HostFilterInit: No host policy file found or HQ not enabled and no policy server configured. Not initializing filter.

Sep 21 08:52:00.335: app| Service Started.

Sep 21 08:52:05.333: app| Initialize hardLimit.

Sep 21 08:52:10.379: app| HardLimitMonitor. Too many page faults (8748). Scale limit down to 586400

Sep 21 08:52:11.716: app| Username associated with named pipe: mb

Sep 21 08:52:11.717: app| HOSTINFO 197827853717 @ 14318180Hz -> 0 @ 1000000Hz

+Sep 21 08:52:11.717: app| HOSTINFO ((x * 2399728063) >> 35) + -13816550263+

Sep 21 08:52:11.729: app| CreateFile on pipe
.\pipe\C:\Users\mb\Virtual Machines\Windows Vista\Windows Vista.vmx failed 2.

Sep 21 08:52:11.729: app| Cannot connect to VMX: C:\Users\mb\Virtual Machines\Windows Vista\Windows Vista.vmx

Sep 21 08:52:15.400: app| HardLimitMonitor. Too many page faults (11195). Scale limit down to 586383

Sep 21 08:52:20.420: app| HardLimitMonitor. Too many page faults (15857). Scale limit down to 586369

Sep 21 08:52:25.448: app| HardLimitMonitor. Too many page faults (15588). Scale limit down to 585405

Sep 21 08:52:30.471: app| HardLimitMonitor. Too many page faults (15801). Scale limit down to 584544

Sep 21 08:52:35.492: app| HardLimitMonitor. Too many page faults (14536). Scale limit down to 582192

Sep 21 08:52:40.515: app| HardLimitMonitor. Too many page faults (12356). Scale limit down to 581442

Sep 21 08:52:45.535: app| HardLimitMonitor. Too many page faults (11594). Scale limit down to 580623

Sep 21 08:52:50.558: app| HardLimitMonitor. Too many page faults (13889). Scale limit down to 579812

The system works without any visible problems. Any idea how to get rid of the error logs in the application event log?

[Racecar56]

@topic maker

This topic lived long...

Could it be a bug with your ancient version of VMware?

Try upgrading to 6.05.

[admin]

It's a known bug. It affects Workstation 6.5.0 too. This should be addressed in a future release.

[Uberdemon]

Thanks for the information darkrain777 your fix worked for me. I recommend trying this fix, if you haven't already. I didn't even have to install or reinstall the WM Ware bridging protocol. All I had to do was check it.

I was having this issue on the a Windows XP host running VM Ware Server. It was strange because I had two guest VM's one Windows XP and one CentOS 5 VM. The Windows VM was fine, but the CentOS VM was having networing issues.

When troubleshooting this issue remember to use direct IPs instead of DNS names (since there could also be a DNS issue also). Try to hit an internal IP address first, then try to hit an external IP address.