Veritas Enterprise Administrator (VEA) becomes unresponsive when viewing the Replication Network.
book
Article ID: 100007824
calendar_today
Updated On:
Description
Error Message
The following Application entries were observed in some cases:
-------------------------------------------------------
Log Name: Application
Source: Windows Error Reporting
Date: 5/01/2012 5:51:47 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: N02.mydomain.com
Description:
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0
Problem signature:
P1: vea.exe
P2: 3.3.1066.0
P3: 4c750ad1
P4: 2ab3
P5: 6144
-------------------------------------------------------
Log Name: Application
Source: Application Hang
Date: 5/01/2012 5:51:47 PM
Event ID: 1002
Task Category: (101)
Level: Error
Keywords: Classic
User: N/A
Computer: N02.mydomain.com
Description:
The program vea.exe version 3.3.1066.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: a24
Start Time: 01cccb6409874ead
Termination Time: 16
Application Path: C:\Program Files (x86)\Veritas\Veritas Object Bus\bin\vea.exe
-------------------------------------------------------
Resolution
The issue has been identified. A fix is included in Cumulative Patch 8 (CP8) for SFW 5.1 SP2.
Applies To
-SFW 5.1 SP2
-VVR Configuration: via TCP or UDP, with and without compression.
Issue/Introduction
When using Veritas Volume Replicator (VVR) with Storage Foundation for Windows (SFW) 5.1 SP2, VEA Graphical User Interface (GUI) may become unresponsive when the Secondary Host is selected, under the Replication Network. The issue may be apparent when selecting the Replication Network, expanding the RDS and then attempting to modify the configuration (that is, right click on secondary RVG and selecting "Change Replication Settings"), or perform another VVR operation.
The above behavior was noticed while the selection is performed on the Secondary Host. VEA performs as expected on the Primary Host.
In some cases, the node itself may become unresponsive.
Additional Information
ETrack: n/a
Was this article helpful?
thumb_up
Yes
thumb_down
No