Repeated Install, Remove/Reboot, Install XP Fax Component

[g45]

Hello, while I bought an eMachine with XP Home Sp2 preloaded in 2006, I only
started using the fax services this year. Through Remove/Install Windows
Components, I installed the component and it works well UNTILL I shutdown for
the day and reboot the next day. The next day the OS says it cannot find a
fax printer. My current work-around is to go back to Remove/Install and
REMOVE the component, reboot, then RE-install the component and reconfigure
the fax. During the RE-install the OS requests the insertion of my
manufacturer's XP disk so that it can search for a DLL in the i386 directory.

Since my purchase of this PC, I have conscientiously installed ALL
recommended XP updates.

What is the problem?

Thx, in advance
g45

 

[Hal Hostetler [MVP P/I]]

You may have Security Database corruption, a common problem experienced by
many who attempt to re-install the Fax service after applying SP2; I've seen
several reports that lead me to think the same thing might happen after SP3
is installed, but the jury is still out on that. In these cases there is
no error message during the installation (distinguishing this from the very
common problem where the installation routine states it cannot find the
necessary files). The installation appears to proceed without error, but
when it is over there is no fax printer listed in Printers & Faxes and any
attempt to send a fax results in the error message "Fax server information
cannot be retrieved. The Fax Wizard will now close." This problem appears to
occur because the security data base is corrupted as documented here:

http://support.microsoft.com/kb/884018/EN-US/
You cannot add a Windows component in Windows XP

This article describes a hotfix users can obtain that might fix the problem
and states that Microsoft does NOT recommend simply running the Esentutl.exe
utility (also referred to in the article, it can repair/rebuild the corrupt
file) to recover from security database corruption.

You can either:

1. Get the hotfix mentioned in the KB article and install it. Microsoft
waives any charges for support calls to get supported hotfixes
listed in Knowledge Base articles.

2. Try this procedure using the Esentutl.exe utility mentioned in the KB
article to fix the bad database file:

http://h10025.www1.hp.com/ewfrf/wc/genericDocument?lc=en&cc=us&docname=c00270202
HP and Compaq Notebook PCs: Unable to Install Windows XP Fax Software

I can report that the Esentutl utility has corrected the problem in a number
of cases, HOWEVER, note that Microsoft recommends against using the utility
and would prefer you try the hotfix.

Hal
--
Hal Hostetler, CPBE -- (e-mail address removed)
Senior Engineer/MIS -- MS MVP-Print/Imaging -- WA7BGX
http://www.kvoa.com -- "When News breaks, we fix it!"
KVOA Television, Tucson, AZ. NBC Channel 4
Live at Hot Licks - www.badnewsbluesband.com

 

[g45]

Thx, Hal, I had read about this security database corruption problem when I
scanned this Newsgroups, but I did not think it applied to me. The SP2 was
pre-installed on the PC when I purchased it in 2006. When I "added" the fax
component, it worked very well for a couple of months. Then, it stop working
well, then it would not work at all after shutdown. You may be right in your
suspicion about SP3. XP appeared to upgrade successfully, i.e., no error
messages, but since the upgrade there are several areas of "changed" activity
with the fax component being one. I shall try the hot fix as you recommend.

I appreciate your help and the Newsgroup's commitment to assisting Windows
end-users.

g45

P.S. I bought a VAIO with Vista Business preloaded. The fax component on
it is starting to exhibit unpredictable behavior. Again, it has been since
updating the system with the recommended changes.

 

[Hal Hostetler [MVP P/I]]

If you've already applied SP3, the hotfix is included and won't install. If
SP3 is the culprit, the only solution I've seen to the problem is to remove
it. If you go this route and it fixes the problem, please let me know so I
have a little more ammo to use the next time I'm able to talk to the
developers.

Hal
--
Hal Hostetler, CPBE -- (e-mail address removed)
Senior Engineer/MIS -- MS MVP-Print/Imaging -- WA7BGX
http://www.kvoa.com -- "When News breaks, we fix it!"
KVOA Television, Tucson, AZ. NBC Channel 4
Live at Hot Licks - www.badnewsbluesband.com

 

[g45]

So far, Hal, your recommendation to remove SP3 is not only working for the
Fax Services Component, I don't get as many "hungapp" error messages or
delayed responses with calls on my commonly used applications, e.g., Excell,
Windows Live, Adobe, etc.

I really appreciate this help.

g45

 

[Hal Hostetler [MVP P/I]]

Thanks for the feedback, I'll be forwarding this to the developers the first
chance I get to see if we can get a handle on it and a fix devised.

Hal
--
Hal Hostetler, CPBE -- (e-mail address removed)
Senior Engineer/MIS -- MS MVP-Print/Imaging -- WA7BGX
http://www.kvoa.com -- "When News breaks, we fix it!"
KVOA Television, Tucson, AZ. NBC Channel 4
Live at Hot Licks - www.badnewsbluesband.com