<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Understand the Windows Installer Logs</title>
	<atom:link href="http://www.msigeek.com/257/interpreting-windows-installer-logs/feed" rel="self" type="application/rss+xml" />
	<link>http://www.msigeek.com/257/interpreting-windows-installer-logs</link>
	<description>Microsoft Guides, Windows Blog and Tech Tips</description>
	<lastBuildDate>Tue, 07 Feb 2012 16:43:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: How to troubleshoot the error 1603 "Fatal Error During Installation"?</title>
		<link>http://www.msigeek.com/257/interpreting-windows-installer-logs/comment-page-1#comment-532</link>
		<dc:creator>How to troubleshoot the error 1603 "Fatal Error During Installation"?</dc:creator>
		<pubDate>Sun, 04 Oct 2009 07:13:36 +0000</pubDate>
		<guid isPermaLink="false">http://174.36.239.128/~msigeek/interpreting-windows-installer-logs/#comment-532</guid>
		<description>[...] One can find that the biggest hurdle to debugging a failed setup is often zeroing in on which part of the setup is actually failing, and this trick of searching for &#8220;return value 3&#8243; ends up helping speed this process up in nearly all cases. Of course, it does not work in 100% of scenarios. You can find some ways of troubleshooting the logs here -  http://www.msigeek.com/identifying-installation-failure-through-cas-using-msi-logs/ http://www.msigeek.com/interpreting-windows-installer-logs/ [...]</description>
		<content:encoded><![CDATA[<p>[...] One can find that the biggest hurdle to debugging a failed setup is often zeroing in on which part of the setup is actually failing, and this trick of searching for &#8220;return value 3&#8243; ends up helping speed this process up in nearly all cases. Of course, it does not work in 100% of scenarios. You can find some ways of troubleshooting the logs here -  <a href="http://www.msigeek.com/identifying-installation-failure-through-cas-using-msi-logs/" rel="nofollow">http://www.msigeek.com/identifying-installation-failure-through-cas-using-msi-logs/</a> <a href="http://www.msigeek.com/interpreting-windows-installer-logs/" rel="nofollow">http://www.msigeek.com/interpreting-windows-installer-logs/</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

