Article ID: 961270 - Last Review: January 12, 2009 - Revision: 1.1 A custom event is logged incorrectly when you run a 32-bit application in a 64-bit version of Windows Server 2008 or of Windows Vista
SYMPTOMSOn a computer that is running a 64-bit version of Windows Server 2008 or of Windows Vista, you run a 32-bit application that logs a custom event. When you try to view this event in Event Viewer, you notice that the event is logged incorrectly. For example, Event Viewer displays a message that states the following:This problem does not occur on 64-bit versions of Windows Server 2003 or of Windows XP. CAUSEThis problem occurs when you register the DLLs that contain the custom event information in the registry by using a path that contains the following string: %SystemRoot%\System32 In 64-bit versions of Windows Server 2008 and of Windows Vista, DLLs that are installed by 32-bit applications are put in the following folder:%SystemRoot%\SysWOW64 Even if you specify the System32 folder when you install a DLL, Windows redirects the System32 folder to the SysWOW64 folder. However, this is not the case for the registry. If you register a DLL in the registry by using a path that contains the %SystemRoot%\System32 string, Windows does not redirect the registration to the SysWOW64 folder. When the 64-bit Event Log service tries to locate the DLLs to retrieve the event information, the Event Log service still uses the System32 folder instead of the SysWOW64 folder. Because the System32 folder does not contain the DLLs, the Event Log service cannot retrieve the event information.RESOLUTIONA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix. To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page. PrerequisitesTo apply this hotfix, you must be running Windows Server 2008 or Windows Vista Service Pack 1.Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Windows Server 2008 and Windows Vista notesThe .manifest files and the .mum files that are installed in each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.Windows Server 2008, x64-based versions; and Windows Vista with Service Pack 1, x64-based versionsCollapse this table
Windows Server 2008, Itanium-based versionsCollapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATION
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
- 824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
Additional file information for Windows Server 2008 and for Windows VistaAdditional files for all supported x64-based versions of Windows Windows Server 2008 and of Windows VistaCollapse this table
Additional files for all supported Itanium-based versions of Windows Server 2008Collapse this table
REFERENCESFor more information about the Event Log service in Windows, visit the following Microsoft TechNet Web site: http://technet.microsoft.com/en-us/library/cc775047.aspx
(http://technet.microsoft.com/en-us/library/cc775047.aspx)
APPLIES TO
| Article Translations
|
Back to the top
