x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 13 replies
  • Subscribers 76 subscribers
  • Views 2267 views
  • Users 0 members are here
Browse Forums
Announcements
105
topics
32
replies
General Discussion
6k
topics
18k
replies
MagicalArmchair

[SafeCall Exception]: Out of memory.

Posted By

Hello all,

We have been getting "[SafeCall Exception]: Out of memory." occasionally for the last month, in the afternoon on very busy days. It starts to appear sporadically on the Leads screen when we click 'edit'. The solution is a recycle of the app pool, which clearly that kicks users out, so I'd prefer to avoid this. Memory leak? Any tips tracking this down? Elf logs below.

I have already upped the virtual memory settings on the box.

EurekaLog 6.0.25

Application:
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1.1 Start Date : Tue, 6 Mar 2018 06:54:19 +0000
1.2 Name/Description: w3wp.exe - (IIS Worker Process)
1.3 Version Number : 8.0.9200.16384
1.4 Parameters : -ap "CRMTNG App Pool" -v "v4.0" -l "webengine4.dll" -a \\.\pipe\iisipm64b235b5-a8ee-437a-b6bd-7459769e01ba -h "C:\inetpub\temp\apppools\CRM App Pool\CRM App Pool.config" -w "" -m 0
1.5 Compilation Date: Tue, 27 Jan 2015 10:50:58 +0000
1.6 Up Time : 9 hours, 49 minutes, 19 seconds

Exception:
----------------------------------------------------------
2.1 Date : Tue, 6 Mar 2018 16:43:39 +0000
2.2 Address : 1A0067E7
2.3 Module Name : eware.dll
2.4 Module Version:
2.5 Type : EOutOfMemory
2.6 Message : [SafeCall Exception]: Out of memory.
2.7 ID : EA37
2.8 Count : 1
2.9 Status : New
2.10 Note :

User:
-------------------------------------------------------
3.1 ID : SYSTEM
3.2 Name : Windows User
3.3 Email :
3.4 Company :
3.5 Privileges: SeAssignPrimaryTokenPrivilege - OFF
SeIncreaseQuotaPrivilege - OFF
SeTcbPrivilege - ON
SeBackupPrivilege - OFF
SeRestorePrivilege - OFF
SeDebugPrivilege - ON
SeAuditPrivilege - ON
SeChangeNotifyPrivilege - ON
SeImpersonatePrivilege - ON
SeCreateGlobalPrivilege - ON

Computer:
---------------------------------------------------------------
5.1 Name : CRM
5.2 Total Memory : 16384 Mb
5.3 Free Memory : 9266 Mb
5.4 Total Disk : 129.66 Gb
5.5 Free Disk : 21.66 Gb
5.6 System Up Time: 11 days, 20 hours, 41 minutes, 38 seconds
5.7 Processor : Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz
5.8 Display Mode : 1024 x 768, 32 bit
5.9 Display DPI : 96
5.10 Video Card : (driver - RAM 4 MB)
5.11 Printer :

Parents
  • 0

    That's our pleasure.

    And after Sage CRM 7.3sp3 you'll be able to skip on to Sage CRM 2018 very easily!

  • 0 in reply to Sage CRM

    We are getting these errors again on a 2018 R3 - any suggestions? We are getting them about once a week... 

  • 0 in reply to MagicalArmchair

    And this has started to appear again?  I take it that is was working fine on your install of 2018 R3 but has just recently started to generate the error message.

  • 0 in reply to Sage CRM

    Correct, as we have purchased more users and the system gets busier, it appears to be becoming an issue again. We nightly recycled the app pool, however it’s generally around 4pm in the afternoon the app pool has run out of its space in the 32 bit app pool. If you watch it in perfmon you can see the space gradually get eaten up over the course of the day. Clearly something is leaking memory. 

  • 0 in reply to MagicalArmchair

    Is SQL on the same server? If the server is close to 100% RAM I tend to tell SQL to limit its Max RAM, on a different issue we've found the Sage 200 Classic Integration fails is the server is almost out of RAM so limiting the SQL server seems to have helped in those situations and wonder if this could be the same

  • 0 in reply to Matthew Shaw

    Hello Matthew, SQL is on the server and it is an Azure server with plenty of grunt. The issue is the private bytes maximum that the 32 bit application pool can use, and that is around 2gb. Over the course of the day, you can see this edge up as garbage collection fails to dispose entirely of everything loaded into memory until you reach the 2gb tipping point, at which point CRM gives the "Out of Memory" error and then needs to be recycled.

    A lot of applications handle recycles gracefully - CRM however logs everyone out and rebuilds metadata on first load, so it is painfully apparent when we have to recycle and gives all users 5 minutes of downtime and egg on our faces. 

    Any suggestions? We have made sure we dispose of any ActiveX objects fully and the like. 

Reply
  • 0 in reply to Matthew Shaw

    Hello Matthew, SQL is on the server and it is an Azure server with plenty of grunt. The issue is the private bytes maximum that the 32 bit application pool can use, and that is around 2gb. Over the course of the day, you can see this edge up as garbage collection fails to dispose entirely of everything loaded into memory until you reach the 2gb tipping point, at which point CRM gives the "Out of Memory" error and then needs to be recycled.

    A lot of applications handle recycles gracefully - CRM however logs everyone out and rebuilds metadata on first load, so it is painfully apparent when we have to recycle and gives all users 5 minutes of downtime and egg on our faces. 

    Any suggestions? We have made sure we dispose of any ActiveX objects fully and the like. 

Children
No Data

*Community Hub is the new name for Sage City