<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://forums.iis.net/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/" xmlns:cs="http://blogs.iis.net/"><channel><title>Search results matching tag 'Atlas'</title><link>http://forums.iis.net/search/SearchResults.aspx?o=DateDescending&amp;tag=Atlas&amp;orTags=0</link><description>Search results matching tag 'Atlas'</description><dc:language>en-US</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>Atlas on IIS 7 does not work in Integrated mode</title><link>http://forums.iis.net/p/1158010/1905231.aspx#1905231</link><pubDate>Sat, 30 May 2009 08:31:42 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:1905231</guid><dc:creator>Stephenos_r</dc:creator><cs:applicationKey>iis_7_-_aspnet_administration-41</cs:applicationKey><description>&lt;p&gt;I deployed a large&amp;nbsp;ASP.net application on IIS 7 ported from IIS 6. &lt;/p&gt;
&lt;p&gt;There are certain parts of the application, unfortunately,&amp;nbsp;that have Atlas not converted to Ajax but work on .Net framework 2.0 running on IIS 6.0. The application works just fine.&lt;/p&gt;
&lt;p&gt;On IIS 7, the parts that still have Atlas implementation throw an JavaScript error as &amp;quot;Unknown Error&amp;quot;. The rest of the application where Ajax is implemented works.&lt;/p&gt;
&lt;p&gt;I changed the AppPool from DefaultAppPool to Classic .NET AppPool and the error goes away. &lt;/p&gt;
&lt;p&gt;Does anyone have insights into the working of Atlas on IIS 7 and why it fails. I am not able to fit any of the IIS 7 breaking changes list to this problem.&lt;/p&gt;</description></item><item><title>Re: Broke in Vista RC-1 - Atlas Toolkit using Integrated Mode</title><link>http://forums.iis.net/p/1031168/1418303.aspx#1418303</link><pubDate>Wed, 04 Oct 2006 16:24:37 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:1418303</guid><dc:creator>mvolo</dc:creator><cs:applicationKey>iis7_-_known_issues_and_workarounds--1</cs:applicationKey><description>This is due to a non-essential piece of Atlas having an issue with the new ASP.NET Integration mode.&amp;nbsp; This is fixed in a subsequent release by removing the module from the Atlas web.config file (you probably got it when you migrated the Atlas configuration, bringing this module over from the httpModules section):&lt;br /&gt;&lt;br /&gt;&amp;lt;modules&amp;gt;&lt;br /&gt;&lt;strike&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;add name=&amp;quot;...&amp;quot; type=&amp;quot;Microsoft.Web.Services.WebResourceCompressionModule&amp;quot; /&amp;gt;&lt;/strike&gt;&lt;br /&gt;&amp;lt;/modules&amp;gt;&lt;br /&gt;&lt;br /&gt;This will provide a workaround for this build of Atlas.&amp;nbsp; In the LH Server timeframe, the IIS team will provide a better option for dynamically compressing Atlas resources using the native IIS dynamic compression feature.&lt;br /&gt;&lt;br /&gt;Thanks,&lt;br /&gt;</description></item></channel></rss>