<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>vividly nonsensical &#187; vCenter</title>
	<atom:link href="http://www.jirc.com/tag/vcenter/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jirc.com</link>
	<description>it just makes nonsense</description>
	<lastBuildDate>Thu, 26 Aug 2010 15:57:14 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>FAILED: A system error encountered during an operation</title>
		<link>http://www.jirc.com/2009/06/22/failed-a-system-error-encountered-during-an-operation/</link>
		<comments>http://www.jirc.com/2009/06/22/failed-a-system-error-encountered-during-an-operation/#comments</comments>
		<pubDate>Mon, 22 Jun 2009 16:06:58 +0000</pubDate>
		<dc:creator>mvarre</dc:creator>
				<category><![CDATA[tech]]></category>
		<category><![CDATA[vmware]]></category>
		<category><![CDATA[ESX]]></category>
		<category><![CDATA[HOSTS]]></category>
		<category><![CDATA[vCenter]]></category>
		<category><![CDATA[VI]]></category>

		<guid isPermaLink="false">http://www.jirc.com/?p=328</guid>
		<description><![CDATA[Anyone familiar with ESX will know how finicky it and vCenter can be about name resolution for all parties involved.  I typically make my VI and vCenter Server HOSTS file identical.  This usually solves all my HA problems and other weird issues that arise. Today I realized it&#8217;s also beneficial to duplicate the HOSTS file [...]]]></description>
			<content:encoded><![CDATA[<p>Anyone familiar with <a href="http://www.jirc.com/tag/esx/" class="st_tag internal_tag" rel="tag" title="Posts tagged with ESX">ESX</a> will know how finicky it and <a href="http://www.jirc.com/tag/vcenter/" class="st_tag internal_tag" rel="tag" title="Posts tagged with vCenter">vCenter</a> can be about name resolution for all parties involved.  I typically make my <a href="http://www.jirc.com/tag/vi/" class="st_tag internal_tag" rel="tag" title="Posts tagged with VI">VI</a> and <a href="http://www.jirc.com/tag/vcenter/" class="st_tag internal_tag" rel="tag" title="Posts tagged with vCenter">vCenter</a> Server <a href="http://www.jirc.com/tag/hosts/" class="st_tag internal_tag" rel="tag" title="Posts tagged with HOSTS">HOSTS</a> file identical.  This usually solves all my HA problems and other weird issues that arise.</p>
<p>Today I realized it&#8217;s also beneficial to duplicate the <a href="http://www.jirc.com/tag/hosts/" class="st_tag internal_tag" rel="tag" title="Posts tagged with HOSTS">HOSTS</a> file on a machine that is being converted from physical to virtual using <a href="http://www.jirc.com/tag/vcenter/" class="st_tag internal_tag" rel="tag" title="Posts tagged with vCenter">vCenter</a> Converter (the machine I am converting). Before I appended those entries to the I was receiving &#8220;<span style="font-family: courier new,courier;"><em>FAILED: A system error encountered during an operation.</em></span>&#8221; each time I tried running the conversion.  The error cleared up right away.</p>
<p>I still don&#8217;t know why this continues to be an issue. The infrastructures are setup as vanilla and as &#8220;by the book&#8221; as possible.  DNS and WINS are always setup and working properly.  Short name and FQDN resolution always works from every host and client on the network.</p>
<p>I suppose it isn&#8217;t the end of the world. Seems like it should be an easy thing for VMware to &#8220;fix&#8221;&#8230;then again maybe they don&#8217;t consider it to be broken.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jirc.com/2009/06/22/failed-a-system-error-encountered-during-an-operation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
