I am facing a peculiar problem with an asp.net 2.0 application(C# code behind) which has been running smoothly for last 3 years or so.The thing is that I have one custom object named "Horse" which becomes null at a particular line where I check for its nullability though there is seemingly no reason for its becoming null at this line.Interestingly when I spit the content of this object using Response.Write just before the line where I am getting the null reference exception, it shows the content of the "horse" object to the browser.
More interesting thing is that if I access the page from IE 6.0 and IE 7.0,I don't get the exception at all.But if I use IE 8.0,then I get this exception.
Can anyone please tell me reason and solution for this issue?
Thanks in advance!
Subrata
What Rex M and Nikhil say are very true. However, have you tried clearing cookies/cache?
If the app is relying on a cookie and the browser storage has become overloaded then I've seen this happen before.
Related
I'm getting an Invalid length for a Base-64 char array error, but it's not my code and I don't see any explict references to this function. I know that it could be a problem with the ViewState or a '+' decoding problem with Request.QueryString, but is there anything else where something is being implicitly converted to Base 64?
Edit: I'm just given a bunch of code and an exception message pointing to some pages, so I'm looking for absolutely anything related that could be suspicious - but I don't know what those look like. No debug privilages either so I have to just scan through and make guesses.
You need to use the debugger to find out exactly which line is causing the error. You can find this out by having the debugger break whenever an exception is thrown in your code. Do the following within Visual Studio (I am showing Visual Studio 2012):
Click the Debug menu.
Choose Exceptions...
You will now see the following:
As the picture shows, make sure the Thrown checkbox is checked for Common Language Runtime Exceptions.
Click OK and the next time you run your code, the debugger should halt at the line that is causing the Invalid length for a Base-64 char array error.
I'm writing a small ASP .Net application in order to retrieve data from a SQL database. The application uses drop downs in order to select what the next drop down should contain and when a page is selected, it should retrieve the HTML from the database. Everything is working until it gets to the retrival of the HTML data. When I try to retrieve the data, I get:
Microsoft JScript runtime error:
Sys.WebForms.PageRequestManagerServerErrorException:
An unknown error occurred while
processing the request on the server.
The status code returned from the
server was: 500
The HTML column is a defined as NVARCHAR(MAX), but I can't see this causing a problem. The application works if I set the DataValueField to another column. Has one else come across a problem like this? Maybe someone could shine some light on this?
One thing I noted when dealing with varchar(max) columns is that the framework still commonly expects to have a size associated with it. What I ended up having to do was specify the length as -1 to get it to accept a varchar(max) field. Your error message doesn't indicate that this is the problem, but you might try experimenting with it rather than turning off the validation, which could possibly have other repercussions.
Figured it out. Just needed to set ValidateRequest to false at the Page level.
I have a site in ASP.NET using Telerik AJAX controls.
Despite the latest binary being added to the website project, my code (eg myRadGrid.Datasource = "";) shows a red line on type names as they cannot be found for some reason.
Can anyone possibly explain why or have experience in this sort of problem?
Thanks
Why are you assigning an empty string to the radgrid datasource property? Try setting it to null instead, which is what you do if you want to clear the data source...
I have a flex application which is configured with blazeds sever and i am pulling images from remote database from my flex application, but as soon as i click the get image button to pull images it is giving some action script error.
TypeError: Error #2007: Parameter bytes must be non-null.
at flash.display::Loader/_loadBytes()
at flash.display::Loader/loadBytes()
I tried googling but couldn't found any solution.
Any help is appreciated.
You have a null parameter inside the function flash.display::Loader/loadBytes(). ;)
Short answer is that you're probably fetching the wrong url. Use firebug or Fiddler or something to determine whether the url is correct. If that's not the case, maybe you're not handling the right events.
Like the comments say, we need the code.
Thank You everyone it was a my code error, it give this error if no value is returned to load bytes . I was pulling a image from a table where no image was present and therefore returning null value in load bytes.
I've begun using ASPUnit to unit test my classic ASP code. This is all good and I'm happy. The only problem is with the error messages it displays when a test generates a runtime error. For example, if I've not defined a variable somewhere in my function I get the error:
Microsoft VBScript runtime error (500): Variable is undefined
What would be more useful is if it could tell me which file/line the error occurred on. I know that I can get this information from the ASPError object which is returned by the Server.GetLastError() and elsewhere in my project I have a custom 500 error page which makes use of this method to automatically report crashes to Fogbugz. However when I try to access Server.GetLastError anywhere else the information returned is blank. For example, the following code will output zero rather than the expected 4.
<%
Option Explicit
On Error Resume Next
aVariable = "hello"
Dim errObj : Set errObj = Server.GetLastError()
Response.Write errObj.Line
%>
Is this the correct way to access ASPError or is it only possible on custom error pages? Is there a better way to get error messages reported within ASPUnit?
To the best of my knowledge the ASPError object does not get populated until your current page finished processing. Its meant to only be used on the 500 error page only. So theory is when you get an error if you've set up your 500 page then IIS will do an internal redirect to that page to allow you to at least record the error. Then and only then is the ASPError object available. I've had crazy ideas of using a xmlhttprequest to try to grab the page but thats just not the way it works.
In short there is not much you can do to get that error message details that you want.
Using JScript server side you can use try catch's which give you access to a exception object but even thats not much good to you, no line numbers or anything. Rubbish.