multi-part identifier "t1.__RowNumber__" could not be bound.

I get the below error often and the server goes down. There was an issue for this which was closed. Can i get the fix for the same ?

The issue goes away after a couple of restart to WWW Service and App Pool Recycling. After that it re occur again when the application pool recycles.

The issue related to this is https://github.com/nopSolutions/nopCommerce/issues/3374

An unhandled exception occurred while processing the request.
SqlException: The multi-part identifier "t1.__RowNumber__" could not be bound.
The multi-part identifier "t.__RowNumber__" could not be bound.
The multi-part identifier "t1.__RowNumber__" could not be bound.
The multi-part identifier "t.__RowNumber__" could not be bound.
The multi-part identifier "t1.Id" could not be bound.
The multi-part identifier "t1.AllowCustomersToSelectPageSize" could not be bound.
The multi-part identifier "t1.CreatedOnUtc" could not be bound.
The multi-part identifier "t.Id" could not be bound.
The multi-part identifier "t.AllowCustomersToSelectPageSize" could not be bound.
The multi-part identifier "t.CreatedOnUtc" could not be bound.
The multi-part identifier "t.Deleted" could not be bound.
The multi-part identifier "t.Description" could not be bound.
The multi-part identifier "t.DisplayOrder" could not be bound.
The multi-part identifier "t.LimitedToStores" could not be bound.
The multi-part identifier "t.ManufacturerTemplateId" could not be bound.
The multi-part identifier "t.MetaDescription" could not be bound.
The multi-part identifier "t.MetaKeywords" could not be bound.
The multi-part identifier "t.MetaTitle" could not be bound.
The multi-part identifier "t1.Description" could not be bound.
The multi-part identifier "t.Name" could not be bound.
The multi-part identifier "t1.DisplayOrder" could not be bound.
The multi-part identifier "t1.LimitedToStores" could not be bound.
The multi-part identifier "t1.ManufacturerTemplateId" could not be bound.
The multi-part identifier "t.PageSize" could not be bound.
The multi-part identifier "t1.MetaKeywords" could not be bound.
The multi-part identifier "t.PageSizeOptions" could not be bound.
The multi-part identifier "t1.MetaTitle" could not be bound.
The multi-part identifier "t.PictureId" could not be bound.
The multi-part identifier "t1.Name" could not be bound.
The multi-part identifier "t.PriceRanges" could not be bound.
The multi-part identifier "t1.PageSize" could not be bound.
The multi-part identifier "t1.PageSizeOptions" could not be bound.
The multi-part identifier "t.Published" could not be bound.
The multi-part identifier "t1.PictureId" could not be bound.
The multi-part identifier "t.SubjectToAcl" could not be bound.
The multi-part identifier "t1.PriceRanges" could not be bound.
The multi-part identifier "t.UpdatedOnUtc" could not be bound.
The multi-part identifier "t1.SubjectToAcl" could not be bound.
The multi-part identifier "t1.UpdatedOnUtc" could not be bound.

Try to open appsettings.json file, set "UseRowNumberForPaging" to "false and restart the site

We use SQL Server 2008 R2. Is it still ok, to set UseRowNumberForPaging to false ?

I get the below error if it set it to false

An unhandled exception occurred while processing the request.
SqlException: Incorrect syntax near 'OFFSET'.
Invalid usage of the option NEXT in the FETCH statement.

Can you please help me on this issue ? We are struck and the error keeps occuring.

Hi,

Did you ever find a fix for this issue?

I have the same problem with site crashing every couple of days:
If I set UseRowNumberForPaging to False I get the below error:
SqlException: Incorrect syntax near 'OFFSET'.
Invalid usage of the option NEXT in the FETCH statement.

And if I set UseRowNumberForPaging to True I get the below error:
An unhandled exception occurred while processing the request.
SqlException: The multi-part identifier "t1.__RowNumber__" could not be bound.

Would upgrading SQL Server 2008R2 to a more recent version solve issue?

Kind regards,
Joe

JoeWalsh wrote:
Yes