Duplicate Physical and Logical Disk nodes are created during discovery. (NETIQKB72041)

  • 7772041
  • 19-Jan-2010
  • 02-Mar-2010

Environment

AppManager 7.0.x Management Service

Situation

Duplicate Physical and Logical Disk nodes are created during discovery.


If you discover virtual server and cluster resources such as physical and logical disks in an active node, delete a physical disk object from the Operator Console, fail the resources over to another active node, and run the Discovery_NT Knowledge Script on the virtual server, the Operator Console tree view displays new and duplicated physical and logical objects

Resolution

Hotfix 72041 for the AppManager Management Server resolves specific issues. We assume you are familiar with previous versions of AppManager.  The Hotfix package can be downloaded from here .

This hotfix supersedes Hotfixes 71471, 71362, 71352, 71253, and 71243. For more information about the issues resolved in these hotfixes, see Previous Releases (in the Notes section of this KS, below).

You can post feedback in the AppManager forum on Qmunity, our community Web site that also includes product notifications, blogs, and the AppManager user group.


Why Install This Hotfix?

This hotfix resolves an issue with virtual server and cluster resources. Before you apply this hotfix, if you discover virtual server and cluster resources such as physical and logical disks in an active node, delete a physical disk object from the Operator Console, fail the resources over to another active node, and run the Discovery_NT Knowledge Script on the virtual server, the Operator Console tree view displays new and duplicated physical and logical objects. After you apply this hotfix, the Knowledge Script rediscovers the deleted physical disk under the resource from which you deleted it. (ENG282512)


Contents of the Download Package

The download package contains the following files, which are used by the hotfix setup program unless otherwise noted:

  • AM7025_Hotfix72041_Setup.exe, the hotfix setup program
  • BaseInstall.dll
  • MFC71u.dll
  • msvcp71.dll
  • msvcr71.dll
  • Patch.ini
  • AM7025_ReadMe72041.htm, this readme
  • Setup Files, a folder that contains AM7025_Hotfix72041_MSSetup.msp, the management server setup program. The hotfix setup program automatically runs this file to update the management server.


Installing This Hotfix

To install this hotfix, run AM7025_Hotfix72041_Setup.exe on all management server computers.

The PATCH.log file lists all changes and problems encountered during the installation process. The Windows installer log file, AM7025_Hotfix72041_MSSetup.msp.log, lists only the changes associated with the hotfix installation. By default, these files are located in the \NetIQ\Temp\NetIQ_Debug


Modified Files

This hotfix modifies the following files on all management server computers:

  • NetIQms.exe (7.0.25058.0)
  • NetIQ_ENU.dll (7.0.25058.0)
  • NetIQLic.dll (7.0.25058.0)
  • nqDbgHlp.dll
  • component.dat

 

Cause

This problem is caused by a known issue in the AppManager 7.0 and AppManager 7.0.1 Management Service.

Additional Information

Formerly known as NETIQKB72041

Previous Releases

Hotfix 71471 [April 16, 2009]

This hotfix resolves the following management server issues:

  • Resolves an issue where the management server does not correctly execute actions when you specify two proxy actions for an event. After the management server executes the first action, even though the second action appears to be in progress, the management server never executes it and instead repeats the first action. (ENG185521)
  • Resolves an issue where the management server crashes with an access violation. (ENG254770)
  • Resolves an issue where the AMAdminUnix_SetPrimaryMS job incorrectly generates a proxy event. If you select the Display "AppManager Proxy Events" as objects in treeview option on the Preference - Event Options dialog box when setting repository options, when you run the job on a UNIX agent that AppManager discovered by hostname, it generates a proxy event with the UNIX agent's IP address instead of generating an event for the UNIX agent. (ENG254811)
  • Resolves an issue where the AMAdminUnix_SetPrimaryMS job fails to set the secondary management server value and update the MSDesignation table. When you run the job to set a secondary management server for a UNIX agent, the job does not update the agent properties, and it does not add an entry to the MSDesignation table. (ENG263098)

Hotfix 71362 [Jan 14, 2009]

This hotfix resolved an issue with the management server having excessive open connections with the AppManager repository. Before you apply this hotfix, when the management server monitors a large number of servers, the NetIQ Management Service opens some connections to the AppManager repository over a period of time and does not close them. Eventually this creates a strain on both the SQL Server computer that hosts the AppManager repository, and the management server computer. As a result, either or both the computers lose the ability to communicate with the network. After you apply this hotfix, all the open connections from the management server to the AppManager repository are closed when they are no longer necessary. (ENG245143)

Hotfix 71352 [Dec 10, 2008]

This hotfix resolved an issue where the UNIX agents stop communicating with the management server. Before you apply this hotfix, the UNIX agents stop communicating with the management server and lose connection to the AppManager repository. This issue occurs randomly on different UNIX agents on different management servers at different time periods. After you apply this hotfix, the UNIX agents no longer stop communicating with the management server and do not lose the connection to the AppManager repository. (ENG255402)

Hotfix 71253 [Oct 10, 2008]

This hotfix resolved an issue with the synchronization report of jobs when you migrate the AppManager repository. Before you apply this hotfix, when you migrate the AppManager repository from one SQL Server to another SQL Server, the netiqsync utility does not correctly display the synchronization report for the jobs running on the agents. After you apply this hotfix, when you migrate the AppManager repository, the netiqsync utility displays the correct synchronization report about jobs running on agents. (ENG195063, ENG252726)

Hotfix 71243 [Oct, 2008]

This hotfix resolved the following management server issues:

  • Resolved an issue where the management server stops responding to the UNIX agents. Before you apply this hotfix, when the management server monitors a large number of UNIX agents, it stops responding to the UNIX agents after a certain time period and becomes inactive. The issue occurs because the management server initiates a large number of open connections with the UNIX agents and becomes inactive when the number of connections exceeds the maximum limit of 1000. After you apply this hotfix, the management server will no longer stop responding to the communication from the UNIX agents and will continue to remain active. (ENG249419)
  • Resolved an issue where the UNIX agents stop communicating with the management server. Before you apply this hotfix, the UNIX agents stop communicating with the management server and lose connection to the AppManager repository. This issue occurs randomly on different UNIX agents on different management servers at different time periods. After you apply this hotfix, the UNIX agents no longer stop communicating with the management server and do not lose the connection to the AppManager repository. (ENG252298)

Contact Information

For detailed contact information, see the Support Contact Information Web site .


Feedback service temporarily unavailable. For content questions or problems, please contact Support.