The following are error codes for the IRMIngestion or IRMRetrieval log file:
Reason:
The DNS server for this domain has failed.
Symptom:
The Iron Mountain web service, or its proxy server, or load-balancing server has probably failed, or been taken down.
Reason:
The Iron Mountain web service did not respond correctly to a request. This could be due to a simple glitch.
Reason:
The server may have failed, or the client may have run out of memory to form up the request.
Reason:
The reason will be shown on the line immediately following the message.
Reason:
The Iron Mountain web service did not respond correctly to a request. This could be due to a simple glitch.
Reason:
The Iron Mountain web service did not respond correctly to a request. This could be due to a simple glitch. The SSL link could not be set up because your server was unable to validate the certificate received from Iron Mountain. This is probably because the certification path is not recognized by your server. It could also be because the certificate has expired or been revoked. To check this, open a browser and point it at the ingestion URL. If a dialog appears warning you that the secure connection could not be established, examine the certificate to determine the cause.
Reason:
The Iron Mountain web service did not respond correctly to a request. This could be due to a simple glitch.
Reason:
The DNS server for this domain has failed.
Reason:
The registry has not been configured correctly. The installation of the Iron Mountain integration package may have failed, or else the registry key has been accidentally deleted.
Reason:
The registry has not been configured correctly. Open the registry editor and add the URL of the Iron Mountain ingestion service.
Reason:
The certificate has not been installed correctly or the registry value may have been misspelled. Consult the IRM integration Guide as to how and where to obtain a certificate; how to register it with Iron Mountain; and how to identify it in the registry.
Reason:
The email is too big to be ingested by Iron Mountain. Remember that an email gets expanded by approx 30% when converted to the TNEF format used by Iron Mountain, so the 75 Mb limit will be exceeded for an email of approx 57 Mb.
Reason:
The Iron Mountain web services server is running but the archiving servers further 'downstream' are not.
Reason:
The necessary components are not installed correctly on your server.
Reason:
A MAPI message failed to be converted into TNEF and wrapped into an Internet message. The actual error is given in the log message.
Reason:
TBD
Reason:
The Iron Mountain web services server is running but the archiving servers further 'downstream' are not.
| Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |