Microsoft Fax Console crashing

[Chuck Kahn]

Microsoft Fax Console crashes when I launch it.

Removing it and adding it as a windows component didn't fix anything.

I see there are two versions of it under \WINDOWS\system32

08/29/2002 06:41 AM 130,048 fxsclnt(2).exe
08/04/2004 03:56 AM 143,360 fxsclnt.exe

Here's the pop-up error window:

http://www.post-in-toronto.on.ca/chuck.kahn/hello/246/966/800/Microsoft Fax Console.1.jpg

How do I launch it successfully?

 

[Russ Valentine [MVP-Outlook]]

Perhaps you should start at the beginning. List the steps that produced your
problem. Did Fax ever work successfully? How many times did you install Fax
and how? Is your analog fax modem on the Windows XP HCL list?

 

[Chuck Kahn]

Perhaps you should start at the beginning. List the steps that produced your
problem.

The steps that produced the problem were:

1) Installing a new faxmodem.

2) Double clicking the shortcut to "Fax Console" which points to
%SystemRoot%\system32\FxsClnt.exe /new

3) Watching as this error message pops up:
http://www.post-in-toronto.on.ca/chuck.kahn/hello/246/966/800/Microsoft Fax Console.1.jpg

Actually, I can still poke around in the Fax Console if I move the
error pop up out of the way.

The event viewer reports the following:

Faulting application fxsclnt.exe, version 5.2.2600.2180, faulting
module nl_lsp.dll, version 0.0.0.0, fault address 0x00002170.

Did Fax ever work successfully?

Yes. Last time I used it successfully was 04/21/2004 9:37:17 PM. But
that was another faxmodem.

How many times did you install Fax and how?

Three times. I installed it once, nine months ago. When it didn't
work last week, I re-installed it. When it still didn't work, I
uninstalled and re-installed it.

Every installation was performed through the Windows Components Wizard
utility.

Is your analog fax modem on the Windows XP HCL list?

It is listed as "Compatible with Windows XP" at
http://www.microsoft.com/windows/ca...2&xslt=search&qu=fm56-px&scope=1&btnSearch=Go

 

[Russ Valentine [MVP-Outlook]]

Let me make sure I've got this straight. Your old fax modem worked. But then
you installed a new fax modem and then just launched the Fax program?
The logical sequence (to me at least) would have been to uninstall Fax,
install your new modem and make sure it was working with no conflicts, then
reinstall the Fax Service. I would never expect the Fax Service to detect a
new modem and reconfigure itself automatically.

 

[Chuck Kahn]

Let me make sure I've got this straight. Your old fax modem worked. But then
you installed a new fax modem and then just launched the Fax program?

The old fax modem worked, but it was seven years old, and it didn't
have voice modem capabilities. So I upgraded.

I installed the new fax modem for it's voice capabilities, and as I
use Fax Console infrequently (once every 7-9 months), I never thought
to uninstall it.

The logical sequence (to me at least) would have been to uninstall Fax,
install your new modem and make sure it was working with no conflicts, then
reinstall the Fax Service. I would never expect the Fax Service to detect a
new modem and reconfigure itself automatically.

How do I make sure that the new modem is working with no conflicts? I
can launch Hypterminal and type ATDT followed by a 10-digit number and
the modem dials the number. Does that establish a lack of conflicts?

When I look under the modem's Advanced Port Settings, the COM Port
Number drop down menu has COM8 selected and COM1 through COM7 report
that they are "in use." Is that an indication of a conflict?

I have revised my expections from:

a) expecting fax console to detect a new modem and reconfiguring
itself automatically.

to:

b) expecting fax console to work after being re-installed.

to:

c) expecting fax console to work after being uninstalled and
re-installed.

None of these expectations have been met. I need some new
expectations to work with.

 

[Russ Valentine [MVP-Outlook]]

I would simply make sure your new modem is an analog fax modem with class 1
or 2 fax capabilities, is on the Windows XP HCL list and that it appears in
Device Manager with no conflicts. An IRQ conflict in MSCONFIG may not be
relevant.
Then I would install XP Fax.

 

[Chuck Kahn]

I would simply make sure your new modem is an analog fax modem with class 1
or 2 fax capabilities, is on the Windows XP HCL list and that it appears in
Device Manager with no conflicts. An IRQ conflict in MSCONFIG may not be
relevant.
Then I would install XP Fax.

It is an analog fax modem.

This page http://english.aopen.com.tw/products/modem/fm56-px.htm seems
to indicate class 1 capabilities (is there a better way to determine
this? The log reads AT+FCLASS=? - 0,1,1.0,8).

