As the subject says I had a perfectly good CRM 2013 install on 2012 and it was being used. Sometime overnight the site went down. Now I get a 404.0 error. I've disbaled friendly errors...just get a blank page not even a 404. I've modified the web.config debug=true nothing. Fiddler shows nothing...well not exactly. Fiddler shows a 404 as well.
I've removed ssl cert and reapplied. Tried accessing the site http nada?? I looked for any updates that were pushed overnight nothing..(they are disabled but I checked anyway).
If I browse to http it redirects me https as it should. It prompts for my NT credentials as it should. Downloads favicon and decides it has done all it's going to do.
So I am at a real loss as to even getting a clue as to the problem. If someone can help me with some further troubleshooting direction it would be appreciated.
Thank You
Related
i wrote a ASPX Webapplication and generally it works great. BUT since a few days i figured out one big annoying problem with the IIS 8.5!
You can log in and browse through all sites and subsites without any problem. But after a time (about 6 mins) or when i click on the CheckBoxList on the mainsite "Report" - here CheckBoxList Click - i get the Error:
"403 Forbidden - you don't have the permission to access the
/Report.aspx"
On the IIS i've tested so many security configurations and nothing worked fine. The Funny thing is - sometimes i have no problem with the Webapp for 1-2 weeks and than it started all again with the 403 Forbidden Error. Meanwhile i haven't changed anything.
Application Pool is everything fine. Folder permissions and Website permissions with the IIS_USR is configured with full access. Timeout is set on 30 mins.
I'm sorry i can't give you a link to test what i wrote because of company internal security.
Do you need any other Infos? Code elements? Settings from the IIS? Screenshots?
Hope you know what i'm looking for and thank you for any help!
I still didn't find the problem so i put the whole Website on a different Server and it works perfectly over there.
At the end i think it was/is a problem with the https certificate! So i changed the system from winserver 2012 and IIS 8.5 to winserver 2008 r2 with IIS 7 (if they cue in the same cert and we have the prob again i'll know it for sure).
I hope i have the chance to figure out what the problem on the old server was!
Thanks for every answer!
Have an issue where I get a 404 errors on multiple pages that definitely exist on the server.
It is an ASP based website and at completely random points I get a 404 error for those pages that definitely exist on the server as after I do a refresh it's absolutely fine.
Weird thing is that when I open developer tools I never receive the error anymore.
Any chance that developers tools is actually interfering with the connection between browser and server and actually changes something?
Why I'm not getting the error while developer tools is running?
Has anybody got anything similar to this before?
I am using Internet Explorer 11 as well as tried Internet Explorer 10.
Same on both browsers.
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.
I have an issue here which has me baffled.
Another developer and myself developed an ASP.Net Web Forms application four years ago and the site has been live since. About 6 months ago we moved the application from a Windows 2003 web server using IIS 6, to a Windows 2008 web server using IIS 7.5. When we moved servers we tested the application again in the Firefox web browser, however, I can't remember if we also tested in Internet Explorer. We should have done.
Recently it has been brought to our attention that in Internet Explorer, when a user attempts to hit some of the pages within the website, they are presented with a
Forbidden URL
HTTP Error 403. The request URL is forbidden
I have also tried to recreate this error on my local computer and I also get an error
HTTP Error 400 - Bad Request
This only happens when using an Internet Explorer web browser, it works fine with the likes of Chrome, Firefox etc.
I am not sure how to fix this, but because myself and the other developer have not changed any of the source code, I don't think this is where the problem lies. I have a feeling it might have something to do with IIS on our new web server, but I am really not sure.
Has anyone else seen this problem before?
Any feedback would be greatly appreciated.
Thanks.
Folks, the problem for some reason was as follows:
When a user clicked a button on my site which would then redirect them to another page within the site, I previously had the following code to do so
Response.Redirect("../userprofile/myprofile.aspx")
However, after the release of IE 10, this redirect would no longer work, and instead I had to replace it with
Response.Redirect("~/userprofile/myprofile.aspx")
Hope this helps someone else who is having similar problems.
Have recently migrated a number of websites from an ageing Windows 2003 server running IIS6 to a new Windows 2008 server running IIS7.
The sites all use a CMS written in classic ASP which requires that the 404 error is modified to load a default.asp file which looks at the URL and loads content from a database. This is just to keep all the URLs nice and SEO friendly.
The back office of the CMS works in a similar way (except the 404 error is dealt with by admin/default.asp).
For some reason though, the login page (which obviously involves a form posting to the custom 404 error) does not carry over the POST information.
OK - here's the weird bit. It works fine in Google Chrome, but not in IE7/8 or Firefox.
Obviously this is right royal pain in the harris.
Any ideas why post data is carried through the custom 404 handler for one browser but not any others?
I've got as far as I can and am currently trawling the web for information about this but can't seem to find anything...
OK - here's an update for the weird bit.
It works fine in Safari as well as Google Chrome - but not in IE7/8 or Firefox.
???
I'm not sure this helps, but check this question Posting forms to a 404 + HttpHandler in IIS7: why has all POST data gone missing? and this hotfix by Microsoft