Fax Services Install

[Matt Soukup]

I had Fax Services installed but it did not work correctly. Anything I tried
with the fax printer would give me errors. I went into Add/Remove Windows
Components and removed the Fax Services. I then restarted and tried to add
the Fax Services. The first time it asked me for the CD, so I inserted the
CD and it continues the install and says it was successful. I then went to
my printers to see if it was there and it was. When I tried to open the fax
it gave me an error and then it disappeared. I then went back to the Windows
Components and the Fax Services was not checked, so I checked it and ran the
install again. This time it did not look for the files on the CD but in
"C:\WINDOWS\system32\Setup\I386". I pointed it to the CD's i386 folder and
it continued the install. This time there was not fax printer and the Fax
Services still showed that it was not installed. I copied the i386 CD folder
to the path above and ran the install again. No errors were posted and the
install completed without error, but it still did not work.



I looked at the event log and found an error for Microsoft Fax. This is the
error:

Source: Microsoft Fax

Category: Initialization/Termination

Event ID: 32045

Description:

Fax Service failed to initialize because it could not initialize the TAPI
devices.

Verify that the fax modem was installed and configured correctly. Win32
error code: 31. This error code indicates the cause of the error.



I have installed the latest drivers for my modem and have Symantec WinFax
PRO which has no problem with the modem.



I also have a second PC that is the exact same hardware and Windows Fax
works just fine on it.

 

[Russ Valentine]

I seriously doubt Windows XP Fax would install and function correctly when
you already have WinFax Pro installed. I've never run into anyone who has
even tried it or who thought they needed both programs, but it's hard to
imagine a better recipe for TAPI conflicts.

 

[Matt Soukup]

The other PC I spoke about has both installed. WinFax is working and we have
used it to send faxes. The Windows Fax appears to be working fine. I can
open the console and check the Fax status and it shows that it is working
properly. I have not had a chance to send a fax through it though. The main
reason I am trying this it that we are running Small Business Server 2003
and are looking into using Windows Fax instead of WinFax.

I seriously doubt Windows XP Fax would install and function correctly when
you already have WinFax Pro installed. I've never run into anyone who has
even tried it or who thought they needed both programs, but it's hard to
imagine a better recipe for TAPI conflicts.
--
Russ Valentine
[MVP-Outlook]

I had Fax Services installed but it did not work correctly. Anything I
tried
with the fax printer would give me errors. I went into Add/Remove Windows
Components and removed the Fax Services. I then restarted and tried to
add
the Fax Services. The first time it asked me for the CD, so I inserted
the
CD and it continues the install and says it was successful. I then went
to
my printers to see if it was there and it was. When I tried to open the
fax
it gave me an error and then it disappeared. I then went back to the
Windows
Components and the Fax Services was not checked, so I checked it and ran
the
install again. This time it did not look for the files on the CD but in
"C:\WINDOWS\system32\Setup\I386". I pointed it to the CD's i386 folder
and
it continued the install. This time there was not fax printer and the Fax
Services still showed that it was not installed. I copied the i386 CD
folder
to the path above and ran the install again. No errors were posted and
the
install completed without error, but it still did not work.



I looked at the event log and found an error for Microsoft Fax. This is
the
error:

Source: Microsoft Fax

Category: Initialization/Termination

Event ID: 32045

Description:

Fax Service failed to initialize because it could not initialize the TAPI
devices.

Verify that the fax modem was installed and configured correctly. Win32
error code: 31. This error code indicates the cause of the error.



I have installed the latest drivers for my modem and have Symantec WinFax
PRO which has no problem with the modem.



I also have a second PC that is the exact same hardware and Windows Fax
works just fine on it.

 

[Russ Valentine]

Probably using different modems. Most will not work with both programs
installed because of TAPI conflicts.
--
Russ Valentine
[MVP-Outlook]

The other PC I spoke about has both installed. WinFax is working and we
have used it to send faxes. The Windows Fax appears to be working fine. I
can open the console and check the Fax status and it shows that it is
working properly. I have not had a chance to send a fax through it though.
The main reason I am trying this it that we are running Small Business
Server 2003 and are looking into using Windows Fax instead of WinFax.

I seriously doubt Windows XP Fax would install and function correctly when
you already have WinFax Pro installed. I've never run into anyone who has
even tried it or who thought they needed both programs, but it's hard to
imagine a better recipe for TAPI conflicts.
--
Russ Valentine
[MVP-Outlook]

I had Fax Services installed but it did not work correctly. Anything I
tried
with the fax printer would give me errors. I went into Add/Remove
Windows
Components and removed the Fax Services. I then restarted and tried to
add
the Fax Services. The first time it asked me for the CD, so I inserted
the
CD and it continues the install and says it was successful. I then went
to
my printers to see if it was there and it was. When I tried to open the
fax
it gave me an error and then it disappeared. I then went back to the
Windows
Components and the Fax Services was not checked, so I checked it and ran
the
install again. This time it did not look for the files on the CD but in
"C:\WINDOWS\system32\Setup\I386". I pointed it to the CD's i386 folder
and
it continued the install. This time there was not fax printer and the
Fax
Services still showed that it was not installed. I copied the i386 CD
folder
to the path above and ran the install again. No errors were posted and
the
install completed without error, but it still did not work.



I looked at the event log and found an error for Microsoft Fax. This is
the
error:

Source: Microsoft Fax

Category: Initialization/Termination

Event ID: 32045

Description:

Fax Service failed to initialize because it could not initialize the
TAPI
devices.

Verify that the fax modem was installed and configured correctly. Win32
error code: 31. This error code indicates the cause of the error.



