I have an asp.net site with long running report when I try to render this report all the site stops and wait till report rendered.
I'm the only user for the site.
I tried to open the site from different browser to start different session with no result.
I tried to open different pages that not connected to any database with no result.
This site developed with Asp.Net 4.5 and published with IIS 7.5.
I thought that ASP.Net Run every request in isolated thread , so why this happen
Related
I have very strange issue, when when I press the asp.net button click event page is keep loading(in chrome it shows uploading(43%)), after 5-6 minutes shows below
This Application works perfect in development server.(where I have only this application in the IIS) and in Production environment and get this error
This mostly happens with Postback events(uploading files & etc).
I have been searching for a solution for few days nothing success and the most of the articles are said check the DNS/Proxy server and increasing request timeout from web.config
But as I feel this is related to something else.
Is number of SQL database request affecting on this matter?
I am trying to troubleshoot an existing .Net application which I did not code. The application runs on a split config windows server 2016 server(DB is on another server) running .NET version 4.7.2. The application was developed on .Net 4.6.2. There are certain pages in the application which get rerouted to the landing page(a search page) inconsistently. Sometimes it routes to the correct page and sometimes it routes back to the search page. The logs show that the target URL gets generated sometimes and is empty the other times. I am trying to access the same page every time and it is not dynamic. I am confused on how to troubleshoot this. Any inputs are appreciated.
LOGS:
{REST.aspx.cs} ProcessRequest() redirect=False to=>~/Profile/Display.aspx?subject=107310&predicate=345&object=&tab=timeline&file=&viewas=HTML&ContentType=text/html&StatusCode=200&SessionID=5F1CA70C-BCB1-464C-8E90-FFCA5736CEA5 2:18:42 PM
Above is the line logged for accessing a page which opened up the tab successfully.
{REST.aspx.cs} ProcessRequest() redirect=False to=> 2:10:55 PM
Above is the line logged for accessing the same page,a couple of seconds later which routed back to the landing page instead.
I have a 32-bit asp.net application running in IIS 7.5. I am having an issue with the pages.
Mentioned the issue below.
Open a page. Hit the database through some action in the page.
Open another page in another tab. Now, the second page doesn't respond till the first page responds. The second page has no database hits in page load. It's just plain HTML.
This happens with all the pages in the application. I am not sure if it is because of IIS or my application.
Do you have sessions enabled? If yes, all requests will be run serially. If you can, try to avoid using sessions or only enable it where you need it.
I transfer session from asp.net to classic asp.
I use MSSQL DB for it.
I have
SomeWebPage.aspx - this page is asp.net which save sesion, after it, it call by redirect
SessionTransfer.aspx -this page save sessions to DB and call by redirect
SessionTransfer.asp - this page load session from DB and cal by redirect
SomeWebPage.asp - this page doesn't need now about other pages, it just use session.
Problem is, that it works only if SomeWebPage.aspx, SessionTransfer.aspx, SessionTransfer.asp and SomeWebPage.asp are in same folder, or in same "web pages" folder on iis.
How can i do it if SomeWebPage.asp will be in other web folder. On same IIS server, but it will be specific web?
I use IIS 5.1 for developing and finished program will run on IIS 6.0.
Problem was that it was different applications.
SessionTransfer.asp must be it same application like SomeWebPage.asp (it wasn't)
and
SessionTransfer.aspx must be it same application (pool) like SomeWebPage.aspx (it was)
It ws teddy-bear problem. When we start discus about this, i realized where is problem :-D
thanks amit_g
The IIS 6.0 is serving my Classical ASP pages in a serial fashion (one at a time)
The #2 request will be handled by the web server only when the #1 request ends.
If the #1 request takes a little longer, the #2 request will have to wait for the #1 ends to starts being handled by IIS.
Is this a missconfiguration in IIS?
The operation system is Windows Server 2003 Standard Edition (Service Pack 2)
Yes, IIS or the site is most likely configured for server-side debugging, which causes all requests to the site to go through a single thread.
To check if this is the case/turn it off:
In the Properties pages for any Web site or Web virtual directory, click the Home Directory or Virtual Directory tab.
Under Application Settings, click Configuration. An application must be created for the button to be active.
Click the Debugging tab.
Un-check the Enable ASP server-side script debugging check box.
(Above steps were copied from the Debugging ASP Applications in IIS KB article)
Is this happening across machines? Like if you start loading a page on one computer, then another, the second is blocked? I've seen this on a single computer, but only because the browser is limiting connections to the server