Article ID: 961099 - Last Review: February 6, 2009 - Revision: 3.0 An application that uses Windows NT security event log APIs cannot read the description of an event log message from a computer that is running Windows Vista or Windows Server 2008
On This PageSYMPTOMSAssume that you have an application that uses Microsoft Windows NT security event log APIs. However, on a computer that is running Windows Vista or Windows Server 2008, the application cannot read the description of an event log message. For example, in a network environment, you run Microsoft Operations Manager (MOM) 2005. When the MOM agent is running on a client that is running Windows Vista or Windows Server 2008, the MOM agent cannot read the descriptions of the events in the Windows NT event log. For example, the MOM agent cannot read the following messages. Example 1Example 2In these examples, the Description section is not displayed correctly. Note When the MOM agent runs under the Network Service Account, you must grant the Read permission to the following registry entry on the client computer to make sure that MOM agent has permission to read the registry key for the Security log: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Eventlog\Security However, even if you grant the Read permission to the MOM agent for the entry, the description is not displayed correctly.CAUSEThis issue occurs because in Windows Vista and in Windows Server 2008, the Adtschema.dll component does not have a string table that maps an event ID to the corresponding message description. Therefore, the legacy API cannot format the event description. RESOLUTIONA hotfix is available to resolve this issue. Install this hotfix on the computer that is running Windows Vista or Windows Server 2008. Hotfix information for Windows Vista and for Windows Server 2008A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might 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.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.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 have Windows Server 2008 or Windows Vista Service Pack 1 (SP1) installed.Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other previously released hotfixes.Registry informationTo use this hotfix, you do not have to make any changes to the registry.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.For all supported x86-based versions of Windows Server 2008 and of Windows VistaCollapse this table
For all supported x64-based versions of Windows Server 2008 and of Windows VistaCollapse this table
For all supported Itanium-based versions of Windows Server 2008Collapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor more information about Windows events, visit the following Microsoft Web sites: http://msdn.microsoft.com/en-us/library/aa964766(VS.85).aspx
(http://msdn.microsoft.com/en-us/library/aa964766(VS.85).aspx)
http://msdn.microsoft.com/en-us/library/aa385780.aspx
(http://msdn.microsoft.com/en-us/library/aa385780.aspx)
For more information, 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 Vista and for Windows Server 2008Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008Collapse this table
Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008Collapse this table
Additional files for all supported Itanium-based versions of Windows Server 2008Collapse this table
APPLIES TO
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Back to the top
|
