Windows Server 2003 SP2, SharePoint 2007 SP2 + Feb 2010 updates (version number in web is 12.0.0.6529). I have a user trying to modify their site navigation and came up with this error "<Web> is busy. Please try again". I tried the update myself and came up with the same error. I have looked at the following: checked site storage and there's 20GB still available within the site quota. checked SharePoint content database and there's still 40GB availabe within the allocated storage. tried the same update for a different site (in the same content db) and had no issues. checked the server eventlog and ULS logs and nothing there. I then enabled verbose on the ULS logs and the following error occurred that corresponds to the web with the problem: 04/27/2010 14:32:32.22 w3wp.exe (0x2B58) 0x382C Windows SharePoint Services Database 6f8g Unexpected Unexpected query execution failure, error code 3621. Additional error information from SQL Server is included below. "The statement has been terminated." Query text (if available): "BEGIN TRAN DECLARE @abort int SET @abort = 0 DECLARE @EidBase int,@EidHome int SET @EidBase = 0 SET @EidHome = NULL IF @abort = 0 BEGIN EXEC @abort = proc_NavStructAllocateEidBlockWebId '20C46AE4-66A6-48AA-82FC-50BEA5A825D1',0,2100,@EidBase OUTPUT SELECT ? = @EidBase, ? = @abort END IF @abort = 0 BEGIN EXEC @abort = proc_NavStructMoveNode '6DB7F01F-58D1-4404-A5B7-26171AF864AC','20C46AE4-66A6-48AA-82FC-50BEA5A825D1',2100,1002,-2,N'20090428 11:53:29',@EidBase,@EidHome, ? OUTPUT SELECT ? = @abort END IF @abort = 0 BEGIN EXEC proc_NavStructLogChangesAndUpdateSiteChangedTime '6DB7F01F-58D1-4404-A5B7-26171AF864AC','2... 04/27/2010 14:32:32.22* w3wp.exe (0x2B58) 0x382C Windows SharePoint Services Database 6f8g Unexpected ...0C46AE4-66A6-48AA-82FC-50BEA5A825D1',NULL END IF @abort <> 0 BEGIN ROLLBACK TRAN END ELSE BEGIN COMMIT TRAN END " Can anyone help me out?

bump

I found this article which might be relevant... http://groups.google.com.au/group/microsoft.public.sharepoint.portalserver/browse_frm/thread/56b072b856573449/7fd852d663127328?lnk=st&q=sharepoint+Web+server+busy&rnum=4&hl=en#7fd852d663127328 Which says it might be a proxy server issue or MSDE and have reached its database limitation (2GB) hope this helps

Please try to export & import the site. SharePoint was not synchronized properly because of which you experience the problem. stsadm -o export -url [url] -filename c:\Temp\export.bak stsadm -o import -url [url] -filename c:\Temp\export.bakCogito, ergo sum.

Did the export/import this weekend and it worked. Just had to make sure the account under which the export/import runs has site collection admin priveleges.