, focusing on gateway configurations and dial-peer statements. Error Code Definitions Lexmark's Fax Recommendation Chart
explicitly defines 700-series errors as 'Error occurred when sending a frame' and suggests lowering Max Speed.
Technical deep dives and official documentation for XMedius and fax troubleshooting. XMedius/OpenText Support Network & VoIP Config General Fax Standards Official Support & Developer Guides OpenText Knowledge Base xmedius fax error code 700
| Root Cause | Technical Explanation | Key Logger String | | :--- | :--- | :--- | | | The FAXSERVER service runs under a specific Windows Service Account. That account lacks "Write" or "Modify" NTFS permissions on the target UNC path ( \\fileserver\faxes\ ). Frequently seen with DFS Namespace changes. | Access Denied (0x80070005) | | 2. SMTP Relay / MAPI Corruption | The SMTP smart host rejected the email due to attachment size, recipient unknown, or TLS mismatch. In MAPI mode, the Outlook profile is corrupted or the Exchange mailbox is over quota. | 550 5.2.3 Storage quota exceeded | | 3. Bar Code / OCR Failure | The routing rule uses "First Page Pattern Matching." The resolution of the inbound fax was too low (Fine vs. Superfine), or the bar code was smudged. The router cannot find a key, so it throws 700 (No valid route). | Failed to extract route pattern | | 4. Database Deadlock (SQL backend) | The XMedius database (SQL Server) is under load. When the server tries to log the inbound fax and fetch the routing rule, the SQL transaction times out. | Timeout expired (0x80040e31) | | 5. Corrupt TIFF Structure | The remote machine sent a malformed Page 0 (header). XMedius saves it, but the internal image conversion module (for thumbnail generation or PDF conversion) crashes, aborting the routing pipeline. | ImageMagick exception: Improper image header | | 6. SMTP Attachment Size Limit | The fax is 50 pages. The resulting PDF is 45MB. The XMedius MaxMessageSize registry key or the SMTP server’s maxSize attribute is lower than that. The email is generated but deleted before sending. | Message exceeds fixed maximum size | | 7. DNS/NetBIOS Resolution Lag | The XMedius server resolves the destination folder hostname via DNS. If the DNS TTL expired or the network has a WINS/NetBIOS mismatch, the route resolves during the call, but fails post-call. | The network path was not found (0x80070035) |
Here are the primary culprits behind this error: XMedius/OpenText Support Network & VoIP Config General Fax
You cannot fix what you cannot see. Follow this structured diagnostic approach.
A 50-user legal practice using XMediusFAX 9.0 over a BroadSoft SIP trunk. They failed 15% of outbound faxes to government agencies with Error 700 . | Access Denied (0x80070005) | | 2
For FoIP to work, both the sender and the receiver (and every gateway in between) must agree on the codec (coder-decoder) used to transmit the data. If the XMedius server is configured to enforce G.711 (pass-through) but the network gateway is strictly set to T.38, the negotiation can collapse, resulting in a 700 error.
T.30 trace showed: Send DCN → Recv CRP → Send DCN → Recv ??? → Code 700 . The XMedius was trying to disconnect, but the remote fax kept asking to repeat commands. Further analysis revealed the SIP trunk was using G.711 fallback instead of T.38.
Alert when EventID 700 occurs >3 times within 60 minutes for the same SenderCSID .
The router thread may wake up 50ms before the FaxReceive thread has fully flushed the TIFF file from memory to disk. The router tries to read a file that is still locked. The result: Code 700.