Knowledge Base

Faxes Stuck in Conversion:
Overview and Fix Paths

Use this page as the starting point when faxes stall in conversion. Each symptom points to a different fix path, so the fastest resolution is to match the behavior to the right article before changing anything.

← Back to Knowledge Base
Operations KB-008

Faxes Stuck in Conversion: Overview and Fix Paths

When a fax appears stuck in conversion, the issue is usually one of four patterns: a shared-service path or file reference problem, a single bad source document, a printer or output path issue, or a narrower conversion engine failure covered by a dedicated article. This page helps you identify which branch applies before you go deeper.

Common Patterns
  • Shared-service path or file reference is wrong or missing.
  • One corrupt or oversized document blocks the queue.
  • Printer or output path is unavailable.
  • Conversion engine behavior needs a dedicated fix article.
Choose the Right Fix
01
If the issue is path or file based
Check the shared-service configuration first. If the path, file name, or service account access is wrong, the queue can appear stalled even though the engine is running. This is the right branch when the problem started after a migration or server rebuild.
02
If one bad document blocks the queue
A single large or malformed document can hold up everything behind it. Remove or resubmit the suspect item in a simpler format and see whether conversion resumes.
03
If the printer or output path is blocked
Use the Waiting for Conversion article when the queue is tied to an output printer problem, including the documented case where the printer is out of paper.
04
If the conversion engine itself will not start
Use the registry margins article when the failure is a conversion engine startup problem caused by malformed registry margin values.
05
If Word attachments fail in FCS conversion
Use the FCS conversion article when Microsoft Word attachments remain in In FCS conversion and the cause is the workserver printer driver or PDF module setup.
Related Articles
Start with the symptom, then jump to the specific fix: Registry Margins, Waiting for Conversion, and FCS Conversion Fails. This keeps the KB organized and gives each article a clear search target.
Conversion Overview Troubleshooting Shared Services Waiting for Conversion Registry FCS Conversion
Dealing with a live issue?
We support RightFax incident triage and resolution for enterprise and regulated environments. Engagements scoped based on severity and operational impact.
Start Engagement → View Case Studies