Re: Received fax errors after running SFC.exe

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: Received fax errors after running SFC.exe
    ... I strongly suggest you to contact your hardware vendor for ... this is a Microsoft signed driver file. ... register any of these dlls. ...
    (microsoft.public.windows.server.sbs)
  • AVStream : How can I register my own AVStream driver??
    ... I make an AVStream capture driver based on MS avssamp sample software device ... The hardware ID for my hardware is PCI\VEN_1131&DEV_7146. ... I modified it as following, but, I can't register my driver. ...
    (microsoft.public.windowsxp.device_driver.dev)
  • Re: OEM versus Upgrade
    ... "The term "COMPUTER" as used herein shall mean the HARDWARE, ... the HARDWARE is a single computer system, ... Here's the complete EULA: ... Microsoft Windows XP Professional, ...
    (microsoft.public.windowsxp.general)
  • Re: Slow XP
    ... Did you update hardware drivers from the manufacturer when you upgraded OS ... When was the last time you checked your hard disk for problems? ... Microsoft has these suggestions for Protecting your computer from the ... The system restore feature is a new one - first appearing in Windows ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: Win xp oem activation hits me clear as mud!
    ... Microsoft does not sell OEM versions to end-users, ... the HARDWARE is a single computer system, or shall mean the computer system with which the HARDWARE operates, if the HARDWARE is a computer system component. ... Heck, don't take my word for it, here's the whole XP Pro OEM EULA. ... manufacturer of the computer system or ...
    (microsoft.public.windowsxp.general)