Problem:
Spitfire is unable to send faxes. The event log includes ‘System.Runtime.InteropServices.COMException (0x80070483): Operation failed.‘
Solution:
This problem is usually caused by the inability to find an application that will ‘print‘ the file to the fax device.
- Run sfATC in console mode.
- Turn on verbose mode.
- Route a document to a fax recipient.
- Observe the name of the file being faxed – it should end in .doc or .htm. Verify support for any other extensions with Spitfire Support.
- STOP sfATC after the error. This should leave the file in the sfATC temp folder for testing.
- On the sfATC, open a command window (START | RUN | CMD).
- Type ASSOC and the file extension (e.g. ASSOC .doc) and observe the result. This indicates if the system has an application associated with the file type, for example:
.doc=Word.Document.8
- Use Windows Explorer to find the temp folder and double click on the file. It should open correctly in the associated application.
- Print the file from the associated application.
- Once any issues performing these steps are resolved, the file should fax successfully.
- Restart the sfATC service.
Additional Comments:
If console mode works but service mode does not, check for domain permission issues. It may be necessary to change the identity used by the sfATC service.See also KBA-01279.Note: This KBA predominately applies to legacy versions of sfPMS only. sfPMS no longer uses Word automation. The concept of using console mode to determine if a problem manifests only when run as a service remains a useful troubleshooting tool.
KBA-01178; Last updated: October 12, 2016 at 13:29 pm;
Keywords: 0x80070483;FAXCOMEXLib FaxDocumentClass ConnectedSubmit