Hi,
I am having a problem with the filtering on a RadGrid. The grid functions perfectly when running the code locally or on our Dev server, but fails when in out Test or Production environments. The only difference between the 4 environments is that each has incrementally more data in the database. Locally I am trying to filter about 2000 records, where as in Production it is closer to 4000. The only place I receive any indication that there is a problem is when using firebug. After typing in the box and selecting 'Contains' I get the following from the response :-
I am having a problem with the filtering on a RadGrid. The grid functions perfectly when running the code locally or on our Dev server, but fails when in out Test or Production environments. The only difference between the 4 environments is that each has incrementally more data in the database. Locally I am trying to filter about 2000 records, where as in Production it is closer to 4000. The only place I receive any indication that there is a problem is when using firebug. After typing in the box and selecting 'Contains' I get the following from the response :-
53|error|500|Object reference not set to an instance of an object.|
If I check the response from the Dev environment I get a full page response.
Please let me know If someone can help.....
2 Answers, 1 is accepted
0
Accepted
Hello Matthew,
The code of the error claims that there is server error(500). If you are using RadAjax(RadAjaxPanel/RadAjaxManager) to ajaxify RadGrid you set EnableAjax to False and see the real stack trace of the error.
Regards,
Nikolay
the Telerik team
The code of the error claims that there is server error(500). If you are using RadAjax(RadAjaxPanel/RadAjaxManager) to ajaxify RadGrid you set EnableAjax to False and see the real stack trace of the error.
Regards,
Nikolay
the Telerik team
Browse the vast support resources we have to jump start your development with RadControls for ASP.NET AJAX. See how to integrate our AJAX controls seamlessly in SharePoint 2007/2010 visiting our common SharePoint portal.
0
Matthew
Top achievements
Rank 2
Rank 2
answered on 22 Dec 2010, 05:43 PM
Thanks for the reply. Turned out to be a Data issue.