KB‎ > ‎

Error: System.OutOfMemoryException in Application Event Log when Cloning

Ref: 201107291546 
Last Edited: March 5th, 2013
Defect Id: 2618024
 
 
Description:
A cloning task has seemingly completed: the task has been deleted from the Queue folder. When inspecting the Application Event Log, an error is recorded.
 
Event Type: Warning
Event Source: ImprovementWorkbenchServer
Event Category: None
Event ID: 0
Date:  25/07/2011
Time:  15:19:05
User:  N/A
Computer: MyServer
Description:
Failed task: ProcessLibrary_Live_CLONE_LIBRARY#ProcessLibrary#NewLibrary#ProcessLibraries
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at Microsoft.VisualBasic.Strings.Replace(String Expression, String Find, String Replacement, Int32 Start, Int32 Count, CompareMethod Compare)
   at ImprovementWorkbenchServer.clsMain.ProcessDirectory(DirectoryInfo objDirInfo, String strOld, String strNew, String strFilter)
   at ImprovementWorkbenchServer.clsMain.ProcessDirectory(DirectoryInfo objDirInfo, String strOld, String strNew, String strFilter)
   at ImprovementWorkbenchServer.clsMain.ProcessDirectory(DirectoryInfo objDirInfo, String strOld, String strNew, String strFilter)
   at ImprovementWorkbenchServer.clsMain.ReplaceText(String strPath, String strOld, String strNew, String strFilter)
   at ImprovementWorkbenchServer.clsMain.UpdateWebServerFilesForLibrary(String strOldLibrary, String strNewLibrary, String strRoot)
   at ImprovementWorkbenchServer.clsMain.UpdateFilesForCloneLibrary(String strOldLibrary, String strNewLibrary, String strConfigRoot, String strContainer)
   at ImprovementWorkbenchServer.clsMain.ProcessTask(FileInfo objTask, String strQueueFolder)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
 
Aspects of the cloning procedure may not be complete.
 
 
Cause:
Out of Memory exceptions are rare, and have only been encountered on systems which have a large Catalogue.xml file, and possibly Hierarchy.xml file.
It has also been found to be at least partly system-dependent: a Catalogue that causes an error on one system can be processed successfully on another.
 
 
Workaround:
Retry cloning, but first move the Catalogue and Hierarchy XML files out of the source library so that they are not copied to the new clone and processed. They can be restored when cloning is complete.
The Catalogue and Hierarchy XML files will be found in these locations:
Triaster\ProcessLibraries\<LibraryName>\
  Live\Tools\
  Prelive\Tools\
  Sandpit\Tools\
 
 A Catalogue and Hierarchy will be created when the new library's sites are published, so needn't be created as part of cloning.
 
 
Applies to:
  • Triaster Server 9.x, Triaster Server 10.x    Fixed in Triaster Server 12.4
     
Comments