Table of Contents

Search

  1. Preface
  2. Introduction
  3. Pre-Installation Notes
  4. Installation and Configuration
  5. Initial Configuration
  6. Enable Transport Layer Security version 1.3
  7. Customizing Installation Settings
  8. Product Administration
  9. Upgrade Overview
  10. Active-Passive: Backups and Replication
  11. Active-Active: Clustering and Automatic Failover
  12. Uninstalling Managed File Transfer

Informatica Managed File Transfer Installation Guide

Informatica Managed File Transfer Installation Guide

Troubleshooting Errors

Troubleshooting Errors

The following items identify problems that may occur when a Participant attempts to join a cluster:
  1. If you receive an error about product versions not matching, then the Participant is running a different version of
    Managed File Transfer
    than the Coordinator system. All systems in the cluster must be running on the same
    Managed File Transfer
    version.
  2. If you receive an error about the timestamp on the Participant not being within five minutes of the Coordinator system, then you must change the system clock on the Participant system to be in sync with the Coordinator. The time is compared in UTC and ignores time zone differences.
  3. You may receive an error about one of the documents directories not being shared. This can occur when the Coordinator system can access the directory but a Participant cannot. In this case you will need to log in to the Coordinator system and configure the Logs, Packages, WebDocs or Documents directories to ensure they are the accessible for all systems in the cluster.
  4. You may receive an error about how the Participant system shut down because another system is actively using the database. This can occur when the Participant and Coordinator systems cannot connect to each other over the clustering communications channel. It is important that the Coordinator’s IP and port (used for the communications channel) is accessible by the other Participant systems. If that address is blocked by a firewall or other network restrictions, then this system will not be considered as part of the cluster and will be forced to shut down.

0 COMMENTS

We’d like to hear from you!