There are two ways to resolve this issue:
Option 1 - The Quick Fix. Remove the versaSRS-related cookies from the browser then reload versaSRS. This will clear the sorting preferences and allow the Case Searching results to be viewed again.
Please refer to the linked KB article for instructions on removing versaSRS Cookies: NOTE: This is not a permanent solution. Do not attempt to sort the result columns again or the same error will occur.
Option 2 - The Resolution. If Custom Columns are used in the application, updating the current stored procedure can resolve this issue permanently. As the Database Admin, download the attached zip file (StoredPRocedures.zip) and follow the below instructions:
1. Access the versaSRS database, search for the following Custom Stored Procedures:
(YourDataBase > Programmability > Stored Procedures)
sp_Call_Search_By_Page
sp_Full_Text_Call_Search_With_Attachments_By_Page
2. Right click onto the above Custom Stored Procedures and select Modify.
3. Copy the content in attached file and paste it in the Custom Stored Procedures. If there are previous custom scripts, replace the content with the previous scripts.
NOTE: The first line in the file 
will need to be changed if the database being modified is NOT named 'versaSRS'
4. Select Execute to Save.
NOTE: This will modify the above mentioned Custom Stored Procedures, we recommend saving the original files first. We also recommend upgrading the application in a test environment (where possible) to verify it is successful before trying on the Production environment.