Home Forums SQL Server 7,2000 Backups Error msg: Could not continue scan with NOLOCK due to data movement. RE: Error msg: Could not continue scan with NOLOCK due to data movement.

  • Greetings!

    I've landed in this post because I have a similar problem.

    I work in an organization with several development servers. I have made linked servers to all of them from my notebook to keep some control of the changes made in every database on the servers and developed a process that goes through every server and database to track this information weekly.

    Today everything went fine as always, except for one server: the error message was "Attempt to fetch logical page (1:110800) in database 14 failed. It belongs to allocation unit 14073963587174400 not to 281474978938880."

    I connected to the instance (2008 R2) from the client in my notebook and effectively I couldn't see any element in that database, not even its properties. I executed DBCC CHECKDB but everything went OK. I tried to look at the error LOG but now the error is: "Could not continue scan with NOLOCK due to data movement" (shown in the window). This same error is shown when I try to query any other database from that instance through the linked server in my notebook. I have other instances in that server and they work fine.

    Really, I've read all over and can't find an answer, these databases don't seem to be corrupt! thank you for your patience, I'll appreciate some answer.