Veritas Data Insight 6.1 Administrator's Guide

Exception in method Archive:System.ServiceModel.CommunicationException: The maximum message size quota for incoming messages (65536) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element. ---> System.ServiceModel.QuotaExceededException: The maximum message size quota for incoming messages (65536) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element.

This error can arise when a large number of files are sent for archiving in a single batch. This causes an overflow of the product buffer.

Exception in method GetFileServerShares:System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at http://10.209.108.73/EnterpriseVault/FileSystemArchivingAPI that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: The remote server returned an error: (404) Not Found. 2013-05-07 03:37:51 INFO: #{27} [ArchiveStep.archiveFiles] [ARCHIVE OUT] --- End of inner exception stack trace --- 2013-05-07 03:37:51 INFO: #{27} [ArchiveStep.archiveFiles] [ARCHIVE OUT] at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)

This error occurs when the Enterprise Vault Admin service is down or the Enterprise Vault server is unreachable. For instance, when the disk on the Enterprise Vault server vault store is full, all the Enterprise Vault services are stopped. This could also occur if the name of Enterprise Vault server, protocol, or port are specified incorrectly.

If the AdminService is not down, still this error can arise if the EVFileSvrArcMngr service is not running.

[Exception in method Archive:System.ServiceModel.FaultException'1[www.symantec.com.EnterpriseVault.API.FileSystemArchiving.Data.ExecutionFailedFault]: This request operation sent to net.tcp://evserver1.tulip.matrixad.local:5114/TaskService/10E7B53932AB5754980C95B4591BC72171012f00evserver1 did not receive a reply within the configured timeout (00:30:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client. (Fault Detail is equal to www.symantec.com.EnterpriseVault.API.FileSystemArchiving.Data.ExecutionFailedFault).]

This error occurs when the internal services of the Enterprise Vault times out when you try to archive a batch of files. To resolve this problem, you can consider changing the size of batch to a smaller value. Also you can consider reducing the number of files that are sent in a batch.

Alternatively, you can change the timeout values in the configuration for the Enterprise Vault. To change the timeout value:

Executing Function Archive: Exception in method Archive:System.ServiceModel.FaultException'1[www.symantec.co m.EnterpriseVault.API.FileSystemArchiving.Data.TimeoutFault]: The File System Ar chiving task service failed to start. Check that the File System Archiving task service is enabled in the configuration file, <Enterprise_Vault_installation_fol der>\EvFSAArchivingTask.exe.config. (Fault Detail is equal to www.symantec.com.E nterpriseVault.API.FileSystemArchiving.Data.TimeoutFault).

This error occurs at random.

To resolve this problem, re-run the failed archive operation. If you are an Data Insight administrator user, you can re-run the archive operation from the Settings > Action Status page of the Management Console.See Viewing and managing the status of an operation.

2013-03-21 11:17:27 WARNING: Archive: Got exception while archiving - System.ServiceModel.FaultException'1[www.symantec.com.EnterpriseVault.API.FileSystemArchiving.Data.ServerTemporaryUnavailableFault]: Unable to contact the Enterprise Vault Task Controller service. Check that the service is running. (Fault Detail is equal to www.symantec.com.EnterpriseVault.API.FileSystemArchiving.Data.ServerTemporaryUnavailableFault).

This error occurs when the Enterprise Vault task controller service cannot be reached for some reason.

Exception in method Archive:System.ServiceModel.FaultException'1[www.symantec.com.EnterpriseVault.API.FileSystemArchiving.Data.ExecutionFailedFault]: Internal error occurred. Internal Error : <Error checking if file: \\?\UNC\vnxemc.tulip.matrixad.local\Share4EV\Public Share Copy\Ganesh\di automaation\logs3\DI_Automation\Library\Copy (3) of KeyAction\Action1\SnapShots\ssf35f0.html.z is a placeholder file.> (Fault Detail is equal to www.symantec.com.EnterpriseVault.API.FileSystemArchiving.Data.ExecutionFailedFault)

This error occurs when you attempt to re-archive an already archived file, but the placeholder service on the File System Archiving (FSA) agent is not running.

To resolve this problem, run the placeholder services on the FSA agent and attempt to archive the file again.

[Exception in method Archive:System.Web.Services.Protocols.SoapException: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was ''''00:29:59.9810000''''., at evClient.Program.Archive(FileSystemArchivingService channel)]

This error occurs when you restart the Data Insight services, while Data Insight is still processing an archiving operation.

To resolve this error, make sure that the File System Archiving (FSA) task and Enterprise Vault services are running.