{"id":311,"date":"2012-10-16T01:28:00","date_gmt":"2012-10-16T01:28:00","guid":{"rendered":"http:\/\/atumvirtwordpress.azurewebsites.net\/?p=311"},"modified":"2012-10-16T01:28:00","modified_gmt":"2012-10-16T01:28:00","slug":"vmware-tools-spew-their-words-not-mine","status":"publish","type":"post","link":"https:\/\/avtempwp.azurewebsites.net\/2012\/10\/vmware-tools-spew-their-words-not-mine\/","title":{"rendered":"VMWare Tools &#8220;Spew&#8221; &#8211; Their Words, Not Mine"},"content":{"rendered":"<p>Today I noticed one of my event logs was flooded with events that I had not seen before upgrading to VMware tools 5.1. \u00a0VMware so kindly describes it as such in <a href=\"http:\/\/kb.vmware.com\/selfservice\/microsites\/search.do?language=en_US&#038;cmd=displayKC&#038;externalId=2036350\">KB 2036350<\/a>, shown below. \u00a0<b>*Update*\u00a0<span>This issue is resolved in Patch ESXi510-201212402-BG. To download this patch see,\u00a0<\/span><a docid=\"2035778\" href=\"http:\/\/kb.vmware.com\/selfservice\/microsites\/search.do?cmd=displayKC&#038;docType=kc&#038;docTypeID=DT_KB_1_1&#038;externalId=2035778\" referto=\"referto\" target=\"_blank\" rel=\"noopener\">VMware ESXi 5.1., Patch ESXi510-201212402-BG: Updates tools-light (2035778)<\/a><span>.<\/span><\/b><\/p>\n<p><\/p>\n<h2>Upgrading to VMware Tools 5.1 causes log spew in the Windows Event Log: Error in the RPC receive loop<\/h2>\n<div>\n<h4>Symptoms<\/h4>\n<div><content>After upgrading a Terminal Server or Terminal Server-based Citrix XenApp virtual machine to VMware Tools 5.1:<br \/><\/content><\/p>\n<ul>\n<li>In the Windows Application Event log, you see this error reported multiple times in quick succession (log spew):\n<p><code>Error in the RPC receive loop: RpcIn: Unable to send.<\/code><\/li>\n<li>In the\u00a0<code>vmware.log<\/code>\u00a0file for the virtual machine, you see log spew of this error:\n<p><code>GuestRpc: Channel X reinitialized.<\/code><\/li>\n<li>User instances of\u00a0<code>vmtoolsd.exe<\/code>\u00a0crash with the error:\n<p><code>Access violation (0xC0000005)<\/code><\/li>\n<\/ul>\n<\/div>\n<h4>Resolution<\/h4>\n<div><content>This is a known issue, and is currently being reviewed by VMware.<\/p>\n<p>To work around this issue and alleviate the symptoms, you can disable VMware Tools logging to the Event Log and general virtual machine logging to the\u00a0<code>vmware.log<\/code>\u00a0file for the virtual machine.<\/p>\n<p><strong>To disable VMware Tools application event logging:<\/strong><\/content><\/p>\n<ol>\n<li>Edit the\u00a0<code>tools.conf<\/code>\u00a0file in a text editor.\n<p><b>Note<\/b>: To locate the\u00a0<code>tools.conf<\/code>\u00a0file, see the\u00a0<em>Configuration File Location<\/em>\u00a0section in\u00a0<a docid=\"1007873\" href=\"http:\/\/kb.vmware.com\/selfservice\/microsites\/search.do?cmd=displayKC&#038;docType=kc&#038;docTypeID=DT_KB_1_1&#038;externalId=1007873\" referto=\"referto\" target=\"_blank\" rel=\"noopener\">Enabling debug logging for VMware Tools within a guest operating system (1007873)<\/a>.<\/li>\n<li>Add this section to the\u00a0<code>tools.conf<\/code>\u00a0file:\n<p><code>[logging]<br \/>vmusr.level = error<\/code><\/li>\n<li>Save and close the file.<\/li>\n<li>Restart the VMTools Service (<strong>Administrative Tools<\/strong>\u00a0>\u00a0<strong>Services<\/strong>)<strong>.<\/strong><\/li>\n<\/ol>\n<p><strong>To disable general virtual machine logging:<\/strong><\/p>\n<ol>\n<li>Click the virtual machine in the Inventory.<\/li>\n<li>On the\u00a0<strong>Summary<\/strong>\u00a0tab for that virtual machine, click\u00a0<strong>Edit Settings<\/strong>.<\/li>\n<li>In the virtual machine\u00a0<strong>Properties<\/strong>\u00a0dialog box, click the\u00a0<strong>Options<\/strong>\u00a0tab.<\/li>\n<li>Under\u00a0<strong>Advanced<\/strong>, click\u00a0<strong>General<\/strong>\u00a0and deselect\u00a0<strong>Enable logging<\/strong>.<\/li>\n<li>Click\u00a0<strong>OK<\/strong>\u00a0to save the change.<\/li>\n<li>To make the change take effect, power off the virtual machine and power it back on again.\n<p><strong>Note<\/strong>: If you do not want to power off your virtual machine to disable logging, you can also vMotion the virtual machine after changing this setting.<\/li>\n<\/ol>\n<div><strong>Note<\/strong>: This issue may also occur on non-Terminal Servers, such as Windows 2008 and Windows 2003.<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Today I noticed one of my event logs was flooded with events that I had not seen before upgrading to VMware tools 5.1. \u00a0VMware so kindly describes it as such in KB 2036350, shown below. \u00a0*Update*\u00a0This issue is resolved in Patch ESXi510-201212402-BG. To download this patch see,\u00a0VMware ESXi 5.1., Patch ESXi510-201212402-BG: Updates tools-light (2035778). Upgrading [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[64,66],"tags":[],"_links":{"self":[{"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/posts\/311"}],"collection":[{"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/comments?post=311"}],"version-history":[{"count":0,"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/posts\/311\/revisions"}],"wp:attachment":[{"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/media?parent=311"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/categories?post=311"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/tags?post=311"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}