VMware tools Error
We recently upgrade our ESXI hosts to 5.1
On a few of the VM's we are getting the below error message.
[warning] [vmuser:vmusr] Error in the RPC receive loop: RpcIn: Unable to send
I need to know the root cause and a solution that we can use that will not require any downtime.
On a few of the VM's we are getting the below error message.
[warning] [vmuser:vmusr] Error in the RPC receive loop: RpcIn: Unable to send
I need to know the root cause and a solution that we can use that will not require any downtime.
ASKER
I checked that link before posting here. this is what i get when i follow the url.
We're sorry, but this Document is not currently available
We're sorry, but this Document is not currently available
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Both
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2036350
and
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2035778
Take me to the page that displays We're sorry, but this Document is not currently available
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2036350
and
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2035778
Take me to the page that displays We're sorry, but this Document is not currently available
ASKER
Also when searching Vmware KB
Your search - Error in the RPC receive loop: Rpci: Unable to send - did not match any documents.
No pages were found containing "Error in the RPC receive loop: Rpci: Unable to send".
Suggestions:
Make sure all words are spelled correctly.
Try different keywords.
Try more general keywords.
Your search - Error in the RPC receive loop: Rpci: Unable to send - did not match any documents.
No pages were found containing "Error in the RPC receive loop: Rpci: Unable to send".
Suggestions:
Make sure all words are spelled correctly.
Try different keywords.
Try more general keywords.
Both of the links you posted work for me...maybe clear your browser cache or try a different computer?
ASKER
this thread
http://communities.vmware.com/thread/419192
has the solution you are talking about in it. I am testing now.
http://communities.vmware.com/thread/419192
has the solution you are talking about in it. I am testing now.
ASKER
Change made. Will see if it works. Looks like it only happens durring times of high volume.
It seems that the upgrade didn't create the file tools.conf
You can create it like this:
[logging]
log = true
# Enable tools service logging to vmware.log
vmsvc.level = debug
vmsvc.handler = vmx
# Enable new "vmusr" service logging to vmware.log
vmusr.level = error
vmusr.handler = vmx
# Enable "Volume Shadow Copy" service logging to vmware.log
vmvss.level = debug
vmvss.handler = vmx
Save it as tools.conf in the appropriate folder for the guest OS.
Windows XP and Windows Server 2000/2003
C:\Documents and Settings\All Users\Application Data\VMware\VMware Tools\tools.conf
Windows Vista, Windows 7, and Windows Server 2008
C:\ProgramData\VMware\VMwa
Linux, Solaris, and FreeBSD
/etc/vmware-tools/tools.co
After saving and closing, restart the Tools service.
It seems that the upgrade didn't create the file tools.conf
You can create it like this:
[logging]
log = true
# Enable tools service logging to vmware.log
vmsvc.level = debug
vmsvc.handler = vmx
# Enable new "vmusr" service logging to vmware.log
vmusr.level = error
vmusr.handler = vmx
# Enable "Volume Shadow Copy" service logging to vmware.log
vmvss.level = debug
vmvss.handler = vmx
Save it as tools.conf in the appropriate folder for the guest OS.
Windows XP and Windows Server 2000/2003
C:\Documents and Settings\All Users\Application Data\VMware\VMware Tools\tools.conf
Windows Vista, Windows 7, and Windows Server 2008
C:\ProgramData\VMware\VMwa
Linux, Solaris, and FreeBSD
/etc/vmware-tools/tools.co
After saving and closing, restart the Tools service.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2036350
There is a fix, but unfortunately, it does require a server reboot. However, if you use vMotion, you won't have any downtime.