The modem is on the HCL list (see
http://www.microsoft.com/windows/ca...2&xslt=search&qu=fm56-px&scope=0&btnSearch=Go)
as "Compatible with XP" and the Device Manager reports no conflicts.

I removed the modem from the computer. Then I uninstalled it from
Device Manager as follows:

| Click Start, click Run, type cmd.exe, and then press ENTER.
| Type set devmgr_show_nonpresent_devices=1, and then press ENTER.
| Type Start DEVMGMT.MSC, and then press ENTER.
| Click View, and then click Show Hidden Devices.
| Expand the Modem tree.
| Right-click the dimmed modem, and then click Uninstall.

I went back into XP and uninstalled Fax Services and all other
Fax/Voice/Modem related programs.

I restarted.

I shut down and reinstalled the modem onto my motherboard.

I powered up and installed the drivers for the AOpen FM56-PX modem.
(Windows XP automatically detected and installed drivers as a FM56-PV
modem, so I uninstalled that device before installing the correct
FM56-PX drivers downloaded last week from the Aopen ftp site.)

I ran Hypterterminal and dialed a number to verify that the modem was
working.

I reinstalled Fax Services.

I started Microsoft Fax Console.

It encountered a problem and needs to close. The problem hasn't
changed.

Could it be some corrupt log that Fax Console is choking on?

 

[Russ Valentine [MVP-Outlook]]

See if faxsetup.log tells you anything.

 

[Chuck Kahn]

Could it be some corrupt log that Fax Console is choking on?

I found the Console's logs under:

\Documents and Settings\All Users\Application Data\Microsoft\Windows
NT\MSFax\ActivityLog

There were three files:

| InboxLOG.txt
| OutboxLOG.txt
| schema.ini

In order to delete them, I had to stop the Fax Service. Relaunching
Fax Console after deletion still resulted in "Faulting application
fxsclnt.exe, version 5.2.2600.2180, faulting module nl_lsp.dll,
version 0.0.0.0, fault address 0x00002170."

So corrupt logs aren't the issue.

 

[Chuck Kahn]

It encountered a problem and needs to close. The problem hasn't
changed.

Also interesting: if I stop the Print Spooler service and then launch
the Fax Console, a warning message comes up saying "A connection to
the fax printer cannot be made", to which I click "OK"; then the Fax
Console just sits there, not crashing. Then I relaunch the Print
Spooler service. Still no crash from Fax Console. Then, if I either
exit and relaunch Fax Console, or if I don't exit and select Configure
Fax from the Tools menu, Fax Console crashes with the same "Faulting
application fxsclnt.exe, version 5.2.2600.2180, faulting module
nl_lsp.dll, version 0.0.0.0, fault address 0x00002170."

 

[Chuck Kahn]

The event viewer reports the following:

Faulting application fxsclnt.exe, version 5.2.2600.2180, faulting
module nl_lsp.dll, version 0.0.0.0, fault address 0x00002170.

Uninstalling Net Limiter Beta (where the nl_lsp.dll came from) fixed the problem.

Thanks to RunOrDie of DALnet's #windows95 channel for the advice!

 

[Russ Valentine [MVP-Outlook]]

I wasn't asking about corrupt logs. I was asking you for the contents of
faxsetup.log.

 

[Chuck Kahn]

I wasn't asking about corrupt logs. I was asking you for the contents of
faxsetup.log.

Your faxsetup.log question hadn't reached google groups when I wrote
that.

I can see that there are 12655 lines in my faxsetup.log, the most
recent entry is this:

[09/20/04 08:40:09] [0x1160] [ ] FaxOcmSetupProc (fax - (null))
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] FaxOcmSetup proc called with
function 'OC_CLEANUP'
[09/20/04 08:40:09] [0x1160] [ ] prv_OnCleanup
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] Term Unattended module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
[09/20/04 08:40:09] [0x1160] [ ] Term Service Module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
[09/20/04 08:40:09] [0x1160] [ ] Term Registry Module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
[09/20/04 08:40:09] [0x1160] [ ] Term Print Module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
[09/20/04 08:40:09] [0x1160] [ ] Term MAPI Module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (TRUE)
[09/20/04 08:40:09] [0x1160] [ ] Term File Module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
[09/20/04 08:40:09] [0x1160] [ ] Term Util module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
[09/20/04 08:40:09] [0x1160] [ ] Term State module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
[09/20/04 08:40:09] [0x1160] [ ] fxocDbg_Term
[09/20/04 08:40:09] [0x1160] [ ] {

I don't know how to interpret this.

Anyway, I can launch Fax Console without it crashing, but printing to
fax no longer works (as it did in April) if I make a cover page with
the "Send Fax Wizard." (Back in January, I couldn't queue up more
than 3 fax numbers at a time, so I had to keep re-typing my cover page
info. See "The Fax service print monitor has failed to submit the
fax." <[email protected]> )

Here are the steps I'm going through:

1) Open document in Word.

2) File | Print -- choose the printer named "Fax"; click "OK"

