Quantcast
Channel: Symantec Connect - Archiving and eDiscovery - Discussions
Viewing all articles
Browse latest Browse all 3821

3432 errors occurred during the creation of a profile errors?

$
0
0
Oui, j'ai besoin d'une solution

Hello,

We started getting lots of these errors towards the end of our nightly archiving run. This might have started after we moved a lot of mailboxes from Ex2003 to Ex2010 (anti-throttling script has been run) :

 

Event Type: Error

 

Event Source: Enterprise Vault 
Event Category: Archive Task 
Event ID: 3432
Date: 11/04/2013
Time: 03:36:14
User: N/A
Computer: EV-1
Description:
One or more errors occurred during the creation of a profile to connect to an Exchange Server. 
 
Targeted Exchange Server: EX-1
Mailbox: SMTP:SRV-APP-EV@mycompany.com
 
ConfigureMsgService failed with the following errors: 
 
Out of memory error has occurred for the following connection points:
EX-1
dc4
 
This indicates that the maximum number of connections has been consumed on this Enterprise Vault Server.
 
For more information, see Help and Support Center at http://evevent.symantec.com/rosetta/showevent.asp?EvtID=3432
 
 
We using EV904. I've seen another post for EV10  recommends setting the following key to solve the problem:
 
 
1. In Regedit,

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\KVS\Enterprise Vault\Agents.

2. Created a new DWORD Value RemoveEmbeddedAttachments with decimal value of 0.

3. Rebooted the archiving tasks.

www.symantec.com/connect/forums/event-id-3432-both-archiving-and-retrieval-out-memory-error-has-occurred-following-connection

 

In our case, EV is on a 32-bit Windows 2003 cluster, so I presume the key, if applicable, would be in HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Enterprise Vault\Agents  instead.

 
Is this helpful in our case please? If so, Is this key recommended for EV903 as well as EV10 and does it cause any data loss?
 
Thanks,
 
- Alan.
 

Viewing all articles
Browse latest Browse all 3821

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>