Users get Exception of type System.OutOfMemoryException

Two users get the error Exception of type ‘System.OutOfMemoryException’ was thrown and Epicor closes on them.

They usually only have 4 Epicor programs open along with Outlook, the Call Center Agent Client, and a web browser. They have 8GB RAM on their workstations.

These are the only two users that see this.

Any ideas of what to look for?

any dashboards running for them? I’ve seen it when trying to put a ton of data from a dashboard.

No, they don’t use any dashboards.

~;)Karen

If there are customization’s on the forms they are using in which objects are not properly disposed of this would cause memory leaks, thus eventually causing the OutOfMemoryException.

  1. Have your users noticed any patterns in this behavior? Are they printing a Crystal report or clicking refresh on a dashboard? <-- lots of data could cause it at that point and replacing the epicor.exe reference in these user’s shortcuts for Epicor on the target line with epicor64.exe could be helpful (or prolong how long it takes to reach the out of memory condition).
  2. Are they on the financial-ly side of the fence? <-- Posting Engine Logging could cause it at that point
  3. Have your users log into the Epicor client.
    Notice the private memory usage of the epicor.exe/epicor64.exe in the Windows task manager.
    Ask them to launch the forms they are in every day.
    Close all screens within Epicor so that only the Epicor main menu is open.
    Notice the private memory usage of the epicor.exe/epicor64.exe in the Windows task manager.
    If memory is higher the second time than the first, it could be a UI Customization issue.

The Windows message that announces the issue (at least as of Windows 7) also gave information about a Windows system setting that would allow users to run with an increased resource limit. It isn’t a cure-all but an upward adjustment of the threshold beyond which the error will be seen. The change requires a system restart, and you have to have admin privileges to do it. Letting users run with admin privileges that in that environment we did not want to do, so the change went un-made in our case.

Have you tried enabling ‘Network Compression’ in the user accounts?