<P>When using Duplicate User Merge, the error "<SPAN lang=EN>OutOfMemoryException Msg=Exception of type System.OutOfMemoryException was thrown." occurs. This may cause server performance to stop, requiring a server reboot. No records are later found to have been merged.</P> <P></P>This happens whether the Duplicate User Merge is run manually or by schedule. <P></P>Log entries for the error occur, such as: <P></P><FONT face="Courier New">Process: aexsvc.exe (6588)<BR>Thread ID: 2936<BR>Module: AltirisNativeHelper.dll<BR>Source: Altiris.NS.Logging.EventLog.FlushReportedEventThreadProc<BR>Description: Exception of type System.OutOfMemoryException was thrown. ( Unhandled exception. Type=System.OutOfMemoryException Msg=Exception of type System.OutOfMemoryException was thrown. Src=<BR>StackTrace=<BR> )</FONT></SPAN>
Required fields are blank in the users table Inv_Global_User_General, such as the Given and Surname fields. When the Duplicate User Merge runs, it finds each iteration of the blank fields as a "match", then repeats for everyone, greatly increasing the "matches" and causing the out of memory issue. <P></P>This can occur if data from Active Directory (Connector rules, etc.) imports of users do not bring in the required fields. The more records that exist like this, the greater the issue and potential for server instability.
<P>Populate the blank fields to ensure that the Duplicate User Merge works correctly and does not result in out of memory errors. This can be done in various ways but may be time consuming, depending on how many records require updating. For example:</P> <UL> <LI>Add the required data in Active Directory and perform a new AD import into the Notification Server.</LI> <LI>Bring in the data using a Connector Import Rule.</LI> <LI>Workaround. Set up a collection of those users with blank fields and then add that as an exclusion to the Duplicate User Merge to bypass them for now, until their data can be entered.</LI></UL><br/><p>