Messages with attachments are no longer being ingested into Archive Manager when using Centera as a storage device for attachments. The error that is seen is similar to this:
FL.1: Exception has been caught - moving file d:\Quest Software\ArchiveManager\Export\\000067d3-acbb-ef7c-8d43-ec47f1f7c56b.xml to error folder.
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Server stack trace:
at EMC.Centera.FPApi.SDK.FPPool_Open8(String inPoolAddress)
at EMC.Centera.SDK.FPPool..ctor(String poolConnectionString)
at Quest.AM.SL2.Centera.CenteraStorageLocation2.Open(String id, String connectionString, FileAccess access)
at Quest.AM.SL2.Core.RemoteStorageLocation2`1.Open(String connectionString, FileAccess access)
at Quest.AM.SL2.Core.RemoteStorageLocation2`1.WriteFromFile(String connectionString, FileAccess access, String path, UserData userData)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Quest.AM.SL2.Core.RemoteStorageLocation2`1.WriteFromFile(String connectionString, FileAccess access, String path, UserData userData)
at Quest.AM.SL
The PEA file that is used to allow Archive Manager to write to Centera is not allowing access as expected.
- Open the dbo.StorageLocation in the ArchiveManager database in SQL Management Studio10.10.10.
- Verify that the only active storage location (default = True) is the one set to use the Centera (StorageType = 2) IP addresses you currently use. This will look similar to: 100.150.x.10, 100.150.x.11?C:\centera\CENTERA.PEA
- verify that the PEA file actually exists in the directory specified on all Archive Manager services servers as well as all Archive Manager web servers
- Download the JCenteraVerify tool
- Enter the IP addresses that are specified in dbo.StorageLocation into the 'Access Node Connectivity Check' box in this tool
- click the Authentication box and browse to the PEA file you use for Archive Manager connectivity and select it
- click the 'Run' button
- If the PEA file works then you should see 'Accessible' written in green beside the IP's
- Below you will also see the capabilities of the PEA file
If you do not see 'Accessible' written in green then you will need to create a new PEA file for the access you require.
Contact EMC support for help with creating a new PEA file
Link to download the JCenteraVerify tool: https://community.emc.com/docs/DOC-2393
Link to Centera support community: https://community.emc.com/community/support/centera
Note: These links are valid at the time of this writing.
