How to resolve Http 400 bad request Error in IIS 7? - asp.net

We have migrated the our websites from one server to another server. all completed successfully but one website has issue of HTTP 400 bad request. I have googled alot but none of the solution works for me then I found this article which told me to set the website under the default website in. when i do that it works for me. but i want to make the previous one working. so please help me how can i do this and please let me know why it is working under default websites.
UPDATE: i have also enabled the log for tracing the error but its not creating a single log.
Thanks in advance.

Related

Azure Web App Http Error 500

https://bucherid.azurewebsites.net/
the website can't be accessed normally and ended up with http error 500
But, when i logged in to
bucherid.azurewebsites.n*t/wp-login/
finally i can see the website content normally.
previously the site can be accessed normally and then from yesterday I don't know why but this http 500 happened.
are there solution for this?
from the failed requests traces, this is what appear
image
there's also error messages like this
"There is not enough space on the disk."
Based on the information you have provided, it can not tell what has caused this issue yet. I suggest you enable the Detailed error message functionality through the Azure portal. the screenshot below is to show where to turn on that.
After that done, you should have log files under the directory d:/home/LogFiles/DetailedErrors in your Azure server. You can refer to the link to know how to download them. These files will provide more specific details for the HTTP errors.
Additionally, you can also enable PHP run-time error log by changing the built-in PHP configurations. For more info, please refer to How to debug PHP in MS Azure.
Depending on your SKU, there are limitations in how much disk space you get. See the App Service Pricing page for details.

Http 403 on new IIS deployment

Having just asked this question : ASP.NET Web Project deployed to IIS Express not accessible outside localhost I figured I would just go ahead and install IIS. I did this - and setup a new deployment of my site.
However when you try visiting it : http://andyworker.hopto.org:8080/ you will notice a http 403 error. Googling around I see this post http://sanuja.com/blog/resolving-iis-403-forbidden-access-is-denied which suggests adding a user and giving it read write execute for IIS however that bit where I add the user fails - as I don't think the user exists?
Can anybody help me here? I am very new to IIS having never deployed something before and having just installed it - but something simple here feels quite unintuitive.
Andy

Creating a customised 503 page in IIS 7

This is my first question :)
Is there any way to create a cutomised 503 error page in IIS7. Form what I have read, this error page is served up internally by http.sys and cannot be overriden. This is confirmed at the top of this page.
However, I have seen Questions on Stackoverflow where this is apparently possible, but I have had no luck trying to implement it. Could anyone give me a definitive answer?
Thanks in advance.
Sadly, the TechNet article is accurate - there is no way to replace 503 for the scenario you describe.
The error is detected by the IIS server as it attempts to hand the incoming request to your application. Everything your application does is performed in its app pool. Modules like rewrite rules and custom HTTP responses are all executed in this way.
If your application has no app pool to run in, it unavailable to do any custom processing: there is essentially no code running for your application.

Hybrid ASP.NET/MVC application on IIS 7.5 .aspx pages not loading

I have a hybrid ASP.NET/MVC 2 application that is currently hosted on II6.
I need to migrate this to IIS 7.5 and I'm having trouble getting it to work.
The furthest I've got is when the app pool is in integration mode, I migrated the web.congig using AppCmd.exe but only the MVC part worked and the .aspx pages wouldn't load.
I suspect that this is due to a custom handler that somone wrote called StaticFileHandler.
I know that this code is being hit as I see it in the log file.
And also checking the IISLogs I can see that the request returns a 200 http code
I've search around for answers but the only one I found that came close was someone who had their .aspx pages working and not their MVC part.
Has anyone got an idea what I can try?
I've been looking into this for days and havn't come up anything.
Thanks in advance.
I figured this out.
The issue was due to modules in the website.
These were doing things like compression and such, once taken them out, and removing them from the web.config, I got it working rather easily.

HTTP Error 503 - But only when using domain name to navigate

I am currently having a strange issue that has taken me by surprise, I have not had the issue before and I have no idea why I am getting it now.
I have an asp.net mvc 3 website which has a number of controllers all with actions. It is important to note that this issue is only present with one controller and the problem is with all Actions.
The error I am getting is "HTTP Error 503. The service is unavailable."
However, this error only occurs if I browse to the page using the domain name, for example...
subdomain.example.com/controller
but everything works fine if I browse with the ip address and port number...
xxx.xxx.xxx.xxx:xxxxx/controller
remember all other controllers work fine regardless of the method used to browse.
I have tried looking for answers to this and trying to find any useful logging information but have found nothing of use. Hopefully somebody here will have seen this issue before
Ok I have created a sample mvc project with a Reports controller that works so I don't believe it is a problem with MVC.
I'd reccomend looking at your routes and your web.config and make sure you don't have anything intercepting it there into an httphandler or module. Then I'd look at the IIS instance and check for virtual directories. You pretty much are trying to figure out where exactly it is failing - is it even reaching ASP.Net?
One last option to look into is your company proxy - does going to the URL directly go through the proxy? I know at my company this can happen - so there may be a rule there that is intercepting it.

Resources