What to do if a LinkFixer Advanced process aborts in OpenText?

What to do if a LinkFixer Advanced process aborts in OpenText?

What to do if a LinkFixer Advanced process aborts in OpenText?

Modified on: Wed, 18 Mar, 2026 at 3:01 PM

It is highly unlikely for LinkFixer Advanced to abort a process (such as Scan, Inoculate & Cure, Modify Links, or Move/Rename) when working with OpenText. These processes have been extensively tested and validated through client use.
However, if a process does abort, follow the checklist below to identify and resolve the issue.

Troubleshooting Checklist

1. Verify System Requirements
Ensure the machine running LinkFixer Advanced meets the official system requirements
2. Check Network Configuration
Remove any load balancer between LinkFixer Advanced and the OpenText server
3. Enable Required Settings
Enable the MIME setting in LinkFixer Advanced

Test Environment Setup

To safely diagnose the issue:
  1. Create a test OpenText environment that mirrors your production setup (including files and configuration)
  1. Set LinkFixer Advanced logging to Detailed
  1. Set the OpenText environment logging level to Debug (coordinate with your OpenText administrator

Security Considerations

Temporarily disable antivirus or security software on both:
  1. The LinkFixer Advanced machine
  1. The OpenText server

Reproduce the Issue

1. Run the same process in the test environment using a smaller dataset (approximately 100 GB)
2. If the process completes successfully, increase the dataset (up to ~400 GB or less)
3. The goal is to capture sufficient diagnostic data in the logs

If the Process Still Aborts

Collect and submit the following logs for analysis:
  1. LinkFixer Advanced logs
  1. OpenText logs
  1. Windows Event Viewer logs
You can then submit these logs by creating a support ticket within LinkFixer Advanced.