<?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>ERROR &#8211; Virtualization, DBaaS &amp; Whatever Crosses My Mind</title>
	<atom:link href="https://magander.se/tag/error/feed/" rel="self" type="application/rss+xml" />
	<link>https://magander.se</link>
	<description></description>
	<lastBuildDate>Thu, 18 Aug 2016 10:25:04 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://magander.se/wp-content/uploads/2021/01/cropped-Screenshot-2021-01-19-at-22.37.56-32x32.png</url>
	<title>ERROR &#8211; Virtualization, DBaaS &amp; Whatever Crosses My Mind</title>
	<link>https://magander.se</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>VMware vSphere Update Manager service fails</title>
		<link>https://magander.se/vmware-vsphere-update-manager-service-fails/</link>
					<comments>https://magander.se/vmware-vsphere-update-manager-service-fails/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Tue, 03 Mar 2015 09:34:13 +0000</pubDate>
				<category><![CDATA[vCenter Server]]></category>
		<category><![CDATA[1888318]]></category>
		<category><![CDATA[1932 Error]]></category>
		<category><![CDATA[2008]]></category>
		<category><![CDATA[2008 R2]]></category>
		<category><![CDATA[5.5.0]]></category>
		<category><![CDATA[5.5.0 VMware Update Manager]]></category>
		<category><![CDATA[5.5.0U1b]]></category>
		<category><![CDATA[7031]]></category>
		<category><![CDATA[7036]]></category>
		<category><![CDATA[Build]]></category>
		<category><![CDATA[Build 1888318]]></category>
		<category><![CDATA[ERROR]]></category>
		<category><![CDATA[Event ID 7031]]></category>
		<category><![CDATA[Event ID 7036]]></category>
		<category><![CDATA[he Application Experience service entered the stopped state]]></category>
		<category><![CDATA[jetty-vum-ssl.xml]]></category>
		<category><![CDATA[managedJetty]]></category>
		<category><![CDATA[no element found]]></category>
		<category><![CDATA[Service Control Manager]]></category>
		<category><![CDATA[The VMware vSphere Update Manager Service service terminated unexpectedly]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[vCenter Server 5.5.0U1b]]></category>
		<category><![CDATA[Version = 5.5.0]]></category>
		<category><![CDATA[VMware Update Manager]]></category>
		<category><![CDATA[vSphere Update Manager]]></category>
		<category><![CDATA[VUM]]></category>
		<category><![CDATA[VUM service fails to start]]></category>
		<category><![CDATA[Windows Server 2008 R2]]></category>
		<guid isPermaLink="false">http://magander.se/?p=4930</guid>

					<description><![CDATA[So a few days back i had some problem with the VMware Windows based vSphere Update Manager (VUM) Server that didn’t start after rebooting the virtual machine (VM) where the service runs. All other VMware related services running on the VM started without any problem. vCenter Server (and VUM) version running was 5.5.U1b was running &#8230; </p><p><a class="more-link block-button" href="https://magander.se/vmware-vsphere-update-manager-service-fails/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/vmware-vsphere-update-manager-service-fails/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>vCenter Orchestrator &#8211; Unable to run workflow</title>
		<link>https://magander.se/vcenter-orchestrator-unable-to-run-workflow/</link>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Fri, 03 Oct 2014 10:42:32 +0000</pubDate>
				<category><![CDATA[Other]]></category>
		<category><![CDATA[disable validation checking]]></category>
		<category><![CDATA[ERROR]]></category>
		<category><![CDATA[validate a workflow before running it]]></category>
		<category><![CDATA[validate workflow]]></category>
		<category><![CDATA[validation]]></category>
		<category><![CDATA[validation process]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[vCenter Orchestrator]]></category>
		<category><![CDATA[vCenter Orchestrator 5.5.1]]></category>
		<category><![CDATA[vCO]]></category>
		<category><![CDATA[vCO 5.5.1]]></category>
		<guid isPermaLink="false">http://magander.se/?p=4221</guid>

					<description><![CDATA[An extremely short blog post 🙂 A few days ago i was trying to run a vCenter Orchestrator (vCO) 5.5.1 built in workflow and received the following error: This error tells you that the workflow didn’t pass the validation check before running and that’s why you can’t run the workflow. The workflow would not have &#8230; </p><p><a class="more-link block-button" href="https://magander.se/vcenter-orchestrator-unable-to-run-workflow/">Continue reading &#187;</a>]]></description>
		
		
		
			</item>
		<item>
		<title>vCloud Director internal server error when deploying vApps</title>
		<link>https://magander.se/vcloud-director-internal-server-error-when-deploying-vapps/</link>
					<comments>https://magander.se/vcloud-director-internal-server-error-when-deploying-vapps/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Fri, 05 Apr 2013 13:54:45 +0000</pubDate>
				<category><![CDATA[vCloud Director]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[0000000]]></category>
		<category><![CDATA[100%]]></category>
		<category><![CDATA[5.1]]></category>
		<category><![CDATA[868405]]></category>
		<category><![CDATA[947939]]></category>
		<category><![CDATA[backtrace]]></category>
		<category><![CDATA[buildobbora]]></category>
		<category><![CDATA[Datastore Cluster]]></category>
		<category><![CDATA[distributed resource scheduler]]></category>
		<category><![CDATA[drmRebalanceInt]]></category>
		<category><![CDATA[drs]]></category>
		<category><![CDATA[ERROR]]></category>
		<category><![CDATA[Fully Automated]]></category>
		<category><![CDATA[internal server error]]></category>
		<category><![CDATA[No Automation]]></category>
		<category><![CDATA[opID]]></category>
		<category><![CDATA[rip]]></category>
		<category><![CDATA[rip 0000000]]></category>
		<category><![CDATA[Storage DRS]]></category>
		<category><![CDATA[vCenter Server]]></category>
		<category><![CDATA[vCenter Server 5.1]]></category>
		<category><![CDATA[vCenter Server 5.1.0b]]></category>
		<category><![CDATA[vCloud Director 5.1.1]]></category>
		<category><![CDATA[VMware DRS]]></category>
		<category><![CDATA[vmware-vcloud-director-5.1.1-868405]]></category>
		<category><![CDATA[vmware-vcloud-director-5.1.1-868405.bin]]></category>
		<category><![CDATA[VMware-VIMSetup-all-5.1.0-947939]]></category>
		<category><![CDATA[VMware-VIMSetup-all-5.1.0-947939.iso]]></category>
		<category><![CDATA[vpx]]></category>
		<category><![CDATA[vpxd.exe]]></category>
		<category><![CDATA[vpxd.log]]></category>
		<category><![CDATA[vSphere Datastore Cluster]]></category>
		<category><![CDATA[vSphere DRS]]></category>
		<guid isPermaLink="false">http://magander.se/?p=746</guid>

					<description><![CDATA[During VMware vCloud Director (vCD) vApp deployments using the latest versions of both vSphere (ESXi 5.1 and VMware vCenter Server 5.1.0b 947939) and VMware vCloud Director (5.1.1 868405) i got the below vDC error message: The vCD cell logs located in the /opt/vmware/vcloud-director/logs directory told me e.g. “vCenter Server is unresponsive” These errors made me start investigating &#8230; </p><p><a class="more-link block-button" href="https://magander.se/vcloud-director-internal-server-error-when-deploying-vapps/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/vcloud-director-internal-server-error-when-deploying-vapps/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>VXLAN VIB installation fails</title>
		<link>https://magander.se/vxlan-vib-installation-fails/</link>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Tue, 26 Mar 2013 16:20:48 +0000</pubDate>
				<category><![CDATA[vCloud Director]]></category>
		<category><![CDATA[VXLAN]]></category>
		<category><![CDATA[80/eam/vib?id]]></category>
		<category><![CDATA[An esxupdate error was caught]]></category>
		<category><![CDATA[ERROR]]></category>
		<category><![CDATA[metadata file]]></category>
		<category><![CDATA[MetadataDownloadError]]></category>
		<category><![CDATA[resolve]]></category>
		<category><![CDATA[Unrecognized file vendor-index.xml in Metadata fil]]></category>
		<category><![CDATA[vdn]]></category>
		<category><![CDATA[vendor-index.xml]]></category>
		<category><![CDATA[vib]]></category>
		<category><![CDATA[vibs]]></category>
		<category><![CDATA[vxlan]]></category>
		<category><![CDATA[vxlan vib installation fails]]></category>
		<category><![CDATA[vxlan.zip]]></category>
		<guid isPermaLink="false">http://magander.se/?p=468</guid>

					<description><![CDATA[So today was the fourth time during a very limited time frame the ESXi host VXLAN VIB installation failed when trying to enable the VXLAN functionality. When using the installation procedure for VXLAN documented here i’m not even reaching the part (Figure 6 in the provided link) when the ESXi hosts VMkernel Interfaces (Virtual Adapters/vmk) are created &#8230; </p><p><a class="more-link block-button" href="https://magander.se/vxlan-vib-installation-fails/">Continue reading &#187;</a>]]></description>
		
		
		
			</item>
	</channel>
</rss>

<!--
Object Caching 25/127 objects using Disk
Page Caching using Disk: Enhanced 

Served from: magander.se @ 2026-06-29 01:39:39 by W3 Total Cache
-->