Everyone knows you always find the answer right after you ask. I can't believe it took you so long to ask. ;)
On Thu, Nov 15, 2012 at 9:47 AM, Iain Carlin <[email protected]> wrote: > Well, as per usual, after weeks of searching, 15 minutes after posting to > ozDotNet I stumble across the answer: > > > http://stackoverflow.com/questions/6948669/iis-7-not-serving-default-document > > > > > On 15 November 2012 11:55, Iain Carlin <[email protected]> wrote: > >> Hi Stehen, thanks for the suggestion, but they are not two different >> pages, that's the problem. >> >> For http://mysite the default document is set to index.asp. It should >> act exactly the same hitting http://mysite or http://mysite/index.aspbut the >> first site gives an error. >> >> >> On 15 November 2012 11:29, Stephen Price <[email protected]>wrote: >> >>> Perhaps look at whats being loaded to see the difference. Try pressing >>> F12 in IE for developer tools, click Network and start capturing button. >>> Load the two pages and see if anything differs majorly between the two >>> pages? >>> Should show you any 404s. >>> Alternatively try the same with Fiddler? >>> >>> >>> On Thu, Nov 15, 2012 at 8:41 AM, Iain Carlin <[email protected]> wrote: >>> >>>> I have an issue with a third-party tool that is deployed as a web site >>>> on our IIS 7 server. >>>> >>>> The site is set up to run under an application pool configured for .Net >>>> 4.0 in classic mode. >>>> >>>> The start page for the site is a classic asp page (not sure why, not my >>>> site). If I browse to the page directly, (http://mysite/index.asp), >>>> everything loads and runs fine. >>>> >>>> index.asp is configured as the default document for the site. However >>>> when I browse to http://mysite the asp page loads but all the .Net >>>> bits are in various states of brokenness. >>>> >>>> There are errors in the Windows application log that indicate two >>>> different frameworks are being loaded - but everything on this site is >>>> using the single .Net 4.0 application pool. >>>> >>>> What is different about loading using the default document vs browsing >>>> to the file directly? >>>> >>>> I wonder if perhaps there is a clash between 64 and 32 bit versions of >>>> 4.0 somehow. >>>> >>>> The vendor is blaming our server, but there are 6 other sites on it, >>>> also using various combinations of asp and .Net (both V2.0 and 4.0 (64 and >>>> 32)) and none of those are having any issues. >>>> >>>> This has caused me weeks of frustration so any assistance would be >>>> appreciated. >>>> >>>> >>>> >>> >> >
