Wierd thing happening in event viewer tonite- need some help

[Robin]

I have about 40 of these in applications and this is the first time i have
seen this since installing WD

The description for Event ID ( 1904 ) in Source ( HHCTRL ) cannot be found.
The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event:
http://www.microsoft.com/athome/security/spyware/software/isv/default.mspx,
http://go.microsoft.com/fwlink?LinkID=45840.



please help



robnin

 

[Robin]

and I now figured out where this is coming from, because i just tested it on
all 3 computers and same thing is happening.
It is happening when I open the "help" in WD
I cleared Event Viewer- Application- opened WD went to the "help screen"
looked around in there for topics. Closed it and again 50 events for HHCTRL
same error msgs
THIS NEEDS TO BE FIXED ASAP!

Happened on 3 seperate computers running xp pro sp2

robin

 

[Larry Gardner]

Search for hhctrl.ocx on your system under C:\windows

Where found, Open Start Menu | Run, enter regsvr32 "pathname of hhctrl.ocx
file"

 

[robinb]

then do what?
robin

Search for hhctrl.ocx on your system under C:\windows

Where found, Open Start Menu | Run, enter regsvr32 "pathname of hhctrl.ocx
file"

 

[robinb]

ok i did the search and found 7 entries:
these 3 in blue
c:\windows\$ntservicepack uninstall$
c:\windows\$ntuninstall kb890175$
c:\windows\$ntuninstallkb896358$

then in black:
c:\windows system32
c:\windows\servicdepackfiles\136
c:\windows\$hf_mig$\kb890175\sp2Qfe
c:\windows\$hf_mig$\kb896358$

so which one am i doing that to and what does that do?
and show me the exact path please?
thanks
robin

 

[Robin]

ok i did it for c:\windows\system32
I had to do it 2x to get it to hold
explain what that does please and I am assuming there is a bug in WD if it
is happening on 3 computers
robin

 

[Larry Gardner]

Somehow, the registration of HHCTRL was lost in the registry (Windows
operates on these registrations in order to determine what DLL to use when
executing a process).

Most Windows applications are just empty dialog boxes. It's these DLLs that
control what/how things are displayed. When the application opened the help
file, it could not connect up to the HHCTRL because it had know record of
what object it was from the registry stand-point.

The regsvr32, just put this information back in the registry.

This happens from time-to-time, when things are installed and checks are not
made. WD probably had nothing to do with the HHCTRL registration, but it's
help file depended on it. It just happens that any other Help files don't
use it, or WD installation was to update it, and failed.

It's funny, because I just had this happen with Address Books, yesterday.
Address Books worked perfect. But I have an application, named RoboForm,
that I wanted to import the Address Book. Wouldn't work. All the other
systems with RoboForm, worked flawlessly. By useing RegMon and Filemon from
www.sysinternals.com I was able to determine that something was not
operating correctly with C:\Program Files\Common Files\System\wab32.dll.

After I regsvr32 wab32.dll, no problem.

Welcome to Windows.

 

[robinb]

thanks for the explanation
robin

Somehow, the registration of HHCTRL was lost in the registry (Windows
operates on these registrations in order to determine what DLL to use when
executing a process).

Most Windows applications are just empty dialog boxes. It's these DLLs
that control what/how things are displayed. When the application opened
the help file, it could not connect up to the HHCTRL because it had know
record of what object it was from the registry stand-point.

The regsvr32, just put this information back in the registry.

This happens from time-to-time, when things are installed and checks are
not made. WD probably had nothing to do with the HHCTRL registration, but
it's help file depended on it. It just happens that any other Help files
don't use it, or WD installation was to update it, and failed.

It's funny, because I just had this happen with Address Books, yesterday.
Address Books worked perfect. But I have an application, named RoboForm,
that I wanted to import the Address Book. Wouldn't work. All the other
systems with RoboForm, worked flawlessly. By useing RegMon and Filemon
from www.sysinternals.com I was able to determine that something was not
operating correctly with C:\Program Files\Common Files\System\wab32.dll.

After I regsvr32 wab32.dll, no problem.

Welcome to Windows.

 

[Robin]

btw robinb and robin are the same person, i am just posting from different
computers.
robin