Capture 4.0 FaxEntry: FEtrace.log show Error [3014] in MigrateIn ---[3018] in M

Resolving The Problem

Capture 4.0 FaxEntry: FEtrace.log show Error [3014] in MigrateIn ---[3018] in MigrateIn
Question:
Why my FEtrace.log show these lines of error entries?
Question:
Why my FEtrace.log show these lines of error entries?
02-22-2003 00:05:22 Error [3009] in CreateBatch - Internal Error. Can not find specified Template. FAX_TEMPLATE
02-22-2003 00:05:22 Error [91] in FindOrCreateBatch - Object variable or With block variable not set
02-22-2003 00:05:22 Error [3014] in MigrateIn - New Batch could not be Created.
02-22-2003 00:05:53 Error [3018] in MigrateIn - Can not get folder object from folder name. (TACS:/FAX_INC)

Answer:
One explanation it that this happened when IDMIS was not available (was doing backup, for example) and the FaxEntry was still trying to communicate with the IDMIS thus was logging the reported error . Once FaxEntry loses communication to the IDMIS, it must be restarted.

One way to prevent this error entries from happening in FEtrace.log is to enable FaxEntry Idle waiting time. Once you have enabled the FaxEntry Idle Time, FaxEntry will no longer attempt to communicate to the IDMIS server during the backup time period and it will re-establish a login once the time period expires.

To troubleshoot, check the IDMIS elogs to see when SysAdmin performed the IMS backup (running initfnsw), and make sure FaxEntry idle time is enabled to avoid communication to the IDMIS while backing up.

One fact for example (case 10129468):
Customer system does a initfnsw restart every night at 23:59.
The fact that initfnsw restart at 23:59 explains why FaxEntry was logging the errors reported.

SEE ALSO: RESOLUTION 10000720