Insufficient free memory eventid: 3270

[Michael_Librett]

Anyone run into this error ? I have checked that the 16k mapisvc.inf file is located in C:\Windows\System32, ran fixmapi, deleted all the temp Outlook profiles and restarted the server. I continue to get this error:

Thanks in advance

Type:Warning
Event Source:Enterprise Vault
Event Category:Journal Task
Event ID:3270
Date:2/15/2007
Time:12:04:00 PM
User:N/A
Computer:GSMACDQ09ES
Description:
There is not enough free memory available to continue. The Task for GSMACDQ16ES will pause for a while before retrying.

For more information, see Help and Support Center at http://evevent.veritas.com/rosetta/showevent.asp

[Michael_Bilsbor]

Hi,

V7 takes care of all the 'mapi' stuff these days.
Perhaps it's a very large message EV is coming across?

A dtrace may give you an idea of whether it's a repeated item.

[Michael_Librett]

Ran a dtrace which shows that there is not enought memory MAPI error 8007000e.

Here's the dtrace (the error is in the last line):

924988 15:01:57.856 0 CStorageArchive::Create|Creating Saveset2 object.|Requested in memory: TRUE|Creating in memory: TRUE
924989 15:01:57.856 0 CStorageArchive::Create (Exit) |Success |
924990 15:01:57.856 0 :CArchivingAgent::ProcessItem() |Writing the Archive ID of the message to the saveset |
924991 15:01:57.856 0 :CArchivingAgent::ProcessItem() |Writing the retention category of the message to the saveset |
924992 15:01:57.856 0 CArchivingAgent::PI_BuildSaveset - write the message to the saveset
924993 15:01:57.856 0 CMAPISaveset::SaveSharableMessage
924994 15:01:57.856 0 Save Sharable Message as MAPI.
924995 15:01:57.856 0 CSavesetOnIStg::IsSavesetUnicode
924996 15:01:57.856 0 Saveset Version: V1.1
924997 15:01:57.856 0 Unicode: True
924998 15:01:57.856 0 CSavesetOnIStg::IsSavesetUnicode (Exit). hr=Success
924999 15:01:57.856 0 CSavesetOnIStg::IsSavesetUnicode
925000 15:01:57.856 0 Saveset Version: V1.1
925001 15:01:57.856 0 Unicode: True
925002 15:01:57.856 0 CSavesetOnIStg::IsSavesetUnicode (Exit). hr=Success
1036772 15:03:03.606 65750 CMAPISaveset::SaveSharableMessage - failed to insert into the saveset, trying a complex saveset
1036773 15:03:03.606 0 CSavesetOnIStg::IsSavesetUnicode
1036774 15:03:03.606 0 Saveset Version: V1.1
1036775 15:03:03.606 0 Unicode: True
1036776 15:03:03.606 0 CSavesetOnIStg::IsSavesetUnicode (Exit). hr=Success
1052107 15:03:07.794 4188 CMAPISaveset::SaveSharableMessage (Exit). hr=Not enough storage is available to complete this operation.
1052108 15:03:07.794 0 CMAPISaveset2::_Insert _com_error exception. hr=Not enough storage is available to complete this operation.
1052111 15:03:07.794 0 HRXEX fn trace :|Source : .\ArchivingAgent.cpp (CArchivingAgent::PI_BuildSaveset) built Nov 24 22:05:56 2006|Description: Call error 0x8007000e
1052114 15:03:07.794 0 CArchivingAgent::PI_BuildSaveset - exiting function
1052115 15:03:07.794 0 CArchivingAgent::ProcessItemInternal - Call to PI_BuildSaveset Failed RetryCount
1052117 15:03:07.794 0 :CArchivingAgent::ProcessItem() |Exiting routine |
1052118 15:03:07.794 0 CSavesetPersist::ResetStorage LB: 0x8f77858 Stg(LB): 0x8d1d3f8 Stg(doc): 0 File: (null)
1052738 15:03:07.919 125 EV~W Event ID: 3270 There is not enough free memory available to continue. The Task for GSMACDQ16ES will pause for a while before retrying. |

[Michael_Librett]

Forgot to mention that both the EV & Exchange 2003 server were rebooted and the errors continued.

[Steve_Burk]

Anyone ever get a solution for this?  I am running v7.0.  Have run fixmapi and made sure the mapisvc.inf is the same across the board.  Still getting the error.  I have 5 different nodes running archiving and journalling against 2 mailbox servers.  It is happening on any of the nodes against only one of the Exchange servers.  I have applied a Microsoft fix for EXMIME.dll from KB 912068 --http://support.microsoft.com/kb/912068/en-us on the Exchange servers, no luck there either.

[Michael_Bilsbor]

Hi,

1. Remember EV takes care of MAPI type issues ie mapisvc.inf and fixmapi etc. don't need to be run.

It could be that the item was large or corrupt in some way.  Have you look at the message itself?  Have you tried setting archiving threads to 1 and then running against that mailbox?