This error is very common in SharePoint environment and there are few reasons to cause the issue. But as a root cause, every issue needs to do something with SQL Server installed on your SharePoint Server.


Low disk space

This is the most common reason in most SharePoint environments and it is due to Low Disk Space in your SQL Server.



You might see this when you are creating a New Page or New Item in SharePoint environment. Basically, you are trying to contribute to the SharePoint Environment.


  • If it is a SQL Express environment make sure you are not exceeding the limit of 4GB.

  • Check your Hard Disks spaces in SharePoint SQL Server for Log Disks and Date Disks.

Read permission issue

You might see this error when you are opening a SharePoint List and believe me this is also a very common scenario when you are working with SharePoint.


This is caused by not having read permission to columns items in the list which might be a lookup list and the current user does not have permission to read that item in the reference list.

So the case will be there might be a permission issue in the reference list to read.

  • First case there might be not having permission at all to read. You can check the permission from the list permission setting.



If the user has permissions check item-level permissions in Advanced List Settings. Users may be restricted to read-only items which are created by the same user.


Row Ordinal limits

Having more columns exceeding the SharePoint limits of Row Ordinal may cause this error.

SharePoint stores data in SQL Table. If SharePoint can not store in one row it will store the data in another column and which will be handled by Row Wrapping Property.

So Row Ordinal will be a sequence of 0 to the upper margin of the Row Ordinal.

Assume you have a SharePoint list item which is storing data in two rows and row ordinal. So first few columns will be stored in Row 1 and next set will be stored in Row 2.

But when you change the order of the items which is already stored it may be false to two different row ordinals and might cause the issue.

So you can change the column order again to make your environment work.

Note: You can change the maximum limit by using following script:

$web = http://mywebapplication
$webapp = Get-spwebapplication $web
#the default value is 6
$webapp.MaxListItemRowStorage = 8

CAML Queries

This is also a common issue when you are using CAML queries and specifying a data type which is not the actual data type and not a compatible type.

Assume you have a Column Boolean and you are specifying text in the field query.

Incorrect CAML Query that throws an error:

<FieldRef Name="AcctualBooleanFeild" />
<Value Type="Text">Yes</Value>
Correct Query
<FieldRef Name="AcctualBooleanFeild" />
<Value Type="Integer">1</Value>

This is happening because conversion failed happens in SQL level when SharePoint tries to execute the query.

SP Content Database

There can be a situation you are getting this error after you migrate one SharePoint content database to another SharePoint Server. Simple when you mount a database from another farm to your farm as a content database.

This may be also causing read conflicts with SQL database for users. You can delete the unique permission in SharePoint cached profile to resolve this issue.


And delete any unique permissions in the List.

Other causes

There can be many causes other than mentioned.

Feel free to extend this article and report other issues and their solution related to this error.