Row Cannot be located for updating
Article ID
ias-10814
Article Name
Row Cannot be located for updating
Created Date
22nd January 2013
Product
Problem
When using IRIS the following error can occur Core Running Error Row cannot be located for updating. IDispatch Error #3128
Resolution
There are a number of reasons why this error occurs
You are using SQL Server Express and have reached the maximum 1GB RAM limit for this version
You are using SQL Server Workgroup and have reached the maximum 4GB RAM limit for this version
There is insufficient available RAM in the server machine for SQL Server to process the request
In many cases restarting the SQL Service resolves the problem as over time SQL Server RAM usage can grow exponentially. However, if this is a recurring problem there are a number of options available, which are outlined below, but it is advised that you speak to your own IT provider about each one for more details.
Install a new instance of the SQL Server version you are running
It is possible to use multiple databases in one instance of SQL Server. However this can mean RAM usage is higher than expected. RAM limits apply on an instance basis, installing a new instance solely for IRIS use may help.
Upgrade to a more appropriate version of SQL Server
If you are running SQL Server Express and have hit the 1GB Limit you will need to upgrade to SQL Server Workgroup or if you are running SQL Workgroup you will need to consider upgrading to SQL Server Standard
Install SQL Server on its own dedicated server
In many cases SQL Server is installed on a single server along with other business applications such as Exchange, Active Directory etc. All these applications compete for available RAM and this can sometimes mean SQL Server cannot “grab” the required amount of RAM. Moving the installation of SQL Server to its own dedicated server will provide greater resource availability.
Increase the Physical RAM available in the server
Should your server allow you can add more physical RAM. However, this will only help if SQL Server is not able to “grab” enough RAM to complete the process.
NOTE: Adding more RAM to servers running SQL Server Express that have hit the 1.5GB ceiling will have little effect.
We are sorry you did not find this KB article helpful. Please use the box below to let us know how we can improve it.