LHM, CHM, and/or explorer processes are hanging.

Article:TECH167963  |  Created: 2011-08-24  |  Updated: 2011-11-14  |  Article URL http://www.symantec.com/docs/TECH167963
Article Type
Technical Solution


Environment

Issue



The PBX port (1556) used by the CommandCentral Storage (CCS) processes for communication is shutting down.


Error



 [halrun -q] halrun.cpp:1070: Process HALLHM - HUNG (5932)
 [Error] V-86-9-70 [HALLHM@<FQHN>] Process "HALLHM" PID = "5,932" has entered unexpected state: HUNG.


Could be any process but usually is the one most active at the time the communications are interrupted

[HALCHM] HALEventPoster_i::post_event: CORBA EXCEPTION error while trying to post event "system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0'
OMG minor code (2), described as '*unknown description*', completed = NO

[HALLHM@<FQHN>] Windows_NT_main.cpp:722: SCMNotifyState: SetServiceStatus. newState SERVICE_STOPPED lastErr=0x6
[FCExplorers] HALEventPoster_i::post_event: CORBA EXCEPTION error while trying to post event "system exception, ID 'IDL:omg.org/CORBA/COMM_FAILURE:1.0'
TAO exception, minor code = 6 (failed to recv request response; ENOENT), completed = MAYBE
"
Loss of contact with database
FD[6]:             Category: MANAGEMENT
FD[7]:              Message: The connection to the Storage Manager Database was lost.
FD[8]:                  UMI: V-86-3-1012
FD[9]:             Severity: CRIT

 

PBX failure


[CIMVAILExplorers] T2140 event_base.cpp:111: HALEventBase: THROWING TransportInitializationFailed
[CIMVAILExplorers] HALBase: Exception during HALEventPoster_i creation!
[Error] V-86-1-10 [halrun] BAD PARAM exception on ORB creation
Please Check if a PBX Exchange is running...
Also check if a service with same name is running...
Also check for user privileges and PBX Configuration...


Cause



A 3rd party application is interfering with an established connection by blindly closing the port(s) or making the system so busy as to hang communications.

The McAfee definitions and engine updates can consume 100% of CPU on a Virtual Machine and interfere with any other running processes.


Solution



Lower the priority of the McShield process so that it does not consume all cpu cycles and allows other processes to continue running.  Add a registry key entry as specified below:

1.      ThreadPriority of McShield can be set to normal via a registry tweak -


          a.      HKLM\Software\McAfee\SystemCore\VSCore\On Access Scanner\McShield\Configuration, RunAtNormalPriority
                   This is a DWORD that needs to be created, and given the value of 1.


          b.      Restart the McShield service for the change to take effect.




Article URL http://www.symantec.com/docs/TECH167963


Terms of use for this information are found in Legal Notices