Start a new topic

System.OutOfMemoryException

Hello - 

When doing imports the past 3 days, we have been getting a new and odd set of Exceptions (see below).  We take the exception file and re-import those that didn't get imported.  About half get imported and the other have throw the same Exceptions.  Finally, on the third try, all rows get imported.  

We wondered if this was a problem on our server, but have reset the server and it is still occurring.  Do you have any suggestions/ideas?  This is extremely time-consuming, so any help you can give will be appreciated.

We are running version 3.3.0.17 of IOM.

Examples from the Exception log:

 

Source row 13 produced Excel error row 2: An exception occurred in the Duplicate Search: Error 5.6: Exception of type 'System.OutOfMemoryException' was thrown. 

Source row 16 produced Excel error row 5: Error 5.6: Exception of type 'System.OutOfMemoryException' was thrown.

Source row 17 produced Excel error row 6: Error 5.2: Exception of type 'System.OutOfMemoryException' was thrown.

Source row 22 produced Excel error row 10: Error calling Omatic service: Exception of type 'System.OutOfMemoryException' was thrown.

Source row 23 produced Excel error row 11: Exception of type 'System.OutOfMemoryException' was thrown. [CImport_Process_02.5]

Source row 26 produced Excel error row 14: Error 2.3: Exception of type 'System.OutOfMemoryException' was thrown.

 

 

Thanks,
Rachel


While we had seen it in versions prior to 3.3.0.17 it was much more prevalent in that version.

Thanks,

John

Thanks for the quick reply.  Out of curiosity, is this an issue associated with 3.3.0.17 (specifically)? I ask because we just upgraded to that version last week; prior to that we never received this exception.

I will work on getting 3.3.1.1 installed.

-Rachel

Hi Rachel,

This has to do with your duplicate search settings returning a large number of results. It can be prevented by adjusting your duplicate criteria to return fewer results, but I would suggest upgrading to the latest version of IOM (3.3.1.1) as this version handles this scenario differently so that you don't receive this error.

Thanks,

John
Login or Signup to post a comment