hi guys,
Does anyone have any knowledge about the error seen at the image down below
The error occurs after waiting on the page for a while and then requesting an ajax call. The error is not repeated afterwards, but when the user waits again the error pops up again too. So the problem is about waiting on the page for a while, but could not find out why?
Thanks for the incoming responses
edit:link to image http://i53.tinypic.com/2ni8bcg.png
Well, basically an exception is occurring within your web service. It sounds like it's probably something timing out.
The first thing you should do is improve your logging (e.g. with ELMAH) so you can see exactly where the exception is being thrown... and then go about fixing it.
If it's a database connection timing out, it could be that you're forgetting to close the connection somewhere...
Related
I'm new on this website and I'm stuck with a server error. I tried everything and i just cant figure it out. I'm also new to asp.net mvc so I'm stil a noob.
I just got a feeling that there is something going on in my web.config.
So the error is that if you go to a certain detail page, you go to the error page that the previous programmer made and that error says: "internal server error"
I deleted that to see the original error message:
Server Error in '/' Application.
Runtime Error Description: An exception occurred while processing your request. Additionally, another exception occurred while executing the custom error page for the first exception. The request has been terminated.
The weird thing is that on my localhost it does work, its just the online website that has the error.
I'm just stuck at this point and need help :(
I don't know what most of the code means in the web.config but I don't want to leak something important so I'm kinda scared to post all the code, there are like publickeytokens and some other stuff
I am using the latest Selenium WebDriver running using .NET/Microsoft Technology stack.
What I am observing these days is that all of my tests in the suite starts failing throwing this exception
Additional information: A exception with a null response was thrown sending an HTTP request to the remote WebDriver server for URL http://localhost:5557/wd/hub/session/c775e68e-c842-41b3-a1a6-44a88ef4c210/element. The status of the exception was KeepAliveFailure, and the message was: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
I am not able to figure out what is the issue and what I need to do to resolve this issue. I am quite sure this is not to do with the coding.
The issue mainly occurs when I try clicking on a button or trying to enter some text in the input box.
Could any one please point me in the right direction as what I need to resolve this issue
Thanks
This is old but thought I'd throw an answer here for anybody stumbling upon the same issue. Ran into this earlier today. I was able to get it to work by reducing the polling interval of the wait:
WebDriverWait myWait = new WebDriverWait(driver, TimeSpan.FromMinutes(5));
myWait.PollingInterval = TimeSpan.FromMilliseconds(500); //I reduced this from checking every 5 second to checking every half second and it started working.
bool waitOnUser = myWait.Until(t =>
{ ...});
I am using Microsfot Lightswitch, running my deployed applications as Virtual Directory in IIS. So far it is working fine. Since yesterday I am getting the error message right after successful login.
The application has stopped responding due to an error and needs to be restarted.
Error details: [Arg_NullReferenceException]
Arguments:
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.30214.00&File=mscorlib.dll&Key=Arg_NullReferenceException
I also used fiddler to trace the actual error, but still could not find. Here is the fillder's screen shot:
Can any body suggest what could be actually going wrong, or how can I reach to the actual real error?
Edit: It seems there is some problem with the read-line in fiddler, but I am unable to dig down the real error, actually I am new to fiddler.
im trying to make a HTTP request loop, however, it seems to fail after the first time. i have no idea why this is happening, ive had a look around online and it's something to do with closing the request and then restarting it(i think), but i cant seem to do it?
my loop code is available here http://pastie.org/4199450
i get the following when i run it:
SUCCESS!
connection failed
connection failed
..
Anyone got any ideas?
You are connecting to the server/port once without disconnecting after.
Then, you try to connect again but you are still connected. This may be the reason why the connection line fail the second times.
I am using Asp.Net c# and Sql Server 2005. I am using Masterpage and content page. when i debug my code that time it's give error ::
Window Internet Explorer
SYS.WEBFORMS.PAGEREQUESTMANAGER TIMEOUTEXCEPTION: THE SERVER REQUEST TIMED OUT.
Any body please help me out ?
Thanks
It is an Ajax error - do you only get the error when debugging? If you want to increase this timeout then set the AsyncPostBackTimeout of your script manager to something large
You have an ajax request that's taking too long to complete. It would help if you can isolate the request and share what it's trying to do.
This happens if you sit there too long trying to step through your ajax request. Either increase the timeout or work faster.
Incidentally, I believe the timeout setting defaults to 90 seconds. See this for more information.
I don't see anything immediately obvious in that error message to suggest it's a SQL server request that's timing out rather than any other sort of "server request". However, if it is, stick a profiler on your SQL server to see which request is taking a long time - and find out whether it's just a query which needs speeding up, a deadlock, or something like that.
Another possibility is that it's the connection pool - if you're not closing your connections properly, you could be timing out waiting for them to be returned to the pool. If that's the case, you obviously won't see the request in the SQL profiler.