Video Screencast Help

Symantec VRTShal executable/library encountered a problem and needed to close

Created: 27 Apr 2010 • Updated: 03 Jul 2010 | 1 comment
This issue has been solved. See solution.

 Symantec VRTShal executable/library encountered a problem and needed to close
I have a popup periodically from the console of our SAN connected SQL servers.  The pop up states the subject above.  In the application event logs the following error appears:
Event Type:        Error
Event Source:        Application Error
Event Category:        (100)
Event ID:        1000
Date:                4/27/2010
Time:                9:30:47 AM
User:                N/A
Computer:        SNKXS200
Faulting application hbaapp.exe, version 5.1.1694.0, faulting module ql2xhai2.dll, version, fault address 0x000044f9.
I have updated all of the known HBA software on the servers ... Sansurfer and Powerpath all look good .
I have no idea what is causing this nor what this is regarding.  Any ideas as to what is causing this? 

Comments 1 CommentJump to latest comment

RodP's picture

Hello Gregory15:

To answer your question from the data provided the following data was gleened from the error. You are running CommandCentral Storage (CCS) version 5.1.1 on a windows node with MSSQL installed and Qlogic HBA(s) connected to your SAN Switch. It is unknown which service agents you have installed on this Managed host (MH) but by default without Array Management or NetApp discovery  you will have the storage and host service agents (referred to as Explorers).

Likely prior or during the Local HAL Manager (LHM) stoppage you will experience a fault / failed  in the service agent.

To take a status of the CCS MH application you can run:
Note: assumed default install on a newer OS - remove the (86) for 32 bit
C:\Program Files (x86)\VERITAS\CommandCentral Storage\HAL\bin>"C:\Program Files (x86)\VERITAS\CommandCentral Storage\Support\Tools\VxCCS\VxCCS.bat" status
Microsoft (R) Windows Script Host Version 5.7
Copyright (C) Microsoft Corporation. All rights reserved.

***Veritas Hardware Abstraction Layer is running***
***Veritas CommandCentral Storage SICL is running***
***Symantec Private Branch Exchange is running***

Note: if installed for the Data Module component you will also see:
***Veritas CommandCentral Storage Data Module Explorers is running***

And to verify the service agents are active and not faulted you can run:
cd C:\Program Files (x86)\VERITAS\CommandCentral Storage\HAL\bin
C:\Program Files (x86)\VERITAS\CommandCentral Storage\HAL\bin>halsecurity login
 Domain:        vx:cc_users
 Account:       admin
Enter password for admin: <enter the same password as you use to login to the CCS GUI as admin user>
Login Successful

Note: many returns on the following list snipped for brievity seen as empty line in the output
C:\Program Files (x86)\VERITAS\CommandCentral Storage\HAL\bin>halagentcfg list-processes -a
Process    [ApplicationExplorers]      RUNNING      1956
  Explorer [MSSQLExplorer]             RUNNING                Normal
Process    [HostExplorers]             RUNNING      268
  Explorer [HostExplorer]              RUNNING                Normal
  Explorer [StorageExplorer]           RUNNING                Normal
  Explorer [TapeDeviceExplorer]        RUNNING                Normal
Process    [HALLHM]                    RUNNING*     1252
  Explorer [HALLHM]                    RUNNING*               Normal

If any process is in a failed state it can be restarted using the command line flag start-process --process-name ProcessName [--service-group ServiceGroupName].

C:\Program Files (x86)\VERITAS\CommandCentral Storage\HAL\bin>halagentcfg  start-process --process-name HostExplorers 
Note: processes end as plural whereas explorers are singular, except for HALLHM

HALLHM has a different syntax to start that process you can use:

C:\Program Files (x86)\VERITAS\CommandCentral Storage\HAL\bin> LHM --start-service

The explorers listed for the Process  [HostExplorers] can use the hbaapi installed with CCS (vxhbaapi.dll) which may be in conflict with your version.

Description of the discovery in CCS by the different explorers is here -

Public Link:

Under the Qlogic site there is a reference to an issue which is known and can cause a problem with the ability to run CCS.

Symantec has documented the link on the Symantec support site at and since you have already upgraded your drivers likely this is not your issue.

You may still have a conflict with the Qlogic installed hbaapi and the CCS installed  vxhbaapi.dll which calls hbaapp. Please check that the environment path contains the link to the required libraries "C:\Program Files (x86)\VERITAS\CommandCentral Storage\HAL\bin".

If the problem remains after taking these steps there will likely be further data required which can be attained by a trained Symantec Technical Support staff member vai an open support issue to identify the exact cause and stop the annoying pop-ups from occurring on your system.