Overview

Learn the steps to troubleshoot issues related to FaxMaker's Attendant service.

Symptoms associated with the Attendant service include:

• Fax lines not initializing in the FaxMaker Monitor
• Unable to log into the web interface
• No Fax Lines in Monitor After Server Renamed
• Service does not auto start after a reboot

Troubleshooting steps

Ensure the attached fax device is active and responsive

Faxes cannot be received or transmitted when lines are not properly initialized, a condition that can be watched using the FaxMaker Monitor.

Refer to the Fax lines not initialized in the FaxMaker Monitor for steps that can be taken to check different device types.

Ensure the Attendant service is started

It's not possible to log into the web interface/monitor if the Attendant service is not running. Check the Windows Services app and start the service if required.

For additional solutions (not necessarily related to the Attendant service), check the Unable to Log into FaxMaker Monitor article.

Ensure the service is set to start automatically

Check the Windows Services app and set the service properties so it starts automatically.

While on it, make sure the other FaxMaker services are also set that way.

Review settings that contain the server name

When a server is cloned or renamed, references to the server name in FaxMaker's settings are not automatically updated. Refer to the No Fax Lines Appear in the FaxMaker Monitor After the Fax Server is Renamed article to confirm the issue and apply the suggested solution.

Check the Attendant service log files

The main log file for the Attendant service is AttendantService.txt. Refer to the article about The Attendant Service Debug Log Files for more information, additional files, and their locations.