STSADM Import giving outofmemoryexception
Hi, I'm trying to move few sites in one site collection to a nbrand new site collection. For that I'm trying to export the sites and import into to the new site collection using the below command stsadm -o import -url http://localhost/tower3 -includeusersecurity -updateversions 1 -filename phsr.dat and I'm getting the following error when I try to get a Production copy of the site and import into the Lab Server. Export command I used is <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-alt:"Calisto MT"; mso-font-charset:0; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:-1610611985 1107304683 0 0 159 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-alt:"Times New Roman"; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman";} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {mso-style-noshow:yes; mso-style-priority:99; color:purple; mso-themecolor:followedhyperlink; text-decoration:underline; text-underline:single;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-size:10.0pt; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} -->
stsadm -o export -url http://team.***.com/site1 -filename phsr.bak -includeusersecurity -versions 4
I would appreciate any help on this. [5/5/2009 3:42:48 PM]: Progress: Importing ListItem /Tower3/Lists/ProjectList?id=1100. [5/5/2009 3:44:35 PM]: FatalError: Exception of type 'System.OutOfMemoryException' was thrown. at System.String.GetStringForStringBuilder(String value, Int32 startIndex, Int32 length, Int32 capacity) at System.Text.StringBuilder.GetNewString(String currentString, Int32 requiredLength) at System.Text.StringBuilder.Append(String value) at System.IO.StringWriter.Write(String value) at System.Xml.XmlTextEncoder.Write(String text) at System.Xml.XmlTextWriter.WriteString(String text) at System.Xml.XmlWriter.WriteAttributes(XmlReader reader, Boolean defattr) at System.Xml.XmlWriter.WriteAttributes(XmlReader reader, Boolean defattr) at System.Xml.XmlWriter.WriteNode(XmlReader reader, Boolean defattr) at System.Xml.XmlReader.ReadOuterXml() at Microsoft.SharePoint.Deployment.XmlFormatter.ParseObject(Type objectType, Boolean isChildObject) at Microsoft.SharePoint.Deployment.XmlFormatter.DeserializeObject(Type objectType, Boolean isChildObject, DeploymentObject envelope) at Microsoft.SharePoint.Deployment.XmlFormatter.Deserialize(Stream serializationStream) at Microsoft.SharePoint.Deployment.ObjectSerializer.Deserialize(Stream serializationStream) at Microsoft.SharePoint.Deployment.ImportObjectManager.ProcessObject(XmlReader xmlReader) at Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects() at Microsoft.SharePoint.Deployment.SPImport.Run() Thanks Ramesh
May 6th, 2009 12:00am
Karl/Lu, Thank you your workaround. But, I still get the same error as before. I increased the size of the virtual memory from from 2GB to 6GB. Don't know whether that makes any difference. I also have the sql server on the same dev machine. Any ideas. thanks Ramesh
Free Windows Admin Tool Kit Click here and download it now
May 8th, 2009 7:07pm
I didn't have access to server.....but, the kb article says /3gb is not supported http://support.microsoft.com/kb/933560
May 8th, 2009 9:34pm
Finally, I was able to fix this issue. The issue was with Versioning with a List. A List was enabled for versioning and when a particular user wants to view, the user always click on "Edit" and click on "OK" even if user didn't make any changes to the List Item and for some reason sharepoint creates as a new version. So we have around 10 list items with upto 40000 version and stsadm command tries to load all the version and gives up with outofmemory exception. So, I tried to set the List as no version enabled. It failed with the same error. Sharepoint doesn't remove the older version and just keep the latest version, just like when you enable and disable feature. So, I have to delete the particular item and then export and import which worked without any error. Thanks for the all the help guys. Ramesh
Free Windows Admin Tool Kit Click here and download it now
May 20th, 2009 5:46pm
I realise this is a MOSS forum, but this is a relevant thread. We get this error with a MOSS import into SharePoint 2010. The import file is only 200MB and we are using the "-versions 2" switch":
[10/21/2010 2:17:19 PM] [List] [Decisions] Error: Server Out Of Memory.
There is no memory on the server to run your program. Please contact your administrator with this problem.<nativehr>0x8007000e</nativehr><nativestack></nativestack>
[10/21/2010 2:17:19 PM] [List] [Decisions] Debug: at Microsoft.SharePoint.Library.SPRequestInternalClass.CreateListOnImport(String bstrUrl, Guid& pguidListId, String bstrTitle, String bstrDescription, Int32 lTemplateID, String bstrFeatureId, Guid guidRootFolderId, Int64 llFlags, Int32 iVersion, Int32 iAuthor, String bstrFields, String bstrContentTypes, String bstrImageUrl, String bstrEventSinkAssembly, String bstrEventSinkClass, String bstrEventSinkData, Guid guidDocTemplateId, String bstrViews, String bstrForms, Boolean bCompressedSchema)
at Microsoft.SharePoint.Library.SPRequest.CreateListOnImport(String bstrUrl, Guid& pguidListId, String bstrTitle, String bstrDescription, Int32 lTemplateID, String bstrFeatureId, Guid guidRootFolderId, Int64 llFlags, Int32 iVersion, Int32 iAuthor, String bstrFields, String bstrContentTypes, String bstrImageUrl, String bstrEventSinkAssembly, String bstrEventSinkClass, String bstrEventSinkData, Guid guidDocTemplateId, String bstrViews, String bstrForms, Boolean bCompressedSchema)
at Microsoft.SharePoint.Deployment.ListSerializer.CreateList(SPWeb parentWeb, Dictionary`2 listMetaData, Boolean usingPublicSchema)
at Microsoft.SharePoint.Deployment.ListSerializer.SetObjectData(Object obj, SerializationInfo info, StreamingContext context, ISurrogateSelector selector)
at Microsoft.SharePoint.Deployment.XmlFormatter.CallSetObjectData(Object obj, SerializationInfo objectData, ISerializationSurrogate surrogate, ISurrogateSelector selector)
We then tried a Web Frontend Server with more available RAM instead of the Application Server (and used PowerShell import instead of STSADM) and got the following error:
[21/10/2010 2:34:42 PM] Progress: Importing Role Assignment for {SITE}/{LIST}.
[21/10/2010 2:34:42 PM] FatalError: <nativehr>0x80070003</nativehr><nativestack></nativestack>
[21/10/2010 2:34:42 PM] Debug: at Microsoft.SharePoint.Library.SPRequestInternalClass.UpdateMembers(String bstrUrl, UInt32 dwObjectType, String bstrObjId, Guid& pguidScopeId, Int32 lGroupID, Int32 lGroupOwnerId, Object& pvarArrayAdd, Object& pvarArrayAddIds, Object& pvarArrayLoginsRemove, Object& pvarArrayIdsRemove, Boolean bRemoveFromCurrentScopeOnly, Boolean bSendEmail)
at Microsoft.SharePoint.Library.SPRequest.UpdateMembers(String bstrUrl, UInt32 dwObjectType, String bstrObjId, Guid& pguidScopeId, Int32 lGroupID, Int32 lGroupOwnerId, Object& pvarArrayAdd, Object& pvarArrayAddIds, Object& pvarArrayLoginsRemove, Object& pvarArrayIdsRemove, Boolean bRemoveFromCurrentScopeOnly, Boolean bSendEmail)
at Microsoft.SharePoint.Deployment.RoleAssignmentsImport.ProcessComplexElement(ImportStreamingContext context, XmlReader xr, SqlSession session)
at Microsoft.SharePoint.Deployment.SqlBatchImport.Run()
at Microsoft.SharePoint.Deployment.SecurityObjectSerializer.SetObjectData(Object obj, SerializationInfo info, StreamingContext context, ISurrogateSelector selector)
at Microsoft.SharePoint.Deployment.XmlFormatter.CallSetObjectData(Object obj, SerializationInfo objectData, ISerializationSurrogate surrogate, ISurrogateSelector selector)
at Microsoft.SharePoint.Deployment.XmlFormatter.ParseObjectDirect(Object objParent, Type objectType)
at Microsoft.SharePoint.Deployment.XmlFormatter.DeserializeObject(Type objectType, Boolean isChildObject, DeploymentObject envelope)
at Microsoft.SharePoint.Deployment.XmlFormatter.Deserialize(Stream serializationStream)
at Microsoft.SharePoint.Deployment.ObjectSerializer.Deserialize(Stream serializationStream)
at Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects()
at Microsoft.SharePoint.Deployment.SPImport.Run()
[21/10/2010 2:34:42 PM] Progress: Import did not complete.
So we found the {LIST} in the {SITE} above and made its permissions inherit from its parent. We then re-exported and imported, removed all list-specific permissions when it continued to fail and then finally on the next list that fails
and then finally it worked.
The list itself (and its ACL) is not large, so it's an unusual problem - I wonder if it's a bug when the system attempts to import more than 7 custom roles which it's trying to do here. Just FYI it was still failing even if I specified
"-cabsize 1023" and "-nofilecompression".
October 21st, 2010 10:01am