| Event Id | 1904 |
| Source | HHCTRL |
| Description | 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://office.microsoft.com/assistance/hfws.aspx?AssetID=HP030760001033&CTT=1&Origin=EC010230021033&QueryID=oPb7PQdxz0&respos 1, http://go.microsoft.com/fwlink?LinkID=45840. |
| Event Information | According to Microsoft: RESOLUTION: The HTML Help ActiveX control (Hhctrl.ocx) runs in a second thread. To work around this issue, you must force Hhctrl.ocx to run in a single thread in Visual Basic. You can do this by calling HtmlHelp with the HH_INITIALIZE command when Visual Basic loads, and by calling HtmlHelp with the HH_UNINITIALIZE command when Visual Basic unloads. To run these commands when Visual Basic starts, create an add-in that automatically loads when you start the IDE. To use this add-in, register HHCTRLAV.dll by using regsvr32. To do this, follow these steps: 1. Click Start, and then click Run. 2. Type regsvr32 c:\HHCtrlAV\HHCtrlAV.dll. 3. Press ENTER. A message informs you that DLLRegisterServer succeeded. You must also set up the add-in to be recognized by Visual Basic, and to be loaded when Visual Basic starts. To do this, add HHCTRLAV.Connect=1 to the end of the Vbaddin.ini file. The Vbaddin.ini file is located in C:\Windows or in C:\WinNT. You can now start Visual Basic. HHCtrlAV is in the list of loaded add-ins. If HHCtrlAV is started when Visual Basic starts (the Load on Startup option is enabled), then you do not receive the access violation in VB5.EXE or VB6.EXE as a result of Hhctrl.ocx. |
| Reference Links | BUG: A Fatal Error Occurs If You Run a Microsoft Visual Basic Application by Using the HtmlHelp API |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.