Script error in links from Help

  • Thread starter Thread starter Julian Over
  • Start date Start date
J

Julian Over

Whenever I click a link in Windows Help, I get a message
like the following:

Internet Explorer Script Error

An error has occurred in the script on this page.

Line: 592
Char: 9
Error: Object doesn't support this property or method
Code: 0
URL: mk:@MSITStore:C\WINNT\Help\ASR.chm::
/recovery_create_erd.htm

Do you want to continue running scripts on this page?

I have W2000 SP4, MSIE 6, script engine 5.6.

Any ideas, anyone? I cannot find a solution by searching
on the support site.
 
Julian,
Whenever I click a link in Windows Help, I get a message
like the following:

Internet Explorer Script Error
An error has occurred in the script on this page.
[...]
I have W2000 SP4, MSIE 6, script engine 5.6.
Click to expand...

Try unregistering and then re-registering the HTML Help ActiveX
control (hhctrl.ocx). To do this, open a Command Prompt window and
enter the following two commands:

regsvr32 /u <drive>:\winnt\system32\hhctrl.ocx
regsvr32 <drive>:\winnt\system32\hhctrl.ocx
 
Thank you very much, Pete - that did it. Any idea why it
happened? Julian
-----Original Message-----
Julian,
Whenever I click a link in Windows Help, I get a message
like the following:

Internet Explorer Script Error
An error has occurred in the script on this page.
[...]
I have W2000 SP4, MSIE 6, script engine 5.6.
Click to expand...

Try unregistering and then re-registering the HTML Help ActiveX
control (hhctrl.ocx). To do this, open a Command Prompt window and
enter the following two commands:

regsvr32 /u <drive>:\winnt\system32\hhctrl.ocx
regsvr32 <drive>:\winnt\system32\hhctrl.ocx
Click to expand...
 
Julian,
that did it. Any idea why it happened
Click to expand...

There is something in SP4 that breaks the registry entries for the
HTML Help ActiveX control, which is what provides the navigation
features in the help files. The most likely cause of the problem is a
security patch for Internet Explorer, as some of the cumulative
patches for IE that Microsoft released last year are known to cause
similar problems (see http://support.microsoft.com/?kbid=822989).

Anyway, I'm glad you got it fixed.
 
Back
Top