none
FAXCOMEXLib Fatal Error in Remote Fax Queue RRS feed

  • General discussion

  • I have written a C# console application that uses FAXCOMEXLib.

    The application reads in a text file and submits it to the fax queue.

    (1) The fax queue is running on Windows 2003 SBS  (ServicePack2) (and is working fine), by manually sending faxes to the Fax Server using the traditional File->Print from a application.

    (2) I've developed a application using Visual Studio 2013 Express C# console app.

    (3) Running the console app on my Windows 8 Enterprise development machine works fine, and submits the document to the fax server on the Windows 2003 server SBS (ServicePack2), and sends successfully

    (4) If I deploy the console app to a Windows 2008 server  (ServicePack2) the following happens;

    • I had to install the fax service on the local machine, even though the fax is being sent via another fax server, otherwise I get the error "Retrieving the COM class factory for component with CLSID {CDA8ACB0-8CF5-4F6C-9BA2-5931D40C8CAE} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).|"

    • The app runs fine, once the fax service is installed on the Windows 2008 server

    • The fax is submitted to the fax queue successfully on the Windows 2003 SBS server, from the app running on the Windows 2008 server

    • I can see the fax status on the Windows 2003 SBS server in the queue as Pending, followed by Dialing and then Transmitting.

    • However after a while, I get a error Fatal error, and the fax doesn't go.  The fax number is fine, and can send a fax using the traditional File-Print (send to fax method), as well as receiving faxes.  

    So the issue isn't with the modem.

    The event log entry is

    Event Type: Warning
    Event Source: Microsoft Fax
    Event Category: Outbound 
    Event ID: 32028
    Date: 14/01/2014
    Time: 15:43:42
    User: N/A
    Computer: FAXSERVER
    Description:
    An error was encountered while sending a fax. The service will attempt to resend the fax. If further transmissions fail, please verify that the phone line, fax sending device, and fax receiving device are working properly. Sender: . Billing code: . Sender company: . Sender dept: . Device name: U.S. Robotics 56K FAX EXT. Job ID: 0x0201cf113f2ab5e7. User name: FAXSERVER\Administrator.
     Please check the activity log for further details of this event.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    How can I over come this issue, because I really don't now what to try next.

    Wednesday, January 15, 2014 8:37 AM

All replies

  • Not a clue what's happening but some explaination and a pointer to check first.

    The reason you have to install the Fax Service on Server 2008 is due to the fact that the API you are calling is not present on the machine until it gets installed which you did by adding the Fax Role.

    I'd start by running the application with administrative privilege.  Either launch the application from a command window that has been opened As Administrator or disable UAC and reboot, then launch the application.


    Alan Morris Windows Printing Team

    Wednesday, January 15, 2014 6:37 PM
    Answerer
  • I ran the application as administrator by right clicking on the EXE file, and selecting "Run As Adminstrator".  But the same problem still exists, the fax leaves the application and is posted to the queue on the Windows 2003 SBS server.  

    I can see the fax status on the Windows 2003 SBS server in the queue as Pending, followed by Dialing and then Transmitting; followed by Fatal Error.

    For your information, the accounts I've logged into on the Windows 2008 server is as administrator.

    What else can I try.  Do you need me to provide any additional information ?


    • Edited by NeilDT Friday, January 17, 2014 10:32 AM
    Wednesday, January 15, 2014 9:02 PM
  • Further to my previous posts, it seems very strange but the test string I was sending in the fax was "Hello World". 

    This string on it's own, appears to be what is causing the problem.  Is there some test code left in the fax service, that would cause a fatal error if the only string content in the fax is "Hello World" ???


    • Edited by NeilDT Thursday, January 23, 2014 12:21 PM
    Thursday, January 23, 2014 9:34 AM