Re: Received fax errors after running SFC.exe

Nick,

I had a client with those errors and others. I was fighting with their
problem at the same time you were posting (I posted six days earlier). I
have finished my testing.

At first, one of the employees told me they had no problems with their
manual fax machine receiving, but claimed that the problems started only
after the new SBS 2003 R2 server was installed and faxing was switched to
it. It had a USR Courier V.Everything 3CP3453 external modem on it. After
several weeks of trying various things, including modems on the HCL, I
contacted Cantata (formerly Brooktrout) and got a loaner TruFax 200 with
which to test faxing. During testing with that loaner Brooktrout card on my
own server, the owner's wife told me they have a horrible fax line that
doesn't even work when it rains. What were the results? See the following.

Please see this thread "Brooktrout TruFax card questions" for
recommendations on what device to use.

In particular, the results of extensive testing are posted on Thursday,
January 11, 2007 10:37 PM and on Monday, January 15, 2007 6:05 PM.

Also, the following is from a response to another post with subject "Fex
help!! (please!!)" from Thursday, January 18, 2007 9:00 AM.

********************************************************
Something may very well have changed with a Microsoft Update, because I
could fax outbound from my USR Courier external several months ago (around
October) but could not reliably fax out any more until I installed the
Brooktrout card.

They have two cards specifically for Microsoft Shared Fax, and they are
certified by GFi to work with FAXmaker if you need more ponies. They are the
TruFax and the TR1034 boards noted here:
http://www.cantata.com/products/shared_fax/.

If you want the cheaper of the two, it is the TruFax board. Click on this
link http://www.cantata.com/products/part_no._guide/index.cfm for part
numbers, then click on one of the two choices below. Note that the web page
is misleading when it states that a board is "for Europe only" or "for
non-Europe countries only." The "Europe only" boards just mean that they are
RoHS-compliant. The same board can be used in the USA. The webmaster has
been informed but has not changed it yet.

TR1034 for Microsoft Shared Fax RoHS
TruFax for Microsoft Shared Fax RoHS (for Europe only)

The most current part numbers for the TruFax series all start with 999-169,
so just figure out how many ports you want and use the corresponding number.
CALL THEM to make sure you get the right board, since the UK appears to have
slight differences.

GFi FAXmaker http://www.gfi.com/faxmaker/ and supported Brooktrout cards
http://kbase.gfi.com/showarticle.asp?id=KBID001227.

*********************************************************

Also, see "Best fax modem settings to receive from multifunction devices?"
dated Monday, December 18, 2006 11:03 AM.

Did you ever run the hotfix I mentioned here
http://support.microsoft.com/kb/919009/en-us?

My "final answer" to my client...use a Brooktrout TruFax card (or the TR1034
at four times the price). They previously had about an 80% receive failure
rate with their USR modem (and the others I tried). With the TruFax card,
they have had 100% success rate for two weeks, both sending and receiving. I
ordered them their own TruFax 100 Card yesterday. Cantata is letting me keep
the loaner TruFax 200 card that I used for testing.

I, too, could fax fine with my USR Courier V.Everything external modem for a
few months prior to November or December, then outbound crapped out on me. I
could not receive from anyone with a Brother MFC device. Testing with the
Brooktrout card showed 100% success receiving.

Gregg Hill










"Nick" <NoSpam@xxxxxxxxxxx> wrote in message
news:eN152PIQHHA.4376@xxxxxxxxxxxxxxxxxxxxxxx
Hello Inn Jin,

Seperate message regarding ongoing "Unknown fatal Error" "0x0000000C",
eventId: 32092.

""Inn Jin [MSFT]"" <v-innjin@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:$gMvo%237PHHA.3604@xxxxxxxxxxxxxxxxxxxxxxxxx
One thing I want to say, as our hardware drives will change with the
change
of the industry standard, it is not support to use the hardware out of
the
HCL list. I strongly suggest you to contact your hardware vendor for
further troubleshooting.

Inn Jin, I do not understand what you are saying here. The ITU fax
standards (V.27, V.29, V.17, V.34) have not changed since 1994 they are
written in stone. What is this change of industry standard that you keep
refering to?

With regard to the hardware vendor, that is me! Thank you for your
suggestion but this issue is not hardware related.

Further to your suggestion I have now tried a completely different modem
and that suffers from exactly the same error. This replacement modem is
usually in daily use on another site sending and receiving faxes all day
without a problem. It installed using the Microsoft certified driver
which ship with SBS, so again no external drivers are involved.

I have also done some digging regarding the driver file and it appears
that our original modem is using the MdmWHQL0.inf file which came with
SBS, this is a Microsoft signed driver file. The WHQl part of the name I
suggest means Windows Hardware QuaLified! No external drivers involved
purely Microsoft Certified drivers only.

The fax driver files are fxsapi.dll, fxsdrv.dll, fxsres.dll, fxstiff.dll,
fxsui.dll and fxswzrd.dll. You can copy them back, but you may need to
register them.

I still get the error: 'FXS. was loaded, but the DLLRegisterServer entry
point was not found. This file can not be registered' when I try to
register any of these dlls. I have also tried this on another Win2003
machine and get the same error. Are you sure that these files should
register in this way? Could you (or someone else who is watching this
thread) try to see if they register correctly on your server. Is there a
different way that these should be registered?

