Hello,
Last week we upgraded our vsphere servers to version 6. Today I notice that on our RDS server, there are a lot of events from VMware Tools, like every couple of seconds (see below). VMware Tools is up to date on this server, and all vsphere updates are installed on the host as well. The RDS server is Windows Server 2012, with about 10 clients active on it. The only thing I can find on the net, is this: VMware KB: Installing VMware Tools 5.1/5.5 on a Windows virtual machine reports Unity warnings in Wi..., but that doesn't help. I hope someone here has any other ideas? Thanks !!
Logboeknaam: Application
Bron: VMware Tools
Datum: 1/06/2015 12:09:17
Gebeurtenis-id:1000
Taakcategorie: Geen
Niveau: Warning
Trefwoorden: Classic
Gebruiker: <domain user>
Computer: <servername>
Beschrijving:
[ warning] [vmusr:vmusr] SimpleSock: Socket 564 closed by peer.
Gebeurtenis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VMware Tools" />
<EventID Qualifiers="0">1000</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-06-01T10:09:17.000000000Z" />
<EventRecordID>91063</EventRecordID>
<Channel>Application</Channel>
<Computer>SRVRD1.server.vmv.lan</Computer>
<Security UserID="S-1-5-21-1955156641-1582828314-1617787245-4268" />
</System>
<EventData>
<Data>[ warning] [vmusr:vmusr] SimpleSock: Socket 564 closed by peer.
</Data>
</EventData>
</Event>
Try the tools.conf vmusr level, didnt work
Спасибо это помогло.
Hi,
Here few steps which may help you..
To resolve this issue, install the VMware Tools packaged with ESXi 5.1 Update 2 or ESXi 5.5 Update 2 on the affected virtual machines.
To work around this issue, use one of these methods.
Method 1: Disable Protocol Buffer Remote Procedure Call (PBRPC)
tools.conf
file of the guest operating system using a text editor.C:\ProgramData\VMware\VMware Tools\
C:\Documents and Settings\All Users\Application Data\VMware\VMware Tools\
tools.conf
file, locate the line with the comment [unity]
and change the Pbrpc.enable
value from true
to false
.[unity]
Pbrpc.enable=false
Notes:
tools.conf
file does not exist, create a new file and use the content given above. Application Data/ProgramData
folder is usually hidden. Ensure that hidden files are viewable.
Method 2: Delete the Unity plug-in
C:\Program Files\VMware\VMware Tools\plugins\vmusr
Unity.dll
file. We are experiencing the same issue. 2012 R2 RDS server on vSphere 6.0. Hardware version 11. Tools are up to date and I have tried the tools.conf file found here: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=203826...
Has anyone found out more information on this issue?
I have logged the call with VMware support. When we have fixed it I will post the solution.
Any luck by chance? Just started having the same issue on a 2008 R2 terminal server that I just upgraded the tools on this morning. Thanks!
Yes this is the responce I got from support.
The Event entry stating "[warning] [vmusr: vmusr] SimpleSock: Socket xxx closed by peer" is said to be log spam and being created in error while logging the events by VMware tools. I have below mentioned the workaround and fix. Do review the same and update me on further proceedings of this Support Request.
Workaround:
----------
1.Add this section to the tools.conf file:
[logging]
vmusr.level = error
vmsvc.level = error
2. Restart VMware Tools Services
Resolution: The above mentioned logging information shall be updated at large in next upcoming release ESXi 6.0 Update.
The VMware Tools configuration file is named tools.conf
, and the default location is based on the guest operating system type and version:
Guest operating system | Path to configuration file |
Windows XP and Windows Server 2000/2003 | C:\Documents and Settings\All Users\Application Data\VMware\VMware Tools\tools.conf |
Windows Vista, Windows 7, Windows 8, Windows Server 2008 and Windows Server 2012 | C:\ProgramData\VMware\VMware Tools\tools.conf |
Linux, Solaris, and FreeBSD | /etc/vmware-tools/tools.conf |
Mac OS X | /Library/Application Support/VMware Tools/tools.conf |
I created in our case the file tools.conf in C:\ProgramData\VMware\VMware Tools\ and tommorow I will know the results.
Keep you guys posted.
Hi Inps1980,
Did the workaround fix the problem for you?
The problem has just started on one of my RD servers running on esxi 6.0
Hi Ordy56,
Yes this fixed the problem for us.
Cheers,
Patrick
If the file is absent and doesn't exist, do you just create it and cut and paste in the values? I already done it, so we'll see if this resolves the error notifications.
Worked great for me! I have a 2008 TS running and kept getting these logged errors in the Application logs. Creating this file and adding those params worked!
:smileylaugh: thanks for sharing. I allways like feedback good or bad