KB Article T228863
Visible to All Users

What to do when the grid displays blank rows in Server Mode

Description:
This article describes how to troubleshoot a situation when the grid bound to data in Server Mode displays no data. At the same time, data in the database is valid and columns in the grid are bound to existing data source item fields. The problem might occur immediately or after a user applies sorting or filtering.

Answer:
In Server Mode, the data loading operation usually consists of two actions. First, the Server Mode collection requests a database for a total number of records. When the number is obtained, it loads data from the database.
The state when the grid displays empty rows indicates that the total number of records is obtained but an attempt to load data failed. The failure usually followed by a CLR exception that is handled internally. So, the application does not fail due to this exception but the grid displays no data in cells. Under certain circumstances, data might be displayed partially.
Since this problem is always caused by an internal exception, it is not difficult to determine its cause if you can reproduce the problem in the development environment where you can debug your application with Visual Studio.
By default, Visual Studio debugger does not catch handled exceptions or exceptions thrown in third-party code. To debug such exceptions, it is necessary to enable catching user handled exceptions as described in the the How to: Break When an Exception is Thrown article and disable the Show Just My Code option in Visual Studio settings (see Managing Exceptions with the Debugger). Precise steps are described in our Knowledge Base article: How to obtain the exception's call stack.

When the debugger breaks with an exception, carefully read the exception message. Some exceptions are not relevant. Such exceptions as FileNotFoundException, UnauthorizedAccessException, SecurityException, HttpException, etc. are irrelevant to the problem discussed here. Feel free to skip these exceptions and continue debugging until you catch an exception that is of interest.
Once you find an exception that you feel is related to the problem, the work is almost finished. In most cases, the exception message clearly identifies the cause of the problem, and you just have to fix it.

If it is not possible to debug the problematic scenario in Visual Studio (for example, the problem is reproduced by an end user), it is still possible to obtain information about exceptions. For this purpose, you can use the AppDomain.FirstChanceException event to write all exceptions messages and stack traces into a log file.
If it is difficult to determine the cause of the exception based on the error message, feel free to report this issue to our Support team. Attach the exception stack trace and message to your inquiry and provide a brief description of the issue. When does it occur? What actions does an end-user perform before the issue occurs? Our engineers have wide experience in solving such issues and will do everything possible to help.

See Also:
T218612: ASPxGridView / MVC GridView Extension displays empty rows when bound via Server Mode

Show previous comments (6)
DevExpress Support Team 9 years ago

    Hello Matt,

    To process your recent post more efficiently, I created a separate ticket on your behalf: T331907: What to do when the grid displays blank rows in Server Mode. This ticket is currently in our processing queue. Our team will address it as soon as we have any updates.

      Hi,

      The links in the article are outdated.

      Thanks,
      Marcelo.

      Sasha (DevExpress Support) 5 years ago

        Hello Marcelo,

        Thank you, I updated the links.

        Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

        Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.