Product and Development Musings

Automatic Debug Logging in FaxMan 4

10. December 2009 05:19

There will be times when you will need to know what's going on behind the scenes with the FaxMan SDK - you've added new features that aren't working quite yet or our technical support staff has requested debug logs to help you troubleshoot issues with sending or receiving faxes.  In an effort to make this as easy as possible, we've introduced automatic debug logging in version 4.6 of our FaxMan SDK.  Developers familiar with our previous versions will no longer have to use the command line "/d" option.

Port specific data is stored in a file for each day and port with the filename in the format Portxx-yyyymmdd.log where xx is the com port number and yyyymmdd is the date.   FaxMan log data is stored in a file in the format, faxman-yyyymmdd.log where yyyymmdd is the date.

These files, by default, are stored for 3 days.  You can change this by modifying the DaysToRetain FaxMan server configuration option (please refer to our documentation on how to modify these settings).  If you want to keep only a single day's worth of logs, for instance, set DaysToRetain equal to 1.

You'll find the logs in the same directory as the FaxMan4.exe file (typically the Windows System32 directory for 32-bit machines).

FaxMan V 4.6 Released

6. August 2009 08:25

V 4.6 of the FaxMan SDK is now available for downloading from the My Products page.

 

This is a maintenance release that includes the following changes:

  • 64 Bit Printer Drivers for Vista, XP and Windows Server 2003 & 2008
  • FaxMan now automically logs all com port activity into trace files which are automatically removed after a user specified interval. This eliminates the need to startup faxman in debug and try to duplicate a faxing issue.
  • Class 1 sending more robust when line issues after dialing, previous versions would error out when receiving an ERROR or Timeout after the initial CONNECT after dialing, now we resend a +FRH=3 when that occurs.
  • AutoDetect automatically sets the proper init string for Hardware flow control for USR modems.
  • Changes were made to the Transmit code to be more robust when data is received when we are sending the page data. In some prior builds we would not properly handle this leading to No Reponse to MPS/EOP or timeout issues.
  • All FaXMan redistributable files are digitally signed
Log in