Successful fax, yet error 32016 in event viewer

[Groundhog]

Hi - a wierd thing is happening with Fax Console in Windows XP Pro SP1a.

I can send a fax successfully, using the TAPI services driver on my BT
speedway (AVM) ISDN adapter, the pop-up tells me (rather triumphantly) its
been sent, and indeed, the fax appears at the receiving end. So far, so
good.

However, in Event Viewer \ Applications, an error code 32016 is reported, as
detailed below. It is almost as though fax console is sending the wrong
message - anybody have any ideas ? Russ ?
The attempt to send the fax failed. The fax transmission was interrupted.
This fax will not be sent, because the maximum number of retries has been
exhausted. Sender: xxxxxxxxxxxx. Billing code: . Sender company: Home.
Sender dept: . Recipient name: xxxx. Recipient number: xxxxxxxxxx. Device
name: AVM ISDN TAPI Services (Cntrl 1).

Note: I have xxxx ed out the sender details, they are reported correctly

 

[Russ Valentine [MVP-Outlook]]

It's a new one on me, but by now nothing with this Fax Service surprises me.
As you know, I know nothing about the hardware end of things, but this fax
service has innumerable unexplained transmission failures with a number of
modems. The people I've spoken with who do know a thing about modem hardware
suspect bad TAPI calls as a likely culprit, and also suspect that the
Windows XP developers and the Fax Developers were not acquainted with one
another when the fax TAPI protocols were developed. So an incorrect error
message would not be unusual given those circumstances. You're still ahead
of most users who get only a failed transmission and no error in Event
viewer.

 

[Groundhog]

Thanks for the reply Russ. "I know nothing about the hardware end of
things" is a bit harsh

There's some wierd messages flying around when the PC's faxing that's for
sure - I'll try an analog modem and a different fax utility and see if I can
narrow it down, but my guess is it's probably a buggy TAPI layer or
something.

FWIW I like fax console/fax service - and unencumbered with the usual
bloatware that accompanies similar apps. Hence I want to get it working
properly

Hog

It's a new one on me, but by now nothing with this Fax Service surprises me.
As you know, I know nothing about the hardware end of things, but this fax
service has innumerable unexplained transmission failures with a number of
modems. The people I've spoken with who do know a thing about modem hardware
suspect bad TAPI calls as a likely culprit, and also suspect that the
Windows XP developers and the Fax Developers were not acquainted with one
another when the fax TAPI protocols were developed. So an incorrect error
message would not be unusual given those circumstances. You're still ahead
of most users who get only a failed transmission and no error in Event
viewer.
--
Russ Valentine
[MVP-Outlook]

Hi - a wierd thing is happening with Fax Console in Windows XP Pro SP1a.

I can send a fax successfully, using the TAPI services driver on my BT
speedway (AVM) ISDN adapter, the pop-up tells me (rather triumphantly) its
been sent, and indeed, the fax appears at the receiving end. So far, so
good.

However, in Event Viewer \ Applications, an error code 32016 is

reported,

as
detailed below. It is almost as though fax console is sending the wrong
message - anybody have any ideas ? Russ ?
The attempt to send the fax failed. The fax transmission was interrupted.
This fax will not be sent, because the maximum number of retries has been
exhausted. Sender: xxxxxxxxxxxx. Billing code: . Sender company: Home.
Sender dept: . Recipient name: xxxx. Recipient number: xxxxxxxxxx. Device
name: AVM ISDN TAPI Services (Cntrl 1).

Note: I have xxxx ed out the sender details, they are reported correctly

 

[Russ Valentine [MVP-Outlook]]

I agree with you. I like this fax service, too. It has the most potential of
any so far. I think the move from total MAPI dependence toward MAPI
"awareness" while using TAPI protocols will make it far more versatile and
less cumbersome. I know this is just a period of transition, but I still
wish it worked better. I can send you some logging protocols that will help
you track what's happening with your transmissions if you like. I'm sure the
fax developers would like the additional information as well. They're a hard
working group who are dedicated to making this product better.
I really don't know beans about hardware. All I've ever asked for is a fax
program that will let me receive EKG's reliably.
--
Russ Valentine
[MVP-Outlook]

Thanks for the reply Russ. "I know nothing about the hardware end of
things" is a bit harsh

There's some wierd messages flying around when the PC's faxing that's for
sure - I'll try an analog modem and a different fax utility and see if I can
narrow it down, but my guess is it's probably a buggy TAPI layer or
something.

FWIW I like fax console/fax service - and unencumbered with the usual
bloatware that accompanies similar apps. Hence I want to get it working
properly

Hog

It's a new one on me, but by now nothing with this Fax Service surprises me.
As you know, I know nothing about the hardware end of things, but this fax
service has innumerable unexplained transmission failures with a number of
modems. The people I've spoken with who do know a thing about modem hardware
suspect bad TAPI calls as a likely culprit, and also suspect that the
Windows XP developers and the Fax Developers were not acquainted with one
another when the fax TAPI protocols were developed. So an incorrect error
message would not be unusual given those circumstances. You're still ahead
of most users who get only a failed transmission and no error in Event
viewer.
--
Russ Valentine
[MVP-Outlook]

Hi - a wierd thing is happening with Fax Console in Windows XP Pro SP1a.

I can send a fax successfully, using the TAPI services driver on my BT
speedway (AVM) ISDN adapter, the pop-up tells me (rather triumphantly) its
been sent, and indeed, the fax appears at the receiving end. So far, so
good.

However, in Event Viewer \ Applications, an error code 32016 is

reported,

as
detailed below. It is almost as though fax console is sending the wrong
message - anybody have any ideas ? Russ ?
The attempt to send the fax failed. The fax transmission was interrupted.
This fax will not be sent, because the maximum number of retries has been
exhausted. Sender: xxxxxxxxxxxx. Billing code: . Sender company: Home.
Sender dept: . Recipient name: xxxx. Recipient number: xxxxxxxxxx. Device
name: AVM ISDN TAPI Services (Cntrl 1).

Note: I have xxxx ed out the sender details, they are reported correctly