Fax queue "hangs"

[Tore Bostrup]

We have an issue where after attempting to send (print to "Fax") a fax to a
line that did either not pick up (or picked up and quickly dropped the
call - not a fax line), the fax queue wound up hanging. I.e. subsequent
attempts at faxing wound up being queued, but no faxes went out, and no
further dialing was attempted.

Deleting the job(s) from the queue did not resolve the issue, neither did
pausing and restarting it. After rebooting the system, the faxing resumed.

Does anyone know why this would happen, or how we can preferably avoid or
alternatively resolve it without rebooting in the future? There is no
guarantee that an incorrect number is specified.

TIA,
Tore.

 

[Loganatr [MSFT]]

Instead of reboot, can you try stopping and restart the fax service alone.

The problem could be in your modem also, can you check if your modem is in
Microsoft Certified Modem list, the link is at
http://www.microsoft.com/windows/ca...ryl2&pgn=01a642fd-2790-420f-90bd-85df6a377206


If yes, please work with Fax MVP- RussValentine,
(e-mail address removed), to turn on T30 debug logs and send them to us.

--
Loganatr [MSFT]
Microsoft Printing, Imaging and Fax Team
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.'

 

[Tore Bostrup]

Thanks,

I have since switched from printing directly to the Fax to using the FAX COM
objects, and have not seen the issue since.

On a side note there seems to be very limited information available about
programmatic access to sending faxes with the Microsoft Windows 2000 Fax
software. I have been looking for samples for monitoring fax jobs with the
FaxGetJob API, but Google only found 5 web hits (2 for Fax SDK, 2 to a
German site with VB declarations, and 1 to an oriental language site) and 3
groups hits, in one of which Raghavendra R of the Microsoft Printing,
Imaging and Fax Team indicates that the API is required in order to
determine the retry status. (I am posting this as a separate issue in a new
thread).

Tore.

Instead of reboot, can you try stopping and restart the fax service alone.

The problem could be in your modem also, can you check if your modem is in
Microsoft Certified Modem list, the link is at
http://www.microsoft.com/windows/ca...ryl2&pgn=01a642fd-2790-420f-90bd-85df6a377206


If yes, please work with Fax MVP- RussValentine,
(e-mail address removed), to turn on T30 debug logs and send them to us.

--
Loganatr [MSFT]
Microsoft Printing, Imaging and Fax Team
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.'

We have an issue where after attempting to send (print to "Fax") a fax to
a
line that did either not pick up (or picked up and quickly dropped the
call - not a fax line), the fax queue wound up hanging. I.e. subsequent
attempts at faxing wound up being queued, but no faxes went out, and no
further dialing was attempted.

Deleting the job(s) from the queue did not resolve the issue, neither did
pausing and restarting it. After rebooting the system, the faxing
resumed.

Does anyone know why this would happen, or how we can preferably avoid or
alternatively resolve it without rebooting in the future? There is no
guarantee that an incorrect number is specified.

TIA,
Tore.