Last post Jan 13, 2017 11:57 AM by PatriceSc
Jan 05, 2017 11:58 PM|Taichung|LINK
HI I'm using VS2013. I need help with this run time error I got. I don't see the physical folder of Account or file Login. Why is the program looking for it? How to get rid of this error, thank you.
View more information »
Jan 06, 2017 07:42 AM|Cathy Zou|LINK
From your error message.
This problem occurs because the query string length of the requested URL is longer than the length that is specified in the maxQueryString property in the ApplicationHost.config file.
To resolve this problem, follow these steps:
<requestLimits maxQueryString="length" />
Beside, if the problem is still existed. you could check the following links:
Jan 06, 2017 12:47 PM|markfitzme|LINK
Is this an MVC project? If so you don't need physical folders to show this. Look for a controller named Account or Login.
This most likely is shown because of the authentication type that was chosen when the project was first created and most likely is using asp.net Identity as a user store and restricting some pages by default.
Jan 06, 2017 05:38 PM|Taichung|LINK
Hi Mark, in this solution there are 4 projects. One is a Web Api project template with MVC selected when I created the project. But that is not the startup project. I'm getting this error from a Web Form project that I set as start up project.
The odd thing is this start up project that's getting the error when started is not a MVC project. I can't find anything that says Login or Account of any type and definitely no controllers for this project.
This Web form project is created as a Intranet application. Is this the problem?
Jan 06, 2017 06:09 PM|Taichung|LINK
Following your instruction, I entered the file name
%windir%\System32\inetsrv\config\applicationHost.config but it says path not valid. I did this from root of C:\. Where should I look? I'm going a search now on File Explorer.
From C drive, it found about 6 of applicationHost.config files but non of it is from under System32 folder. My PC is runing Windows10, does that change the path?
Jan 06, 2017 06:40 PM|Taichung|LINK
<compilation debug="true" targetFramework="4.5" />
<httpRuntime targetFramework="4.5" />
<authentication mode="Windows" />
<deny users="?" />
<pages>I added the following to the start up project's web.config according to the 1st link you provided.
Any suggestions that I should try? Thank you.
Now I get the same error but in a better looking normal error screen message as follow:
An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.HttpException: The length of the query string for this request exceeds the configured maxQueryStringLength value.
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
[HttpException (0x80004005): The length of the query string for this request exceeds the configured maxQueryStringLength value.]
System.Web.PipelineStepManager.ValidateHelper(HttpContext context) +53
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.6.1073.0
Jan 13, 2017 11:19 AM|Cathy Zou|LINK
Please check the section in your config file:
<httpRuntime maxRequestPathLength="260" maxQueryStringLength="2048" />
By default, the query string lengths was constrainted to 2048 characters. To allow longer or shorter query strings, modify the maxQueryStringLength attribute, please.
Please check the following link:
Jan 13, 2017 11:57 AM|PatriceSc|LINK
Double check the permission. If I remember I saw once someone having a similar problem because he is not authorized to the login page so ASP.NET tries to redirect hem to the login page keeping the returnurl and it then starrs for the next cycle until it
gives up because the query string turns out to be too long.
Or you are not supposed to have any authentication here? Check what is configured for that including at the IIS level...