Overview

The GFI FaxMaker Fax Server service will not stay running.  Each time you restart it, it will not stay running.  This article provides a possible solution to this issue.  

 

Diagnosis

When reviewing the crash in the Windows Event Logs, it appears like below: 

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Channel>Application</Channel>
<Data>Application: fmserver.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00AB3AB0

 

Solution

Follow the steps below:

• Log into the fax server as the account used for the FaxMaker service accounts.  If you are unsure of which account this is, follow the directions below:
  
  • Right-click Start > select Run > type services.msc > click OK.
  • Locate and right-click the FaxMaker Fax Server service and select properties.
  • Select the Log On tab.
  • Log in as the user listed in this account:
    
    
    
    
• Navigate to the C:\ProgramFiles (x86)\GFI\FaxMaker\out\pending folder.  Verify if there are files in this folder.  
• Remove the files from this location.  Move them to another location so they can be reviewed.  Some of these items could be data that was sent as a fax and should not be deleted.  A new folder on the desktop can be created for this purpose.  
• Once the files are moved, in the services.msc, right-click the FaxMaker Fax Server service and select Start.
• When the service starts, we know one of the files that was in the FaxMaker\out\pending folder was causing an issue with the service starting.  
  • For a list of the file types that can be listed in the FaxMaker\out\pending folder and their purposes see the File Types That Appear in the FaxMaker\Out\Pending Folder article.  This article also provides information on reprocessing the files that were moved in this process. 
  • Microsoft Office documents can fail conversion and occasionally cause this.  The troubleshooting Microsoft office document conversion errors can provide steps to resolve the conversion issue.
    
    
    

 

Confirmation

Verify the service remains running.