Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

OpsMgr 2007: Backup programs may fail to backup the event log when the 64-bit agent is installed


View products that this article applies to.

Source: Microsoft Support

↑ Back to the top


RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

↑ Back to the top


Symptom

Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:


http://support.microsoft.com/default.aspx?scid=kb;EN-US;322756

VSS aware backup applications may experience a failure of the Event Log Writer.  The exact error will depend on the backup program used

↑ Back to the top


Cause

When the 64-bit System Center Operations Manager 2007 agent is installed on a 64-bit Windows 2003 server, it does not properly identify the full path to the Operations Manager event log in the registry. 


For example, when this happens the registry key below will contain a value of Config\MOMLog.evt:


    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Operations Manager\File


Since the value does not contains the full path to the actual event log file it can cause backup programs (such as Tivoli Storage Manager agent) to fail when backing up the event log.

↑ Back to the top


Resolution

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.


To resolve this issue, manually change the registry value to reflect the correct, full path to the MOMLog.evt file (e.g. C:\windows\system32\Config\MOMLog.evt).



Note If you keep the File key type REG_SZ, you must use the complete, actual full path of the EVT file. Variables such as %systemroot% will not work because they are not expandable, and this may cause problems.

If you want to use environment variables such as %systemroot%, you have to delete the File key and create a new File key of type REG_EXPAND_SZ.  For more information about these key types, click the following article number to view the article in the Microsoft Knowledge Base:
101230 Definition of Registry Value Data Types


↑ Back to the top


DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.


TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

↑ Back to the top


Keywords: kbnoloc, kbrapidpub, kbnomt, kb

↑ Back to the top

Article Info
Article ID : 970219
Revision : 3
Created on : 4/17/2018
Published on : 4/19/2018
Exists online : False
Views : 299