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.
Related
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
I have an ASP.NET web application, that given a URL, retrieves a file and redirects the browser to the retrieved file. The file is in a sub-folder under the web app. OK, simple enough. So I deploy my web app to the web server. When I load the URL in the browser, it executes 100% fine, then redirects the browser - only to see this message in Internet Explorer. Interestingly enough, in Chrome, it opens up a Google search page.
So, if I change the code a bit so that it displays the URL that it would redirect to in the web page instead of redirecting it, then I copy/paste that URL into the address bar - voila, the file comes up. But the Response.Redirect doesn't work.
Now, the web application is set up on IIS as an application, the application pool identity happens to be an administrator on that machine. The subdirectory underneath the application has no special permissions/settings on it.
Has anyone seen this before?
I found the problem. The string that was used to redirect to, was actually returned from a TCP socket connection from a helper service, and was not truncated. It was converted from a Byte array, and thus had the full size of the byte array (zero-filled). Once I truncated it, it works fine.
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
Today we tried to put an ASP.NET application I helped to develop on yet another production machine. But this time we got a very weird error.
First of all, from all the ASP.NET pages, only Login.aspx was working. The rest just show a blank screen when they should have redirected to Login.aspx. The HTTP response is 200, but no content.
Even worse - when I try to enter the address of some inexistent ASPX page, I also get HTTP 200! Or, when I enter gibberish in some existing ASPX page code (which should have been accessible without login) I also get HTTP 200.
If I enter the name of some inexistent resource (like asdasd.jpg), I get the expected 404.
The redirect to login page is written manually in Global.asax. That's because the application has to use some alternate methods of authentication as well, so I can't just use Forms Authentication. I would suspect that Global.asax is failing, if not for the working Login page.
Noteworthy facts are also that this machine is both a Domain Controller and has SharePoint installed on it. Although the website in question is listed in SharePoint's exception list.
I would check the following:
Is the application within a virtual application or its own site and not just a virtual directory?
Does the application have it's own App Pool? If it does not then is the app pool shared by apps in a different .net version.
Is the .net version of the application the correct one? 1.1 or 2.0?
Do the files in the file system have the correct permissions to be accessed via IIS?
Have you performed an IIS Reset?
Create a stand alone test.aspx page within your folder that just displays the date/time and check it works.
Make this single test.aspx page perform an exception (eg. divide by zero) and see what the outcome is.
More information required.
What Op Sys?
What mode IIS running under?
What version of .Net?
What version of SharePoint?
(Why are you using your DC as a web host?)
Does it work on the other production machines you've deployed to?
If so what is different between this machine and the working ones?
Did you deploy the same way?
Are you sure your hitting the right machine?
Are you sure your hitting the right web site?
What ISAPI components are installed globally and for the web site?
Is .aspx mapped to the ASP.Net ISAPI filter?
Do you have any HTTP Modules or HTTP Handlers configured?
Can you change the global aspx to write out some messages so you can be sure the piece of code you interested in is reaching?
Anything coming up on the IIS log or the event logs?
Addition:
What version of .Net?
By the sounds of it the .jpg request is being dealt with by IIS directly which is why you get the 404, but the .aspx request is being dealt with by something else which except for you login page, is always returning 200.
Assuming .aspx is wired correctly to .Net the the order of processing is based on ISAPI filters (high to low then global before site), then the ASP.Net ISAPI Extension (sorry I said this was a filter earlier but it's actually an extension). Then we get into the ASP.Net pipeline based on your .Net configs, and calls the HTTP Application (which includes your global.asax code), any HTTP Modules followed finally by a HTTP Handler. Your ASP.Net web forms are just fancy HTTP Handlers.
However, the request can be responded to and terminated from any point.
Since your code works on other machines though, I'm tempted to point a finger at SharePoint if it isn't installed on the working machines. Is this SharePoint 2007? That is also an ASP.Net application (I don't think 2003 was).
We have an old system running on a WinServer2003 R2 - IIS6 and it was written using classic ASP.
We need to trap all errors and for that, I configured IIS to redirect 404s and 500s to a custom page (custom errors config) that writes the info to a log file (this page creates and manages the logs).
Here is the weird thing: The first time the error occurs, the page is redirected and I get my log file entry. But, if this page is loaded again (I hit F5, or other user goes there, etc), the browser receives a blank page: no error message and my custom page is ever called.
If I restart IIS6 I get the same behavior, first time it works, next not.
-> Send ASP errors to browser is turned on
-> Show friendly http errors is turned off in my explorer
Any thoughts?
You need to ensure Server Side Debugging is not enabled in the ASP module.
Classic ASP server 500 errors are returned as 200's. An attempt is made at opening the Server Side Debug Application, that then can't be found and IIS subsequently returns a 200 response.
Try doing this while running Fiddler ( http://www.fiddlertool.com/Fiddler2/version.asp ) or some other tool that makes it possible to see what's being sent here and there.
Also; if you set IIS to log in the IIS log format, errors will show up in the log file at the very end of the line for the request that ended in error.
maybe its this issue
http://www.webdevbros.net/2006/11/26/ie7-bug-blank-page-white-screen-after-some-refreshs/