We have an issue with a legacy application in the field. Periodically, faxes stop sending and the terminal needs to be rebooted to restart the process. The application is written in VB6, runs under Windows XP SP3 and we are using SDK V4.6 We have tried a number of different modems without any change in the results.
Below is a portion of a log file that shows the issue.
12:50:07:0515 Opening image: c:\KML Technology Inc\911 Network ACD\Comm Center\FAX204906.FMF
12:50:07:0515 Pages in File: 1
12:50:07:0515 1 Total Pages in FaxID 0
12:50:07:0578 Scheduled Fax (dwID = 43)
12:50:08:0390 Fax on port 6 is Class 1
12:50:08:0593 Fax queued successfully
13:00:47:0203 Opening image: c:\KML Technology Inc\911 Network ACD\Comm Center\FAX844312.FMF
13:00:47:0203 Pages in File: 1
13:00:47:0203 Cover Page: cover2.pg
13:00:47:0203 2 Total Pages in FaxID 0
13:00:47:0234 Scheduled Fax (dwID = 44)
13:00:47:0984 Fax on port 6 is Class 1
13:00:48:0281 Fax queued successfully
13:04:25:0765 Opening image: c:\KML Technology Inc\911 Network ACD\Comm Center\FAX1062734.FMF
13:04:25:0765 Pages in File: 1
13:04:25:0765 Cover Page: cover2.pg
13:04:25:0765 2 Total Pages in FaxID 0
13:04:25:0796 Scheduled Fax (dwID = 45)
13:04:26:0234 Fax on port 6 is Class 1
13:04:26:0453 Fax queued successfully
13:06:36:0843 Opening image: c:\KML Technology Inc\911 Network ACD\Comm Center\FAX1193421.FMF
13:06:36:0843 Pages in File: 1
13:06:36:0843 1 Total Pages in FaxID 0
13:06:36:0843 Scheduled Fax (dwID = 0)
13:08:06:0359 Cancel Requested by Client!
We inserted a timer into our application that is reset whenever a status message is received. If no status update is received in 90 seconds, the application cancels the fax (hence the "Cancel Reqested by Client" message). The log file shows the same information whenever the issue occurs: Scheduled Fax with dwID=0. Once this orrus the user has to reboot the terminal to restart the fax process. I assume the fax service is hung up at this point so restarting the service probably would work. We have tried various combinations of fax size, cover page size, no cover page, but there does not seem to be a pattern.
Any assistence you can give in this matter would be greatly appreciated.
Are you running FaxMan as an EXE or a service ? What OS ?
How often does this issue occur ?
FaxMan is running as an EXE. The OS is Windows XP SP3. The issue is intermittent. It may take a few days (and dozens of faxes) to occur or it may occur right after a reboot (within the first 2 or 3 faxes).
Please check the version on the faxman4.exe you are running and if its not 4.6.1 then download the 4.6.1 release from the My Products page and be sure to update all the exe and faxman4d.dll files on your system as well as the interface ie activeX or .Net assemblies whichever you are using. There was a handle leak issue in 4.6 which may be causing this.
I downloaded V4.6.1. We are in the process of updating the test machines in our lab. I will let you know the results (probably early next week).
This question is closed to new answers.