I have installed the latest drivers for my modem and have Symantec
WinFax
PRO which has no problem with the modem.



I also have a second PC that is the exact same hardware and Windows Fax
works just fine on it.

 

[Greg Lirette [MSFT]]

You may want to test with this fix

http://support.microsoft.com/?id=884018



This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Matt Soukup]

I have uninstalled WinFax and it still will not install the Windows Faxing
Services. I also use this modem to dial remote networks and now that I
installed the US Robotics drivers it will not complete the connection to
some of them. Windows will not let me go back to its drives and when I
remove the USR drives it cannot find any windows drivers for it, eventhough
that is what it was using before.

Probably using different modems. Most will not work with both programs
installed because of TAPI conflicts.
--
Russ Valentine
[MVP-Outlook]

The other PC I spoke about has both installed. WinFax is working and we
have used it to send faxes. The Windows Fax appears to be working fine. I
can open the console and check the Fax status and it shows that it is
working properly. I have not had a chance to send a fax through it though.
The main reason I am trying this it that we are running Small Business
Server 2003 and are looking into using Windows Fax instead of WinFax.

I seriously doubt Windows XP Fax would install and function correctly when
you already have WinFax Pro installed. I've never run into anyone who has
even tried it or who thought they needed both programs, but it's hard to
imagine a better recipe for TAPI conflicts.
--
Russ Valentine
[MVP-Outlook]
I had Fax Services installed but it did not work correctly. Anything I
tried
with the fax printer would give me errors. I went into Add/Remove
Windows
Components and removed the Fax Services. I then restarted and tried to
add
the Fax Services. The first time it asked me for the CD, so I inserted
the
CD and it continues the install and says it was successful. I then went
to
my printers to see if it was there and it was. When I tried to open the
fax
it gave me an error and then it disappeared. I then went back to the
Windows
Components and the Fax Services was not checked, so I checked it and ran
the
install again. This time it did not look for the files on the CD but in
"C:\WINDOWS\system32\Setup\I386". I pointed it to the CD's i386 folder
and
it continued the install. This time there was not fax printer and the
Fax
Services still showed that it was not installed. I copied the i386 CD
folder
to the path above and ran the install again. No errors were posted and
the
install completed without error, but it still did not work.



I looked at the event log and found an error for Microsoft Fax. This is
the
error:

Source: Microsoft Fax

Category: Initialization/Termination

Event ID: 32045

Description:

Fax Service failed to initialize because it could not initialize the
TAPI
devices.

Verify that the fax modem was installed and configured correctly. Win32
error code: 31. This error code indicates the cause of the error.



I have installed the latest drivers for my modem and have Symantec
WinFax
PRO which has no problem with the modem.



I also have a second PC that is the exact same hardware and Windows Fax
works just fine on it.

 

[Russ Valentine [MVP-Outlook]]

Unfortunately, Windows XP Fax has proven to be incompatible with many common
modems and drivers, particularly older ones, even if the manufacturers claim
they are "compatible" with Windows XP. Modem incompatibility is not apparent
during installation or the initial setup. It only becomes apparent when you
first 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.

--
Russ Valentine
[MVP-Outlook]

I have uninstalled WinFax and it still will not install the Windows Faxing
Services. I also use this modem to dial remote networks and now that I
installed the US Robotics drivers it will not complete the connection to
some of them. Windows will not let me go back to its drives and when I
remove the USR drives it cannot find any windows drivers for it,
eventhough
that is what it was using before.

Probably using different modems. Most will not work with both programs
installed because of TAPI conflicts.
--
Russ Valentine
[MVP-Outlook]

The other PC I spoke about has both installed. WinFax is working and we
have used it to send faxes. The Windows Fax appears to be working fine. I
can open the console and check the Fax status and it shows that it is
working properly. I have not had a chance to send a fax through it though.
The main reason I am trying this it that we are running Small Business
Server 2003 and are looking into using Windows Fax instead of WinFax.

I seriously doubt Windows XP Fax would install and function correctly when
you already have WinFax Pro installed. I've never run into anyone who has
even tried it or who thought they needed both programs, but it's hard
to
imagine a better recipe for TAPI conflicts.
--
Russ Valentine
[MVP-Outlook]
I had Fax Services installed but it did not work correctly. Anything I
tried
with the fax printer would give me errors. I went into Add/Remove
Windows
Components and removed the Fax Services. I then restarted and tried
to
add
the Fax Services. The first time it asked me for the CD, so I
inserted
the
CD and it continues the install and says it was successful. I then went
to
my printers to see if it was there and it was. When I tried to open the
fax
it gave me an error and then it disappeared. I then went back to the
Windows
Components and the Fax Services was not checked, so I checked it and ran
the
install again. This time it did not look for the files on the CD but in
"C:\WINDOWS\system32\Setup\I386". I pointed it to the CD's i386
folder
and
it continued the install. This time there was not fax printer and the
Fax
Services still showed that it was not installed. I copied the i386 CD
folder
to the path above and ran the install again. No errors were posted
and
the
install completed without error, but it still did not work.



I looked at the event log and found an error for Microsoft Fax. This is
the
error:

Source: Microsoft Fax

Category: Initialization/Termination

Event ID: 32045

Description:

Fax Service failed to initialize because it could not initialize the
TAPI
devices.

Verify that the fax modem was installed and configured correctly. Win32
error code: 31. This error code indicates the cause of the error.



I have installed the latest drivers for my modem and have Symantec
WinFax
PRO which has no problem with the modem.



I also have a second PC that is the exact same hardware and Windows Fax
works just fine on it.