ESXi

 View Only
  • 1.  VMware Tools error in Windows 2008 terminal server

    Posted Sep 17, 2015 03:09 PM

    I'm running vSphere 5.5 update 2 and I just saw that I've been getting a lot of vmware tools channel restart errors like the one below on at least one of my Win2k8 R2 terminal server guests. Based on the log pattern, I'm guessing a log entry is created each time a user logs in or reconnects to a session. The vmware tools version is 9.4.12.45816. Is there a setting I need to change to fix this issue, or is it cosmetic?

    Thanks.

    Tim

    Log Name:  Application
    Source:    VMware Tools
    Date:      9/1/2015 12:21:37 PM
    Event ID:  1000

    Task Category: None

    Level:     Warning
    Keywords:  Classic
    User:      AD\userhere
    Computer:  host.domain.edu

    Description:

    [ warning] [vmusr:vmusr] Channel restart failed [1]



  • 2.  RE: VMware Tools error in Windows 2008 terminal server

    Posted Sep 17, 2015 06:42 PM

    Surprising as this isse is most likely to occur in older version of ESXi 5.x .

    Did you get a chance to have a look @ http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2038263 . Though it says its resolved in 5.5U2 , do a quick check if your setup require any of the change as mentioned.



  • 3.  RE: VMware Tools error in Windows 2008 terminal server

    Posted Sep 18, 2015 02:53 AM

    Can you post the error seen in vmware.log also. Have you upgraded only the vmware tools to 55u2 version or even the vmkernel is also in 55u2 version?



  • 4.  RE: VMware Tools error in Windows 2008 terminal server

    Posted Sep 18, 2015 05:55 PM

    Everything is running 5.5u2 (Esxi, vcenter). I need to enable debugging to get vmware tool logs, right?



  • 5.  RE: VMware Tools error in Windows 2008 terminal server

    Posted Sep 18, 2015 07:44 PM

    no , you could find tools logs in vmware.log file created under datastore where VM resides.

    path to logs : $ cd  /vmfs/volumes/<datastore>/<vm>

    then run $less vmware.log and see if you find any errors