<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>IIS7: Sharepoint 2007 fails with 503 Service unavailable errors</title><link>http://blogs.msdn.com/jmacleod/archive/2008/06/25/iis7-sharepoint-2007-fails-with-503-service-unavailable-errors.aspx</link><description>Recently I have seen a few of these cases come in so I thought I would share what I know at this time. Technologies involved ===================== - Windows Server 2008 64 bit - SharePoint 2007 (64 bit) configured as a dedicated indexing Server Issue</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Pregnant Man &amp;raquo; IIS7: Sharepoint 2007 fails with 503 Service unavailable errors</title><link>http://blogs.msdn.com/jmacleod/archive/2008/06/25/iis7-sharepoint-2007-fails-with-503-service-unavailable-errors.aspx#8652371</link><pubDate>Wed, 25 Jun 2008 18:30:59 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8652371</guid><dc:creator>Pregnant Man &amp;raquo; IIS7: Sharepoint 2007 fails with 503 Service unavailable errors</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://wordnew.acne-reveiw.info/?p=3361"&gt;http://wordnew.acne-reveiw.info/?p=3361&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: IIS7: Sharepoint 2007 fails with 503 Service unavailable errors</title><link>http://blogs.msdn.com/jmacleod/archive/2008/06/25/iis7-sharepoint-2007-fails-with-503-service-unavailable-errors.aspx#9370518</link><pubDate>Thu, 22 Jan 2009 23:30:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9370518</guid><dc:creator>JoeFrazier4th</dc:creator><description>&lt;p&gt;THANK YOU SOOOOO MUCH. &amp;nbsp;THIS POST FIXED MY PROBLEM!!!!!!!&lt;/p&gt;
&lt;p&gt;i was getting the error &lt;/p&gt;
&lt;p&gt;LoadBalancer.UnRegisterLauncher failed: &amp;nbsp;The remote name could not be resolved: &amp;quot;COMPUTERNAME&amp;quot;&lt;/p&gt;
&lt;p&gt;and none of my sharepoint webapps would stay started.&lt;/p&gt;
&lt;p&gt;i would get Service unavailable when i tried to open any sharepoint page.&lt;/p&gt;
&lt;p&gt;TOTALLY AWESOME &lt;/p&gt;
&lt;p&gt;thank you!!!!&lt;/p&gt;
</description></item><item><title>re: IIS7: Sharepoint 2007 fails with 503 Service unavailable errors</title><link>http://blogs.msdn.com/jmacleod/archive/2008/06/25/iis7-sharepoint-2007-fails-with-503-service-unavailable-errors.aspx#9603233</link><pubDate>Mon, 11 May 2009 18:35:55 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9603233</guid><dc:creator>Jennifer Neumann</dc:creator><description>&lt;p&gt;Jeff, &lt;/p&gt;
&lt;p&gt;thanks a lot for posting this! I would have never guessed that the app pool crashes were happening because we had recently changed the setting from &amp;quot;use all WFE for crawling&amp;quot; to a dedicated server.&lt;/p&gt;
&lt;p&gt;Quick note: your Workaround #1 does not work, as the central admin web app is unavailable as well. For Workaround #2: even though we had IP6 active, the hosts file entry we had was IP4...&lt;/p&gt;
&lt;p&gt;192.168.1.3	sp	# Added by Office SharePoint Server Search (5/11/2009 5:14 PM).&lt;/p&gt;
&lt;p&gt;Deleting that line, then disabling IP6 (just to be safe), and then restarting the &amp;quot;Stopped&amp;quot; app pools was all that was neccessary to get everything working again.&lt;/p&gt;
&lt;p&gt;What I found odd btw is that also our non-SharePoint app pools had crashed because of that hosts file entry.&lt;/p&gt;
&lt;p&gt;Thanks again for your helpful info!&lt;/p&gt;
&lt;p&gt;Jennifer&lt;/p&gt;
</description></item><item><title>MOSS 2007 on Win 2008 Allergic to IPv6</title><link>http://blogs.msdn.com/jmacleod/archive/2008/06/25/iis7-sharepoint-2007-fails-with-503-service-unavailable-errors.aspx#9642311</link><pubDate>Wed, 27 May 2009 00:37:33 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9642311</guid><dc:creator>Michael Blumenthal Blog  </dc:creator><description>&lt;p&gt;Body: My friend Ralph today ran into the issue described here: &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/jmacleod/archive"&gt;http://blogs.msdn.com/jmacleod/archive&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: IIS7: Sharepoint 2007 fails with 503 Service unavailable errors</title><link>http://blogs.msdn.com/jmacleod/archive/2008/06/25/iis7-sharepoint-2007-fails-with-503-service-unavailable-errors.aspx#9810281</link><pubDate>Wed, 01 Jul 2009 06:02:20 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9810281</guid><dc:creator>joelji</dc:creator><description>&lt;p&gt;Thanks a lot Jeff.&lt;/p&gt;
&lt;p&gt;For me the scenario was same: MOSS 2007 x64 with SP2 in a Windows server 2008 x64 with IIS7. Central Admin was working fine but SSP admin site/new webApp created was throwing error '503 Service Unavailable'. I found that the WebApp for SSP for stopped. Even when i tried to start it from IIS manually it failed. &lt;/p&gt;
&lt;p&gt;I tried the first workaround:&lt;/p&gt;
&lt;p&gt;&amp;quot;Use all web front end for crawling&amp;quot; and recycled the App pool in IIS which solved the issue.&lt;/p&gt;
</description></item><item><title>re: IIS7: Sharepoint 2007 fails with 503 Service unavailable errors</title><link>http://blogs.msdn.com/jmacleod/archive/2008/06/25/iis7-sharepoint-2007-fails-with-503-service-unavailable-errors.aspx#9925087</link><pubDate>Thu, 19 Nov 2009 04:54:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9925087</guid><dc:creator>ravindarg</dc:creator><description>&lt;p&gt;Can someone please post exact STSADM command to change crawl service to use WFE(web front end) servers from dedicated server option. I am having same issue and Central admin is not working. Thanks&lt;/p&gt;
</description></item></channel></rss>