Sporadic Fax Monitor

[tjdarth]

Every now and then the Fax monitor opens to receive a fax. It answers the
call and after a minute or two I get the error: An error occurred while
receiving the fax. When this occurs I look in the Archive for all incoming
faxes directory, but do not find any exceptional report? Am I correct in
assuming that this is just one of the shortcomings of Win Fax, or can
something else be done to try to trace this issue for resolution? I am
currently running this product from the win-xp SP2 OS.Thanks in advance . .
.. . Tom Johnson

 

[Russ Valentine [MVP-Outlook]]

You are correct. Windows XP Fax has many shortcomings, not the least of
which is that it won't work with many modems still in common use.
Modem incompatibility is not apparent during installation or the initial
setup. It only becomes apparent when you try to send or receive a fax. The
Fax Service will dial or will answer an incoming fax but then fail with any
of a number of unhelpful error messages such as "Line is busy," "There is no
answer," or "Reception error." There will be nothing in Event Viewer to give
a clue as to where the problem might lie.

These errors have been nearly impossible to track down. To do so requires
enabling both PSS and debug logging of fax transmissions, both of which
require fairly extensive registry changes. For the time being, the best
advice is to attempt to use XP Fax only if you have a modem that is listed
on the Windows XP Hardware Compatibility List and using the latest drivers.
Or, if you're into being a guinea pig, I can send you the logging
instructions.

 

[tjdarth]

Thanks Russ, for the quick educational response. At this time I wish I had a
moment to even breath normally. I am currently embarking on an MCSA
education venture. At the same time when I find a spare moment I am also
trying to learn about j2ee and java. Both of these ventures have to be
scheduled between my regular dialysis treatments every week. I currently
have a U.S. Robotics 56K internal modem which if I remember correctly is on
the Win-XP Hardware compatibility chart. I will hold off on being the guinea
pig for now, but will keep this option in mind in the future. Thanks again .
.. . . . Tom J.

You are correct. Windows XP Fax has many shortcomings, not the least of
which is that it won't work with many modems still in common use.
Modem incompatibility is not apparent during installation or the initial
setup. It only becomes apparent when you try to send or receive a fax. The
Fax Service will dial or will answer an incoming fax but then fail with any
of a number of unhelpful error messages such as "Line is busy," "There is no
answer," or "Reception error." There will be nothing in Event Viewer to give
a clue as to where the problem might lie.

These errors have been nearly impossible to track down. To do so requires
enabling both PSS and debug logging of fax transmissions, both of which
require fairly extensive registry changes. For the time being, the best
advice is to attempt to use XP Fax only if you have a modem that is listed
on the Windows XP Hardware Compatibility List and using the latest drivers.
Or, if you're into being a guinea pig, I can send you the logging
instructions.
--
Russ Valentine
[MVP-Outlook]

Every now and then the Fax monitor opens to receive a fax. It answers the
call and after a minute or two I get the error: An error occurred while
receiving the fax. When this occurs I look in the Archive for all incoming
faxes directory, but do not find any exceptional report? Am I correct in
assuming that this is just one of the shortcomings of Win Fax, or can
something else be done to try to trace this issue for resolution? I am
currently running this product from the win-xp SP2 OS.Thanks in advance

..

.
. . Tom Johnson

 

[Russ Valentine [MVP-Outlook]]

Actually, USR's have been among the most problematic from what I've seen.
Transmission logging is pretty labor intensive, and you have quite enough on
your hands putting up with hemodialysis. Good luck. Hope you can get in line
for a transplant.
--
Russ Valentine
[MVP-Outlook]

Thanks Russ, for the quick educational response. At this time I wish I had a
moment to even breath normally. I am currently embarking on an MCSA
education venture. At the same time when I find a spare moment I am also
trying to learn about j2ee and java. Both of these ventures have to be
scheduled between my regular dialysis treatments every week. I currently
have a U.S. Robotics 56K internal modem which if I remember correctly is on
the Win-XP Hardware compatibility chart. I will hold off on being the guinea
pig for now, but will keep this option in mind in the future. Thanks again ..
. . . . Tom J.

You are correct. Windows XP Fax has many shortcomings, not the least of
which is that it won't work with many modems still in common use.
Modem incompatibility is not apparent during installation or the initial
setup. It only becomes apparent when you try to send or receive a fax. The
Fax Service will dial or will answer an incoming fax but then fail with any
of a number of unhelpful error messages such as "Line is busy," "There

is

no
answer," or "Reception error." There will be nothing in Event Viewer to give
a clue as to where the problem might lie.

These errors have been nearly impossible to track down. To do so requires
enabling both PSS and debug logging of fax transmissions, both of which
require fairly extensive registry changes. For the time being, the best
advice is to attempt to use XP Fax only if you have a modem that is listed
on the Windows XP Hardware Compatibility List and using the latest drivers.
Or, if you're into being a guinea pig, I can send you the logging
instructions.
--
Russ Valentine
[MVP-Outlook]

Every now and then the Fax monitor opens to receive a fax. It answers the
call and after a minute or two I get the error: An error occurred while
receiving the fax. When this occurs I look in the Archive for all incoming
faxes directory, but do not find any exceptional report? Am I correct in
assuming that this is just one of the shortcomings of Win Fax, or can
something else be done to try to trace this issue for resolution? I am
currently running this product from the win-xp SP2 OS.Thanks in

advance

.

 

[tjdarth]

Thanks Russ. Keep the prayers coming. I try to keep involved in different
things during this time frame. You have been a great help. Tom J.

Actually, USR's have been among the most problematic from what I've seen.
Transmission logging is pretty labor intensive, and you have quite enough on
your hands putting up with hemodialysis. Good luck. Hope you can get in line
for a transplant.
--
Russ Valentine
[MVP-Outlook]

Thanks Russ, for the quick educational response. At this time I wish I

had

a
moment to even breath normally. I am currently embarking on an MCSA
education venture. At the same time when I find a spare moment I am also
trying to learn about j2ee and java. Both of these ventures have to be
scheduled between my regular dialysis treatments every week. I currently
have a U.S. Robotics 56K internal modem which if I remember correctly is on
the Win-XP Hardware compatibility chart. I will hold off on being the guinea
pig for now, but will keep this option in mind in the future. Thanks

again

.
. . . . Tom J.
with
any is to
give answers
the

correct

in advance