We have a WSS 3.0 team site that has moved from one server to another.
The site shows some weird behavior now -- for example it doesn't
automatically recognize default.aspx.

I thought I would export it before making changes to see if I could
fix, but I'm getting this error on stsadm -o export:

[3/5/2008 8:59:17 AM]: FatalError: There is no row at position 0.
at System.Data.RBTree`1.GetNodeByIndex(Int32 userIndex)
at System.Data.RBTree`1.get_Item(Int32 index)
at System.Data.DataRowCollection.get_Item(Int32 index)
at
Microsoft.SharePoint.Deployment.ObjectHelper.RetrieveDataFromDatabase(ExportObject
exportObject)
at
Microsoft.SharePoint.Deployment.FolderObjectHelper.RetrieveData(ExportObject
exportObject)
at
Microsoft.SharePoint.Deployment.ExportObjectManager.GetObjectData(ExportObject
exportObject)
at Microsoft.SharePoint.Deployment.ExportObjectManager.MoveNext()
at
Microsoft.SharePoint.Deployment.ExportObjectManager.ExportObjectEnumerator.MoveNext()
at Microsoft.SharePoint.Deployment.SPExport.SerializeObjects()
at Microsoft.SharePoint.Deployment.SPExport.Run()

Yuck! I thought we were done with that sort of thing in 3.0! Any idea
how to detect what the corrupt item is so I can nuke it? How do you
recover a corrupted site (I'm assuming that's what this is). And how
could it have gotten corrupted?

Thanks,

Jeff