-
Posted to
IIS7 - General
by
optiontrader1138
on
07-07-2009, 4:06 PM
Hi Carlos,
I wanted to know that thanks to you, we were able to fix the problem! It turns out that it wasn't the RadGrid control at all. Rather, it was the inclusion of a code snippet embedded in the .aspx page:
<% = BlogLink() %>
This snippet went out and read the first article on our blog. The new server was unable to see the ...
-
Posted to
IIS7 - General
by
optiontrader1138
on
07-07-2009, 10:33 AM
And one more clue... The boxes we're having problems with are both Windows Server 2008. It's running fine on Vista/IIS7 (developers box) however.
-
Posted to
IIS7 - General
by
optiontrader1138
on
07-07-2009, 10:27 AM
Hi Carlos,
First, your code works like a charm. We are installing on our production server today to get exacttimings in that environment.
We installed the application on a brand new install of Windows Server 2008 / IIS 7 last night. We are experiencing the same problem there, so that rules out a bad install. It must be some conflict between ...
-
Posted to
IIS7 - General
by
optiontrader1138
on
07-06-2009, 8:54 PM
This is awesome - I spent all day trying to figure out how to do this and finally resorted to isolating controls one at a time. I will try this tomorrow to be sure, but it appears that we isolated it to a specific third-party control.
The problem, however, is that the control runs just fine in IIS7 on a different server (as well as IIS6 and ...
-
Posted to
IIS7 - General
by
optiontrader1138
on
07-06-2009, 3:06 PM
I've definitively traced it down to the page_render logic. We are using third-party controls and I have a sneaking suspicion that the configuration is wrong for them on the webserver (other pages on the server without custom controls render quickly, and the pages with the custom controls render instantly on local/dev boxes.)
This is a ...
-
Posted to
IIS7 - General
by
optiontrader1138
on
07-05-2009, 8:55 PM
Ok, I spent a few minutes tracing through various pages and I tried altering the failed trace settings to capture all requests with status 100-400. Previously, I was capturing pages with > 10 second load time. For some reason, this appeared to throw off the timing, but removing it gives me reports that are closer to actual results.
The log ...
-
Posted to
IIS7 - General
by
optiontrader1138
on
07-05-2009, 8:28 PM
Hi Carlos,
Thanks, that is helpful. Based on what I am seeing, I am now a bit more confused as I'm getting different timings based on what I'm looking at.
The trace methods I've placed inside of page_load indicate that the page loaded in 18 seconds.
The failed request file indicates that the page loaded in 15.023 ...
-
Posted to
IIS7 - General
by
optiontrader1138
on
07-04-2009, 1:12 PM
Hi everyone,
Thanks to the helpful resources at this site I was able to resolve the first of two critical issues we're facing after upgrading our website to IIS 7 / Windows Server Enterprise 2008.
Unfortunately we've made no progress on the second. Our aspx pages are running incredibly slow now that we're on IIS 7 (they were pretty ...
-
Posted to
IIS7 - Setup
by
optiontrader1138
on
07-04-2009, 12:16 PM
Ok, we solved the problem.
It turns out the developer still had a reference to the ISAPI handler for PHP in their web.config. This overrode the global server settings.
-
Posted to
IIS7 - Setup
by
optiontrader1138
on
07-04-2009, 1:02 AM
Hi everyone,
We've been working for three days on trying to fix some issues related to our recent migration to IIS 7. This one has got us stumped.
Our site is using both PHP and ASPX pages. We've installed FastCGI to serve our PHP pages, but it appears that php5isapi is still being used. We suspect this because we are getting errors such ...