Results 1 to 5 of 5

Thread: Optimistic concurrency check failed. The row was modified outside of this cursor.

  1. #1
    Join Date
    Jan 2008
    Posts
    2

    Optimistic concurrency check failed. The row was modified outside of this cursor.

    Making the move from SQL 2000 to SQL 2005. In doing so one of our legacy .asp applications is now displaying this error, Microsoft OLE DB Provider for SQL Server error '80040e38' Optimistic concurrency check failed. The row was modified outside of this cursor., message when trying to update the table. The line from the program where the error occurs reads as follows:

    rsReq.Update();

    and very early in the code is where the value of rsReq gets set and is as follows:

    rsReq = NewRecordSet("SELECT * FROM All_Jobs where JobPostingID = " + reqNumber);

    I did not write this program so I am clueless as to why this error is now occuring. (P.S. it still works fine in SQL2000, but we have to move off that server to be license compliant)

    Any suggestions on where and what to be looking for to resolve the problem?

  2. #2
    Join Date
    Sep 2002
    Posts
    5,938
    What's db compatibikity level on sql2k5?

  3. #3
    Join Date
    Jan 2008
    Posts
    2
    The compativility level is SQL Server 2000.

  4. #4
    Join Date
    Jul 2008
    Posts
    1

    Did you find a resolution?

    I also just upgraded from SQL Server 2000 to 2005 and am getting the very same error in code that works fine with SQL Server 2000.

    Did you find a resolution to this problem?

  5. #5
    Join Date
    Nov 2002
    Location
    New Jersey, USA
    Posts
    3,932
    Are you using snapshot isolation level?

    You can see that from sys.databases view.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •