Previous Next

• 09-08-2008, 11:37 AM

  John Happy Joined on 11-03-2006, 3:19 AM Posts 9

  ASPX pages run only on Classic pipeline not Integrated pipeline Reply Contact Recently upgraded my web server from Windows Server 2003 to Windows Server 2008 and discovered that most of my aspx pages were broken. The only way, thusfar, I've found to fix the problem is to either set up a website in the Classic .NET AppPool or set up the website in its own App Pool and make sure the Managed Pipeline Mode is set to Classic. I have not discovered how to get an aspx page to work in integrated mode. I just get a HTTP error 404, File not found.

  Tags: aspxintegrated modeclassic mode

• 09-08-2008, 11:47 AM

  In reply to

  Rovastar Joined on 03-13-2008, 10:00 AM London, UK Posts 758	Re: ASPX pages run only on Classic pipeline not Integrated pipeline Reply Contact  Info on what integrated mode is  http://www.iis.net/default.aspx?i=928&subtabid=25&tabid=2 http://msdn.microsoft.com/en-us/magazine/cc135973.aspx http://learn.iis.net/page.aspx/381/aspnet-20-breaking-changes-on-iis-70/   Most overused word in IT is 'should' as in 'That should work!?!'

• 09-08-2008, 2:40 PM

  In reply to

  John Happy Joined on 11-03-2006, 3:19 AM Posts 9

  Re: ASPX pages run only on Classic pipeline not Integrated pipeline Reply Contact I had found the article called 'ASP.NET 2.0 Breaking Changes on IIS 7.0' which described using an executable named APPCMD to help migrate ASP.NET 2.0 apps to IIS 7.0. I'm trying to follow some of the instructions in the article but nothing I've done so far has helped. Host headers distinguish one website from another on my web server. All my web server folders are in the root of the InetPub folder. They are virtual servers, at least that's what they used to be called..  I just tried creating a brand new web site on my web server. I did so using the DefaultAppPool and Framework v2. I was hoping that if I started from scratch, so to speak, that the Integrated pipeline would work out of the box. I used VS 2005 to create a new ASP.Net 2.0 web site within the website just created in IIS 7.0 but still no luck. I created a simple aspx page with just some text on it and could not browse to it. I get a 404 error message. I don't have any problem browsing to that aspx page if I change the App Pool to Classic .NET AppPool. I do not normally create a sub-directory within my website folder and convert it into an application. I usually want the root of the website to be an application and I might create a folder within the website that becomes its own application. Perhaps this practice caused some trouble for me during my upgrade from Windows Server 2003 to Windows Server 2008 and IIS6.0 to IIS7.0.

• 09-08-2008, 2:47 PM

  In reply to

  anilr Joined on 05-23-2006, 6:13 PM Redmond, WA Posts 1,225

  Re: ASPX pages run only on Classic pipeline not Integrated pipeline Reply Contact Upgrading from earlier versions to IIS7 causes all configuration to be updated to only support classic mode - since that is the mode from before upgrade - getting to integrated mode from an upgraded box will be a non-trivial task, if you want to use integrated mode, I would suggest doing a clean install of IIS (you can uninstall IIS and windows process activation service and reinstall IIS to get a clean install) and using something like msdeploy to migrate stuff to IIS7. Anil Ruia Senior Software Design Engineer IIS Core Server

• 09-08-2008, 3:40 PM

  In reply to

  John Happy Joined on 11-03-2006, 3:19 AM Posts 9

  Re: ASPX pages run only on Classic pipeline not Integrated pipeline Reply Contact My goal is to be able to choose between classic and integrated - and to continue to use FrontPage Extensions via SharePoint - to basically have everything I had when I ran my sites under IIS6 and whatever new stuff IIS 7 offered. Apparantly, the place to uninstall IIS, is the Server Manager. I see that the Web Server (IIS) role can be removed and that the Windows Process Activation Service (listed under Features Summary) can be removed. Should I remove the Windows Process Activation Service first and then the Web Server (IIS) role following that? Will removing the Web Server role automatically remove the Windows Process Activation Service?  Will reinstalling the Web Server role (IIS) automatically give me the Windows Process Activation Service feature? I Googled MSDeploy and found the Deployment Team blog. What's the best resource for me to use to help me through the deployment process using MSDeploy?

• 09-10-2008, 11:37 AM

  In reply to

  John Happy Joined on 11-03-2006, 3:19 AM Posts 9	Re: ASPX pages run only on Classic pipeline not Integrated pipeline Reply Contact Answers to my questions, above, appear to be addressed on the following web page:  http://technet.microsoft.com/en-us/mscomops/cc424869.aspx