Link to home
Start Free TrialLog in
Avatar of brl8
brl8Flag for United States of America

asked on

MOSS 2007 upgrade fails: Could not continue scan with NOLOCK due to data movement

Hello All,

We are working on a SharePoint 2007 installation and attempting to upgrade it to SP2.  The upgrade is failing with the following error: Exception: System.Data.SqlClient.SqlException: Could not continue scan with NOLOCK due to data movement

The consultant with whom I am working thinks this is a SQL Server error related to space issues on the Admin Content database.

When I look at sp_spaceused for this database I see the following:
size: 58 MB
Unallocated: 3.23 MB
reserved: 55696 KB
data: 43944 KB
index_size: 10504 KB
unused: 1248 KB

Since I don't know anything about space and how it is allocated and used in SQL Server, I wanted to know if this database has sufficient space, and if not, how would I go about giving it more space?  Are we even on the right track?

Any suggestions or thoughts would be appreciated.

Thanks.
BRL
Avatar of knightEknight
knightEknight
Flag of United States of America image

You will see this error if a database file is shrinking or it's data is moving to another file or another drive.  If you are shrinking a file, stop the shrink operation during the upgrade.
This is not a space issue.  It may be related to Updating Statistics on your databases, probably as an internal part of the upgrade process, or it may be related to restoring a corrupted database from a backup (again, probably as a part of the upgrade), or it could be from excessively fragmented, indexes, or it could be from several other causes, but it is not about space.  You need to check the upgrade log and identify what is happening in the process at the time that the error is generated....
ASKER CERTIFIED SOLUTION
Avatar of Brendt Hess
Brendt Hess
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of brl8

ASKER

Thanks, bhess, I was thinking this was not a space issue.

Our plan of attack now is to do a fresh install of SharePoint on another server, connect the existing content database to it and then hopefully be good to go.  

This is from upgrade.log - any thoughts?

[SPManager] [DEBUG] [10/2/2010 9:26:45 AM]: Upgrading [SPContentDatabase Name=SharePoint_AdminContent_5f894e09-7098-4e72-8d90-cd75f70a5322 Parent=SPDatabaseServiceInstance].
[SPContentDatabaseSequence] [DEBUG] [10/2/2010 9:26:45 AM]: Invalidating WYukon signature in SPContentDatabase Name=SharePoint_AdminContent_5f894e09-7098-4e72-8d90-cd75f70a5322 Parent=SPDatabaseServiceInstance.
[SPContentDatabaseSequence] [DEBUG] [10/2/2010 9:26:45 AM]: ---------------- Begin Table RowCount Dump ----------------
[SPSqlCommandFactory] [DEBUG] [10/2/2010 9:26:45 AM]: SqlCommand.CommandTimeout = 0
[SPSqlCommandFactory] [DEBUG] [10/2/2010 9:26:45 AM]: SqlCommand.CommandTimeout = 0
[SPContentDatabaseSequence] [DEBUG] [10/2/2010 9:26:45 AM]: Table [dbo].[AllDocs] RowCount = 648
[SPSqlCommandFactory] [DEBUG] [10/2/2010 9:26:45 AM]: SqlCommand.CommandTimeout = 0
[SPContentDatabaseSequence] [DEBUG] [10/2/2010 9:26:45 AM]: Table [dbo].[AllDocStreams] RowCount = 5534
[SPSqlCommandFactory] [DEBUG] [10/2/2010 9:26:45 AM]: SqlCommand.CommandTimeout = 0
[SPContentDatabaseSequence] [DEBUG] [10/2/2010 9:26:45 AM]: Table [dbo].[AllDocVersions] RowCount = 0
[SPSqlCommandFactory] [DEBUG] [10/2/2010 9:26:45 AM]: SqlCommand.CommandTimeout = 0
[SPManager] [ERROR] [10/2/2010 9:26:47 AM]: Upgrade [SPContentDatabase Name=SharePoint_AdminContent_5f894e09-7098-4e72-8d90-cd75f70a5322 Parent=SPDatabaseServiceInstance] failed.
[SPManager] [ERROR] [10/2/2010 9:26:47 AM]: Could not continue scan with NOLOCK due to data movement.
[SPManager] [ERROR] [10/2/2010 9:26:47 AM]:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

....


[SPManager] [DEBUG] [10/2/2010 9:26:47 AM]: Elapsed time upgrading [SPContentDatabase Name=SharePoint_AdminContent_5f894e09-7098-4e72-8d90-cd75f70a5322 Parent=SPDatabaseServiceInstance]: 00:00:01.
[SPManager] [INFO] [10/2/2010 9:26:47 AM]: Resetting the status of PersistedUpgradableObject: SPContentDatabase Name=SharePoint_AdminContent_5f894e09-7098-4e72-8d90-cd75f70a5322 Parent=SPDatabaseServiceInstance to Online.
[SPManager] [DEBUG] [10/2/2010 9:26:47 AM]: Using cached [SPContentDatabase Name=SharePoint_AdminContent_5f894e09-7098-4e72-8d90-cd75f70a5322 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: True.
[SPManager] [ERROR] [10/2/2010 9:26:47 AM]: SPManager.Initialize failed.
[SPManager] [ERROR] [10/2/2010 9:26:47 AM]: Could not continue scan with NOLOCK due to data movement.
[SPManager] [ERROR] [10/2/2010 9:26:47 AM]:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
Avatar of brl8

ASKER

thanks!