3) "Send Fax Wizard" comes up; click "Next"; under "Recipient
Information" click "Address Book"; entry in Address Book is chosen
with a fax number; click "Next"; skipping the Cover Page for this
exercise, "Next"; on "Schedule" dialog, chose "Now" and "Normal"
priority, "Next"; on "Completing the Send Fax Wizard" dialog, clicked
on "Finish";

4) Then it starts dialing and I click cancel since this is just a
test. If I choose a Cover Page in step 3, dialing does not happen,
and no error message or event viewer item comes up to indicate what
went wrong.

 

[Russ Valentine [MVP-Outlook]]

Each time you post, you post with a different story. I'm having a hard time
keeping track. It appears that the Fax Console is no longer crashing. Is
that right?
If so, and if you can send faxes, then the faxsetup.log is no longer in
play.
Please bring us up to date on what the current problem is and what happened
to the earlier problems.
--
Russ Valentine
[MVP-Outlook]

I wasn't asking about corrupt logs. I was asking you for the contents of
faxsetup.log.

Your faxsetup.log question hadn't reached google groups when I wrote
that.

I can see that there are 12655 lines in my faxsetup.log, the most
recent entry is this:

[09/20/04 08:40:09] [0x1160] [ ] FaxOcmSetupProc (fax - (null))
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] FaxOcmSetup proc called with
function 'OC_CLEANUP'
[09/20/04 08:40:09] [0x1160] [ ] prv_OnCleanup
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] Term Unattended module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
[09/20/04 08:40:09] [0x1160] [ ] Term Service Module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
[09/20/04 08:40:09] [0x1160] [ ] Term Registry Module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
[09/20/04 08:40:09] [0x1160] [ ] Term Print Module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
[09/20/04 08:40:09] [0x1160] [ ] Term MAPI Module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (TRUE)
[09/20/04 08:40:09] [0x1160] [ ] Term File Module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
[09/20/04 08:40:09] [0x1160] [ ] Term Util module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
[09/20/04 08:40:09] [0x1160] [ ] Term State module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
[09/20/04 08:40:09] [0x1160] [ ] fxocDbg_Term
[09/20/04 08:40:09] [0x1160] [ ] {

I don't know how to interpret this.

Anyway, I can launch Fax Console without it crashing, but printing to
fax no longer works (as it did in April) if I make a cover page with
the "Send Fax Wizard." (Back in January, I couldn't queue up more
than 3 fax numbers at a time, so I had to keep re-typing my cover page
info. See "The Fax service print monitor has failed to submit the
fax." <[email protected]> )

Here are the steps I'm going through:

1) Open document in Word.

2) File | Print -- choose the printer named "Fax"; click "OK"

3) "Send Fax Wizard" comes up; click "Next"; under "Recipient
Information" click "Address Book"; entry in Address Book is chosen
with a fax number; click "Next"; skipping the Cover Page for this
exercise, "Next"; on "Schedule" dialog, chose "Now" and "Normal"
priority, "Next"; on "Completing the Send Fax Wizard" dialog, clicked
on "Finish";

4) Then it starts dialing and I click cancel since this is just a
test. If I choose a Cover Page in step 3, dialing does not happen,
and no error message or event viewer item comes up to indicate what
went wrong.

 

[Chuck Kahn]

Each time you post, you post with a different story. I'm having a hard time
keeping track. It appears that the Fax Console is no longer crashing. Is that right?
If so, and if you can send faxes, then the faxsetup.log is no longer in play.
Please bring us up to date on what the current problem is and what happened
to the earlier problems.

Earlier problem of Fax Console crashing was solved by uninstalling Net
Limiter Beta (that's where the offending .dll originated)

New problems:

1) If I select cover page during the Send Fax Wizard, no fax gets
sent.

