Prev: IE Error when trying to open Office documents in Sharepoint
Next: Error creating mySite in SharePoint 2007
From: krish.vr on 23 Feb 2007 17:52
You got any solution for this. If so, do post that in this forum?

Thanks
Krish

"BubbleG" wrote:

> I've migrated my SPS2003 Portal to MOSS 2007 Enterprise Trial version
> successfully. Now I'm trying to consolidate my previously disparate
> site collections to be located under the new MOSS Portal collection to
> take advantage of the new features available to sites within the same
> collection. I'm following Shane Young's post on using stsadm -o
> export/import to do this
> (http://msmvps.com/blogs/shane/archive/2006/11/14/consolidating-site-collections-after-upgrading-sharepoint.aspx).
>
> I've been able to move a number of collections into the main MOSS
> collection (under <Server>/SiteDirectory...) and they are showing up as
> part of that collection perfectly. However, on some of my site
> collections, I'm getting a "User cannot be found" error at the start of
> the export process. This occurs with or without the
> -includeusersecurity option.
>
> I've gone into the site collection and removed everyone except for
> myself as a collection owner (Site Actions > Site Settings > People and
> Groups > Select All > Actions > Delete Users from Site Collection). I
> Rebooted the server for good measure and tried again, but get the same
> error message. The log (below) doesn't return a specific user, list,
> or library associated with the error.
>
> The odd thing is that in some of the collections that I have
> successfully moved over, I can see that the log is enumerating site
> collection user entries of people that are no longer with the company,
> so it appears that it's not the absence of an actual AD account that
> causes the problem.
>
> Anyone out there run into this issue? I've searched, but not turned up
> anything.
>
> Complete log file for failed export:
>
> [12/20/2006 10:55:33 AM]: Start Time: 12/20/2006 10:55:33 AM.
> [12/20/2006 10:55:33 AM]: Progress: Initializing Export.
> [12/20/2006 10:55:33 AM]: Progress: Starting Export.
> [12/20/2006 10:55:33 AM]: Progress: Calculating Objects to Export.
> [12/20/2006 10:55:40 AM]: Progress: Serializing Objects to Disk.
> [12/20/2006 10:55:40 AM]: Progress: Starting to process objects of type
> Site.
> [12/20/2006 10:55:40 AM]: Progress: Finished processing objects of type
> Site.
> [12/20/2006 10:55:40 AM]: Progress: Starting to process objects of type
> Web.
> [12/20/2006 10:55:40 AM]: Progress: Exporting Web
> http://rcasharei01/groups/HR.
> [12/20/2006 10:55:41 AM]: FatalError: User cannot be found.
> at Microsoft.SharePoint.SPUserCollection.GetByID(Int32 id)
> at Microsoft.SharePoint.SPWeb.get_Author()
> at
> Microsoft.SharePoint.Deployment.WebSerializer.GetDataFromObjectModel(Object
> obj, SerializationInfo info, StreamingContext context)
> at
> Microsoft.SharePoint.Deployment.DeploymentSerializationSurrogate.GetObjectData(Object
> obj, SerializationInfo info, StreamingContext context)
> at
> Microsoft.SharePoint.Deployment.XmlFormatter.SerializeObject(Object
> obj, ISerializationSurrogate surrogate, String elementName, Boolean
> bNeedEnvelope)
> at Microsoft.SharePoint.Deployment.XmlFormatter.Serialize(Stream
> serializationStream, Object topLevelObject)
> at
> Microsoft.SharePoint.Deployment.ObjectSerializer.Serialize(DeploymentObject
> deployObject, Stream serializationStream)
> at Microsoft.SharePoint.Deployment.SPExport.SerializeObjects()
> at Microsoft.SharePoint.Deployment.SPExport.Run()
> [12/20/2006 10:55:41 AM]: Progress: Export Completed.
> [12/20/2006 10:55:41 AM]: Finish Time: 12/20/2006 10:55:41 AM.
> [12/20/2006 10:55:41 AM]: Completed with 0 warnings.
> [12/20/2006 10:55:41 AM]: Completed with 1 errors.
>
>
From: Gunther Rohrer on 28 Feb 2007 00:11
Yes, I did get a solution from Microsoft just last week. They worked
on the issue for over a month and it got bounced all over India,
Canada, and Texas. Turns out the the original site owners for each
collection belonged to our old domain. We were acquired by another
company and migrated the system into the new domain. For example, the
original site owner account was qrs\jsmith, but that account had been
removed and replaced by inovis\jsmith,which caused the export to
fail. By adding the old account back into the site collection, the
problem went away.

This is obviously not a great solution, because the removed account
may not be around any longer to add back into the site collection. I
was lucky as most of the sites I could figure out who the original
owner was and add the accounts back in, but in some cases the account
had been deleted (termed user). And I'm note sure if there is a
workaround for this.

 | 
Pages: 1
Prev: IE Error when trying to open Office documents in Sharepoint
Next: Error creating mySite in SharePoint 2007