Paul
Sun Nov 07 10:04:18 CST 2004
Yes, the problem has appeared to gone away! Server has not been rebooted
or IIS restarted since my last post.... Hmmm, I wonder if it is something
weird with the old fpexedll.dll or Web Trends Cookies in the Master WWW
properties. I checked the fpexedll.dll file version - it is 4.0.2.7523 -
looks like that might be very old, circa 1999 according to the MS copyright
date on the dll.
The Web Trends Cookie dll is fairly old too, version 3.1.0.0, circa 2001.
This is part of WebTrends Professional Suite 5.5c
-- Paul
"Kristofer Gafvert" <kgafvert@NEWSilopia.com> wrote in message
news:OmsGES3wEHA.2568@TK2MSFTNGP11.phx.gbl...
> Hello,
>
> I can reproduce this when using Internet Explorer, but i cannot reproduce
> when using wfetch (from IIS Resource Kit). That is, i see your problem if
> i
> access the page using Internet Explorer, but the page is working correctly
> when using wfetch.
>
> So, it seems to be something that is checking what browser (or something
> else) i am using, and causing this problem. It looks however like it went
> away now (i cannot see it anymore in my browser), is this correct?
>
> --
> Regards,
> Kristofer Gafvert
>
http://www.ilopia.com
>
>
> "Paul" <paule@nospam-mindspring.com> wrote in message
> news:uk1RCC2wEHA.3376@TK2MSFTNGP12.phx.gbl...
>> - Filters installed on the Master WWW web are "fpexedll.dll" and
> "WebTrends
>> Cookies" (we do not use FrontPage, must be a leftover from some other
>> application)
>>
>> - Yes, this only occurs on HTML pages (as far as I can tell)
>>
>> - Footers are not enabled on the Master WWW site or the problem website
>>
>> - There is no script mapping for .html on the Master WWW site or the
> problem
>> website. Problem website only has an .asp script mapping (even though
>> ASP
>> is not used on that particular website)
>>
>> - We use IIS compression. After the Windows 2003 upgrade last weekend,
> it
>> moved the "IIS Temporary Compressed Files" folder from my previously
>> assigned "d:\IIS Temporary Compressed Files" drive to "c:\winnt\IIS
>> Temporary Compressed Files"
>>
>>
>> Here is a sample problem page (in this case pulling from another page on
> the
>> same website):
>>
http://ww2.tmiexpos.com/cme_tracking.html
>>
>> The bottom text is being taken from this page:
>>
http://ww2.tmiexpos.com/expotogo.html
>>
>> I have copied the html files to txt files so you can view the raw source:
>>
http://ww2.tmiexpos.com/cme_tracking.txt
>>
http://ww2.tmiexpos.com/expotogo.txt
>>
>>
>> Just now at the command prompt, I simply copied cme_tracking.html to
>> cme_tracking_resaved.html and the page displays correctly! See:
>>
http://ww2.tmiexpos.com/cme_tracking_resaved.html
>>
>>
>> Very odd....
>>
>> -- Paul
>>
>>
>>
>>
>>
>> "Kristofer Gafvert" <kgafvert@NEWSilopia.com> wrote in message
>> news:eI9RUUxwEHA.3612@tk2msftngp13.phx.gbl...
>> > Hello,
>> >
>> > Are you using any ISAPI filters, reverse proxy software, or other
>> > things
>> > that can cause this? As Bernard, I have never seen this in IIS, and the
>> > only
>> > thing i can think of is that something else causes this.
>> >
>> > --
>> > Regards,
>> > Kristofer Gafvert
>> >
http://www.ilopia.com
>> >
>> >
>> > "Paul" <paule@nospam-mindspring.com> wrote in message
>> > news:%23OWoJzqwEHA.3376@TK2MSFTNGP12.phx.gbl...
>> >> We just upgraded from Windows 2000 Server to 2003 Server last weekend.
>> > Now
>> >> I have a bizarre problem with a site containing strictly static HTML
> page
>> >> content. At the bottoms of some pages, I get what looks like the
>> >> tail
>> > end
>> >> of pages of other websites hosted on the same server. When I scroll
> to
>> > the
>> >> bottoms of the pages I will see text from a completely different
> website
>> >> that is being hosted on the same server. That other website's
>> >> content
>> >> is
>> > a
>> >> static HTML page as well.
>> >>
>> >> It's sort of like a strange "buffer overflow" situation -- but
>> >> IISRESET
>> >> doesn't help and the *same* other website content appears on the
>> >> *same*
>> >> pages in this site, so it doesn't seem to be a random
>> >> whatever's-in-the-buffer-gets-displayed type of thing...
>> >>
>> >> If I simply go in and edit the "broken" .html page and enter a blank
> line
>> > or
>> >> anything to effect a change to the file, and resave the page, the
> problem
>> >> goes away!
>> >>
>> >>
>> >> -- Paul
>> >>
>> >>
>> >
>> >
>>
>>
>
>