It is possible that solving the reregistering issue might be these

Searching the Internet I find a number of others have had this "Unknown
fatal Error" "0x0000000C" problem but never solved. Has anyone ever found
a solution to this MSFax bug?

Nick






""Inn Jin [MSFT]"" <v-innjin@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:$gMvo%237PHHA.3604@xxxxxxxxxxxxxxxxxxxxxxxxx
Hi Nick,

Thank you for updating.

One thing I want to say, as our hardware drives will change with the
change
of the industry standard, it is not support to use the hardware out of
the
HCL list. I strongly suggest you to contact your hardware vendor for
further troubleshooting.

After a long time further research, 0x436 occurs because SCM (Service
Control Manager) remembers the image path keys etc and hence accesses the
renamed key.

Let's try the follow steps be re-install it:

1. Delete the file from the %temp% directory.

2. Export and then delete the keys and files below to *.old:

1) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fax

2) HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Fax

3) C:\Program Files\Microsoft Windows Small Business Server\fax

4) The "SBSMIS-FAX.log"file under "C:\Program Files\Microsoft
Integration\Windows Small Business Server 2003\Logs".

5) The "SBSMSI-faxcfg.log"file under "C:\Program Files\Microsoft
Integration\Windows Small Business Server 2003\Logs".

6) The "faxsetup.log"file under "C:\WINDOWS\".

3. Delete the registry keys that were previously renamed to *.old:

1) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fax.old

2) HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Fax.old

3) C:\Program Files\Microsoft Windows Small Business Server\fax.old

4. Access Add/Remove Programs, Add/Remove Windows Components, uncheck
"Fax
Services" to uninstall it.

5. Once it is uninstalled, access Add/Remove Programs to reinstall it.

6. Then, access "Add/Remove Programs again", this time, we will click
"Change/Remove" on the "Windows Small Business Server 2003" item:

1) Click "Next" on the "Microsoft Windows Small Business Server Setup"
page.

2) Click "Next" on the "Windows Configuration" page.

Note: It states that "This will take approximately 30 minutes", it is
referring to the total time it will take in the first SBS component
installation. For the task such as remove a specific component, it will
just take couple of minutes.

3) Now, in the "Component Selection" page, choose "Remove" before the
"Fax
Services" item.

4) Click "Next", and then click "Next" again to confirm "Component
Summary". You will be prompted to insert the SBS 2K3 setup Disc 1.

7. Once the removal process is completed, access "Windows Small Business
Server setup" again in "Add/Remove Programs", proceed to the "Component
Selection" page, and then choose "Install" for the "Fax Services" item.

Then please try re-apply SP1 then test the issue. For your two questions:

1) Why did the T30 logging not work, is there anything else we can do to
make this work in the hope that it might shed some light on the cause of
the problem.

I'm not sure why T30 logging not work, some unknown errors may happen.
However, you don't have to collect T30 log, as the previous log you send
to
me which locate in C:\Windows\System32\LogFiles\Fax folder is just as
same
as T30 log. The T30 log contains some deeply error code which you can not
seen in other log, it can helps developer to track the connection and
isolate issue.

2). Where exactly are the driver files for the fax modems, can I copy
these
back from a previous backup? Remember this setup worked fine for 18 mths
until I ran SFC.exe so if I can restore the relevant file to that time
surely everything should start working again, shouldn't it?

The fax driver files are fxsapi.dll, fxsdrv.dll, fxsres.dll, fxstiff.dll,
fxsui.dll and fxswzrd.dll. You can copy them back, but you may need to
register them.


Thank you for understanding and cooperating.

Have a nice day!

Best regards,

Inn Jin (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the
corresponding
newsgroups so that they can be resolved in an efficient and timely
manner.
You can locate the newsgroup here:

http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check
the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In
doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.





.

Relevant Pages

  • Re: Shared Fax console only shows "1 page" even on multi-page faxes
    ... correct page number while we chang the fax modem for a new one (Brooktrout ... TruFax 200). ... Microsoft Windows Server 2003" sticker on the box. ... Make sure that you fax modem appears on the Windows Hardware ...
    (microsoft.public.windows.server.sbs)
  • Re: Brooktrout TruFax card UPDATE
    ... TruFax card received every one of them when the USR modem would not. ... Here are the results to and from two test clients who have Dell servers ...
    (microsoft.public.windows.server.sbs)
  • Re: Shared Fax console only shows "1 page" even on multi-page faxes
    ... The problem only happened when I replaced the "Designed for Microsoft ... Windows Server 2003" TruFax 100 board. ... correct page number while we chang the fax modem for a new one (Brooktrout ...
    (microsoft.public.windows.server.sbs)
  • Re: Fex help!! (please!!)
    ... but another client whose server uses a 3CP3453 Courier modem works ... I would recommend a Brooktrout TruFax board. ... Brooktrout card. ...
    (microsoft.public.windows.server.sbs)
  • Re: Brooktrout TruFax card questions
    ... Have you done the Microsoft patch and Brooktrout FSP update that I ... Gregg Hill ... the replacement is the 999-169-13 TruFax 200-R PCI MSF card. ... part number under the heading of "TruFax for Microsoft Shared Fax RoHS ...
    (microsoft.public.windows.server.sbs)
Loading