I am getting following error on a new website created on IIS. I am able to see URL Rewrite deployed on this IIS instance. But the new website is not configured to use it. Please find the screen shot of the error message also attached. I searched across numerous forums and no find. I vaguely remember somehow fixed this issue previously, may be 1 year back or so . Since there is no log of the solution traced anywhere, I am in the same bad situation once gain. Please help me if anybody solved this kind of problem.
Thanks in advance
Praveen
Finally I was able to make out what is going wrong. IIS is adding dependency on URLScan by default when a new website is created, but not sure why. I was able to see this in ISAPI Filters (Please refer attached screen shot). Everything worked fine once I removed URLScan from ISAPI filters.
Related
I have been working on an intranet site and recently users have been complaining that when they save a change they get "This site can’t be reached." The users are using Chrome exclusively as far as I can tell, and when I tested with Edge, I got no errors. So, I first tested on the web server, I was unable to recreate the issue. I tried on another server within the network and I was also unable to recreate the issue. I then tried my pc, which was connected through a VPN and was finally able to recreate the issue. What is weird is that this just started happening and I haven't updated the site in quite awhile. The can view most pages and the issue only seems to happen when posting to IIS. At this point, I am not sure where to start to troubleshoot this issue. Any help would be appreciated.
Edit: Updated the title to show the actual error I got.
Edit 2: Someone put me on to checking the httperr log and I see an error for the post request with client_reset as the error message. hope that makes the issue a bit more clear.
I found the issue with help from the network security firm the client was using. Once I was able to confirm the issue only occurred when clients who were using a VPN, he ran some tests. The issue was that the firewall was blocking posts that seemed suspicious. Now, this site has been running for years with no issues. My assumption is that they made some security changes and it caused this problem. What was odd, was that I tried a few fixes and they would work for a few times and then would stop working, such as using the site ip address versus the domain name. I hope this helps the next person.
Wade
So I am just in utter disgust at what happened. i was working on an asp.net in TFS application and all of the sudden it literally just stopped working. Every time I tried to launch it in a browser it would display this error:
The entire DESCRIPTION states:
Description: HTTP 404. The resource you are looking for (or one of its
dependencies) could have been removed, had its name changed, or is
temporarily unavailable. Please review the following URL and make
sure that it is spelled correctly
I haven't the slightest clue what happened. I have not to my best recollection done anything to jeopardize it.
This is what I've done. since I have two different logins to my computer, I took the solution and tried to launch it in my 2nd login and it worked perfectly. I took that same solution file and tried to launch it in my current login and it's causing this issue.
I reset all my Visual studio settings and tried to launch the solution and again - get the same error.
It is showing the SERVIER ERROR in /HOME.aspx - but this error does not show up in my other login.
Does anyone have any idea what could cause this? I'm basically looking at creating a new user profile for myself to get this resolved. Any help will be much appreciated.
Could it be my user profile or would simply re-installing VS could resolve it?
I have a problem when placing an App module(v 8.4.8) on a page. When I placed an App module on a page I got a pop up saying "Had an error talking to the server (status 404). if you are an advanced user you can learn more about what went wrong - discover how on 2sxc.org/help?tag=debug".
This error happens on whatever action I try to do: trying to add and app, refresh page etc.
I checked a communication to the server using Firebug and seems that one of APIs are missing:
~/desktopmodules/2sxc/api/view/Module/GetSelectableApps
Referer: ~/desktopmodules/tosic_sexycontent/dist/dnn/ui.html?sxcver=8.4.8.19191
Did I missed something? Should I make some configuration after SexyContent module install (v 8.4.8)?
I just checked a video by Daniel Mettler where he showed how to install a module and seems that process is simple. Nothing to worry about.
Does anybody has any idea what might went wrong here?
The same actually happens when I install and Content module: Error about missing APIs:
~/desktopmodules/2sxc/api/view/Module/GetSelectableContentTypes
~/desktopmodules/2sxc/api/view/Module/GetSelectableTemplates
Thanks a lot for your time
My best guess is that it's an issue with the dnn domain/path configuration. So basically my guess is that
you have multiple domains, and if this is configured incorrectly, the paths in the js-calls won't fully match the original one
you have sub-portal (with paths like /products/) or something, and this isn't configured correctly in dnn
languages in portal-paths are causing similar issues.
So please compare EXACTLY the full base path and see if that's the issue.
I have installed kloxo control panel, this is the address http://173.212.227.142:7778/. Then I made domain for my test site, which shows me preview from this link, http://173.212.227.142:7778/sitepreview/kids.com/index.html, which is right.
Now I have installed drupal but it is very hard for me to set here. I have made changes in configuration file like database, and in base_url. But didnot getting the site and it shows me a blank page.Site should come with this address, http://173.212.227.142:7778/sitepreview/kids.com/kids/index.php. I made the base_url as http://173.212.227.142:7778/sitepreview/kids.com/kids.
Please suggest me the solution.
Thanks
If you have a problem in your settings.php file, Drupal won't be able to connect to the database but will show you a page telling you such. The White Screen of Death means there is some kind of php error. It is difficult to know what kind of error from your description. Look in your error logs for php errors and tell us what you see, and it will be easier to help you out.
The white page could be the result of a php error, possibly due to a configuration/setting oversight. You should check your Webservers error log(s) for this, as they might give you some hints on possible causes.
Read this: http://drupal.org/node/158043
Please see my DNN Forum Post for more details.
I've never had any issues with DotNetNuke installations. But with the new v5.20 (or v5.02, whichever it really is), everything runs perfectly fine through installation. I then get to the main default portal homepage. But as soon as I click any of the links available to continue (Home, Register or Login) I get 404 errors every time with a reference back to the applicable aspx page (Home.aspx, Register.aspx or Login.aspx.).
Windows 7, IIS7, SQL Server 2008. All permissions are setup properly on the directory and in IIS. I would think this is an IIS7 configuration issue, but I've tweaked everything in there a half-dozen times. No one at DNN is returning answers on my forum post anymore either after one guy tried.
Help!
This is something to do with the Friendly URL stuff. I found this blog post which talks about the Friendly URL Provider architecture. This made me try changing the urlFormat attribute for the DNNFriendlyUrl provider from "humanfriendly" to "searchfriendly", which made the URLs the way they used to be. I'm not sure exactly where things are going wrong and don't really have time to dig into it at the moment, but hopefully this will be helpful to get you moving again too.
With the release of DNN5 (up until 5.02.01 as of the time of writing), the friendly URL provider won't work when DotNetNuke is not on default port 80. There are different solutions floating around, but the simplest is just to replace the DNN friendly URL provider with the free one from iFinity. The installation is really simple and included in the download. Or see the following blog post:
http://www.sailer.com.au/dotnetnuke/dnn5-friendlyurl-port
Okay have you tried the 'old style' of login - domain.com/default.aspx?ctl=login
If that still doesnt work then i have to say that most likely something has happened to IIS - if so then you might just see if you can install the package you have on a different box or have a friend try a different box
I have done 2 upgrades with 5.2 and a few test installs with the Starter Kit Package and Install packages and have never seen this problem - not to say that it doesnt exist.
My next trial would be to go and redownload the install package from CodePlex and start from scratch to see if you can make the same thing happen again.
OKayone thing I dont think that has been mentioned in reading through everything is double check IIS.
My first guess without looking on your server would be to check if something happened to the 'check file exists' setting - i know this is changed in IIS7 so I cant point to the exact place to check this.
Here is a link to the IIS7 forums on it - http://forums.iis.net/t/1092696.aspx
http://forums.asp.net/t/1191083.aspx
either one might help - google also has a lot on this
Tell me how this goes in checking up on it and we can move forward from there!
you probably need to reg_iis on the version(s) of asp.net that your IIS is going to support.
http://msdn.microsoft.com/en-us/library/k6h9cz8h(VS.80).aspx
If the right version is not set up then you will get the 404 error
So placing it under port 80 works, right?
Is there a good reason not putting it under that port?