Skip to main content

The request filtering module is configured to deny a request that contains a double escape sequence.

HTTP Error 404.11 - Not Found
The request filtering module is configured to deny a request that contains a double escape sequence.

The request contained a double escape sequence and request filtering is configured on the Web server to deny double escape sequences.

Details of the issue is available at:
http://support.microsoft.com/kb/942076/

Resolution summary: Would suggest to read the complete article but just for quick reference I am typing the resolution here.

%windir%\system32\inetsrv\appcmd set config "Default Web Site" -section:system.webServer/security/requestfiltering - allowDoubleEscaping="true"

Or change manually by opening the following file
%windir%\System32\inetsrv\config\applicationHost.config file in notepade. (remember to open notepade with administrator privilege.

and change following value.
Labels:

Comments

  1. Anonymous11:26 AM, September 09, 2008

    Hi, thanks for the help in figuring this out. Thought you should know that in my browser (Firefox) the last part of your comment doesn't show up. I see it in the source as
    requestFiltering allowDoubleEscaping="true"

    with angle brackets around it. I didn't include above in case it didn't show in the comments either. Just FYI.

    ReplyDelete
  2. Vinod Sharma2:34 AM, September 10, 2008

    Thank for letting me know about this issue. I updated and fixed the issue.

    Thanks again.

    ReplyDelete

Post a Comment

Popular posts from this blog

SharePoint WebPart Error - Unable to add selected web part (s) – MOSS 2007

ISSUE: Recently I faced this issue that when I try to deploy my WebPart.  Unable to add selected web part(s). WebPartName: Cannon unregister UpdatePanel with ID ‘ctl00RTMPanel’ since it was not registerd with the ScripManager. This might occure if the UpdatePanel was removed from the control tree and later added again, which is not supported. Parameter name: updatePanel.   I faced this issue twice and both the time the issue was not what display here. This could be sure to any error in the WebPart. Following are list resolution from multiple instances.   RESOLUTION: 1. Check the WebPartName.webpart file. Check whether you have a proper PublicKeyToken value. When I face the issue the value was PublicKeyToken=$PublicKeyToken$. If you have used WSP builder then in the Visual Studio you will find this file at \WebPartsProject\12\TEMPLATE\FEATURES\WebPartName\WebPartName.webpart. Sometime when you create a new WebPart using WSP builder then ...
4 comments
Read More >>>

TIME – 25 Best Blogs of 2009

Every year Time makes a list of best blogs in the world. They chose 25 blogs from millions of blogs in the world, spanning politics, housekeeping, astronomy and everything in between. Below if a direct link to the TIME website for the list. I also copied it to easy comparison of last year best with this year best blogs.   25 Best Blogs of 2009     25 Best Blogs 2008   25 Best Blogs of 2009 Talking Points Memo The Huffington Post Lifehacker Metafilter The Daily Dish by Andrew Sullivan Freakonomics BoingBoing Got2BeGreen Zen Habits The Conscience of a Liberal: Paul Krugman Crooks and Liars Generación Y Mashable Slashfood Official Google Blog synthesis bleat /Film Seth Godin's Blog ...
Post a Comment
Read More >>>

Could not open virtual machine – vmx is not a valid virtual machine configuration file

I recently faced an issue with one of my VMWare virtual machine that when I try to run this virtual machine it did not work. VMWare display this message that “Could not open virtual machine: .vmx. ".vmx" is not a valid virtual machine configuration file.” ISSUE: Could not open virtual machine: G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx. "G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx" is not a valid virtual machine configuration file. I try to open .vmx file [G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx] in notepad then I found it was empty (0 KB). Resolution: I wanted to resolve it quickly so I try following method and it worked very well. But this is not a valid documented process so please try with caution. Following are the steps 1. First of all go to the folder where you have your virtual machine and delete all .lck folders. 564df2d4-03de-04e8-d1c3-bd2d53dcb1b7.vmem.lck Windows XP Professional.vmdk.lck ...
13 comments
Read More >>>