VMware Cloud Community
Dennis318
Contributor
Contributor

Vmware tools generates Windows events: Event ID: 1000

We use Windows server 2003 R2 and ESXi 5.1. We use Vmware tools 9.0.5 build 1065307.

In our event logs we sometimes see this message:

vmware fout.PNG

Event Type:Error
Event Source:VMware Tools
Event Category:None
Event ID:1000
Date:6/16/2013
Time:5:00:24 AM
User:NT AUTHORITY\SYSTEM
Computer:BL-VAP0017

Description:

[critical] [vmsvc:Glib] file ..\..\..\glib\gmain.c: line 2849: assertion `loop != NULL' failed

We dont have any problems on the server, been googling for this problem, no results. So if anyone has an idea... let us know!

Thanks!

Reply
0 Kudos
8 Replies
julienvarela
Commander
Commander

Hi,

Did you try to uninstall and reinstall vmware tools?

Regards,

Julien.

Regards, J.Varela http://vthink.fr
Reply
0 Kudos
Dennis318
Contributor
Contributor

We have it on 100 servers. So we could reinstall vmware tools, but still it be nice to know what it is first...

Reply
0 Kudos
jrmunday
Commander
Commander

Hi Dennis,

Have you seen this KB link;

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2036350


Cheers,

Jon

vExpert 2014 - 2022 | VCP6-DCV | http://www.jonmunday.net | @JonMunday77
Reply
0 Kudos
Dennis318
Contributor
Contributor

I've seen it now.

But that is not our error message...

Thanks

Reply
0 Kudos
bigvern2
Contributor
Contributor

did you get an answer for this - we are getting exactly the same message

Reply
0 Kudos
bigvern2
Contributor
Contributor

not the same error - as the orginal poster has replied earlier

Reply
0 Kudos
jjgunn
Enthusiast
Enthusiast

Try this & let me know if it is helpful

Go to C:\Documents and Users\All Users\Application Data\VMware\VMware Tools

Create a file tools.conf In the file put this (I only used [unity] as the other portion disables logging which I didn't want to do)

[unity]

pbrpc.enable = false

[logging]

vmusr.level = error

vmsvc.level = error

Go to C:\Program Files\VMware\VMware Tools\plugins\vmusr

and rename unity.dll to unity.dll.orig or an extension of your choosing.

Reboot

Hope this is helpful for someone

Reply
0 Kudos