2) If I select multiple fax recipients during the Send Fax Wizard, no
fax gets sent. (Actually an old problem I've had since my January 4,
2004 post to microsoft.public.windowsxp.print_fax "The Fax service
print monitor has failed to submit the fax.")

The only way a fax gets successfully sent with the Send Fax Wizard is
to send to one recipient with no cover page.

 

[Russ Valentine [MVP-Outlook]]

Never seen anything like it reported.
Are your cover pages in the correct location? Do they open correctly in the
Cover Page editor? The Help files will clue you in on all this.

 

[Guest]

Got the same problem here with a brand new Gateway with SP2 preinstalled.
When I try to install Fax Component get error message 0x8 unable to find some
files and the Fax component install fails. Contacted Gateway. They have
nothing to say on the matter. I guess this one will be on the docket for a
fix at Microsoft on SP 33.

Mike

 

[Russ Valentine [MVP-Outlook]]

Did Gateway at least tell you (or have you been able to figure out on your
own) where the Windows XP installation files are for your system?
When the installation routine is unable to find the necessary installation
files (even when directed to the appropriate i386 Folder) it usually means
that the installation files are compressed or in another location. This is
often the case when the files are pre-copied by a manufacturer on the hard
drive. I suspect this will be an issue Gateway must solve.

 

[Guest]

I figured out a month ago that the Windows XP installation files are on a
seperate D: partition on my hard drive. The only file I see mentioned in the
fax install log is fxsmon.dll. When it is called there is a failure to add a
Printer Monitor and failure to create a printer monitor. Both of these are
fatal errors and shutdown the install. The fxsmon.dll is in my i386
directory, but in a compressed form. I also have noted that there are two
other errors at the beginning of the log, dealing with failure to create
short-cuts.

Gateway has been of no help at all in the matter. They want me to do a
restore back to day one or recovery, and wipe out a month of work on my part.
No deal since I know that will not work. I tried to install Fax the second
day I had the computer and it didn't work. I certainly don't need Fax that
bad anyway.

I guess I have learned my lesson this time. Don't buy any computer that has
anything but the operating system installed and the original CD or DVD to go
with it.

Thanks,
Mike

Did Gateway at least tell you (or have you been able to figure out on your
own) where the Windows XP installation files are for your system?
When the installation routine is unable to find the necessary installation
files (even when directed to the appropriate i386 Folder) it usually means
that the installation files are compressed or in another location. This is
often the case when the files are pre-copied by a manufacturer on the hard
drive. I suspect this will be an issue Gateway must solve.
--
Russ Valentine
[MVP-Outlook]

Got the same problem here with a brand new Gateway with SP2 preinstalled.
When I try to install Fax Component get error message 0x8 unable to find
some
files and the Fax component install fails. Contacted Gateway. They have
nothing to say on the matter. I guess this one will be on the docket for a
fix at Microsoft on SP 33.

Mike

 

[Russ Valentine [MVP-Outlook]]

This is often the case when the files are pre-copied by a manufacturer on
the hard drive. If you do a search for the files that the installation
routine claims are missing (fxsapi.dll and fxcfgwz.dll) you won't find them,
but you will find fxsapi.dl_ and fxcfgwz.dl_. These are compressed DLL files
and will need to be decompressed. Double click on them and you will get a
prompt for the file to use to open them. Click on BROWSE. and select Win32
Cabinet Self-Extractor, which is in the system folder. With any luck it will
uncompress them all and make them visible as DLL files. The install routine
still may not find these files. If so, then you must manually direct the
installation routine to the i386 folder that contains these extracted files.
--
Russ Valentine
[MVP-Outlook]

I figured out a month ago that the Windows XP installation files are on a
seperate D: partition on my hard drive. The only file I see mentioned in
the
fax install log is fxsmon.dll. When it is called there is a failure to add
a
Printer Monitor and failure to create a printer monitor. Both of these are
fatal errors and shutdown the install. The fxsmon.dll is in my i386
directory, but in a compressed form. I also have noted that there are two
other errors at the beginning of the log, dealing with failure to create
short-cuts.

Gateway has been of no help at all in the matter. They want me to do a
restore back to day one or recovery, and wipe out a month of work on my
part.
No deal since I know that will not work. I tried to install Fax the second
day I had the computer and it didn't work. I certainly don't need Fax that
bad anyway.

I guess I have learned my lesson this time. Don't buy any computer that
has
anything but the operating system installed and the original CD or DVD to
go
with it.

Thanks,
Mike

Did Gateway at least tell you (or have you been able to figure out on
your
own) where the Windows XP installation files are for your system?
When the installation routine is unable to find the necessary
installation
files (even when directed to the appropriate i386 Folder) it usually
means
that the installation files are compressed or in another location. This
is
often the case when the files are pre-copied by a manufacturer on the
hard
drive. I suspect this will be an issue Gateway must solve.
--
Russ Valentine
[MVP-Outlook]

Got the same problem here with a brand new Gateway with SP2
preinstalled.
When I try to install Fax Component get error message 0x8 unable to
find
some
files and the Fax component install fails. Contacted Gateway. They have
nothing to say on the matter. I guess this one will be on the docket
for a
fix at Microsoft on SP 33.

Mike


:

Microsoft Fax Console crashes when I launch it.

Removing it and adding it as a windows component didn't fix anything.

I see there are two versions of it under \WINDOWS\system32

08/29/2002 06:41 AM 130,048 fxsclnt(2).exe
08/04/2004 03:56 AM 143,360 fxsclnt.exe

Here's the pop-up error window:

http://www.post-in-toronto.on.ca/chuck.kahn/hello/246/966/800/Microsoft Fax Console.1.jpg

How do I launch it successfully?