FAXCOMEXLib Operation Failed error on .NET/C# – problems and solutions

You are attempting to build an automated client to send faxes on XP Professional. Sending faxes seems to work from other applications such as Word. Trying to run a VB example throws the error:

80070483, Operation Failed

Deciphering the error code reveals that the error relates to Win32 (the character 7 at the beginning). To get the actual error message, turn the code of the error (the last part, 0x483) into a decimal – 1155.

On the command line, type:

net helpmsg 1155

Expected output:

No application is associated with the specified file for this operation

This means that there is a file association problem. In this case, try to restore the TIFF file association to Windows Picture & Fax Viewer under: Windows Explorer > Folder Options > File Types.

For the full discussion regarding this issue on the PCreview forum, click here.

You are trying to build a Windows application that will send faxes and check if they were sent. To do this, the fax functionality is built using a dedicated Web form.

An Operation Failed error is thrown at this line:

JobID = objFaxDocument.ConnectedSubmit(objFaxServer)

The exact error is as follows:

exc.Message: 'Operation Failed'
exc.Source: 'FaxComEx.FaxDocument.1'

Uninstall the fax service and install it again on Windows Server 2003 (Standard Edition). This solution is partial, because testing the fax functionality manually shows that the fax service is corrupted, however nothing changes on the server.

For the full discussion regarding this issue on the PCreview forum, click here.

For a similar scenario and solution in C#, see the following section.

You are trying to connect to a Windows 2003 fax server from a remote C# fax service, and then send a fax. Similar to the previous scenario, an Operation Failed error is thrown.

The error code is Interop.FaxComExLib with the number: 710D8.

Deciphering the error code reveals that the error relates to Win32 (the character 7 at the beginning). To get the actual error message, turn the code of the error (the last part, 0x10D8) into a decimal – 4312.

On the command line, type:

net helpmsg 4312

Expected output:

The object identifier does not represent a valid object

This error is related to the printer installation on the machine running the fax application. The solution is to install the shared 2003 fax on this machine (installation is the same as installing a network printer).

An additional issue that came up in this scenario is that the Windows service is running on a user account that doesn’t exist, which throws an error like the following:

The API version does not support the current operation

In this case, create the user account and make sure it has admin permissions.

For the specific discussion regarding this issue, click here or see the full discussion. (Both discussions were posted in the PCreview forum).

You are working with XP Pro on a development machine, and have installed the fax service on an SBS 2003 server. Attempting to send faxes automatically using an ASP Web page fails on the SBS 2003 server.

The exact error is as follows:

System.Runtime.InteropServices.COMException (0x800710D8): Operation failed. at FAXCOMEXLib.FaxDocumentClass.ConnectedSubmit(FaxServer pFaxServer) at ASP.faxbooking_aspx.__Renderform1(HtmlTextWriter __w, Control parameterContainer) in C:\inetpub\wwwroot\FaxBooking\FaxBooking.aspx:line 35

The issue seems to be related to either the DLL or IIS, or a permissions problem. However, editing the IIS permissions in the web.config file doesn’t help.

Write an application in Visual C++, run it on the client machine, and send faxes using this client’s user details.

The error code received here is the same as in the previous section. See the solution described in Trying to Connect to Windows Fax Server and Send Faxes Causes Operation Failed Error (C#) above.

For the full discussion regarding this issue on the Visual Basic Developer Center, click here.