The Veritas Storage agent (vxvm) terminates unexpectedly on service startup, or when new LUNs are added.

  • Modified Date:
  • Article ID:000008043


When using Storage Foundation for Windows (SFW) 5.1 Service Pack 1 in a virtualised environment, the Veritas Storage Agent service (vxvm) may terminate unexpectedly when LUNs from a Clariion system are used.  Subsequent attempts to restart the service will fail until the Clariion storage is removed from the system.

This prevents clustered solutions from working correctly and removes the ability to change storage configuration in non-clustered solutions.

If a process memory dump is captured from the event, it reveals a stack similar to this when captured with full page heap tracking:

1645f5cc 17909a6d msvcr71!memcpy+0x33
1646f668 17904752 vdid_shr!vdid_get_fn+0x8a45
1646f7dc 178dae18 vdid_shr!vdid_get_fn+0x372a
1646f800 178d8e58 ddlprov!vdid_get+0x1c8
1646fdc0 178cbb6c ddlprov!CDdlprov::GetVdid+0x402
1646fdd4 178cdcd7 ddlprov!CDdlprov::UpdateDeviceInfoFromDisk+0x22
1646fe68 178d6b77 ddlprov!CDdlprov::OnDeviceArrival+0xea
1646fe88 178cdeeb ddlprov!CDdlEventListener::OnDeviceArrival+0x2f
1646fe9c 178d2aca ddlprov!CVxEventPath<CDdlEventListener,CVxEventNotification>::Invoke+0x35
1646feb8 178d651f ddlprov!CVxEventDispatcher::Dispatch+0x56
1646feec 178d655d ddlprov!CVxEventManager::Notify+0xa5
1646fef8 10057b01 ddlprov!CVxProvider::ChangeNotify+0x14
1646ff08 100568db vxpal3!Provider::VxapiChangeNotify+0x21
1646ff20 10079d1c vxpal3!Provider::ChangeNotify+0x3b
1646ff40 10095609 vxpal3!NotifyJob::Run+0x7c
1646ff58 100956ec vxpal3!WorkerThread::Exec+0x39
1646ff60 015fac8c vxpal3!WorkerThread::ThreadProc+0xc
1646ff70 016192b0 vxveautil!vxpr_dummy_func+0xc
1646ff84 7c349565 vxveautil!apr_thread_create+0xf0
1646ffb8 7d4dfe37 msvcr71!_endthreadex+0xa0

Error Message

ERROR 1000(0x000003e8) Application Error <HOSTNAME> Faulting application vxpal.exe, version 3.3.1064.0, time stamp 0x4af29dd5, faulting module ntdll.dll, version 6.0.6002.18005, time stamp 0x49e03824, exception code 0xc0000005, fault offset 0x0002ac0f,


In a virtual environment, more data than expected is returned from a specific SCSI query issued against certain Clariion devices.  This causes a heap corruption within vxvm which causes it to crash.


This issue has been identified and a private fix is available from Symantec Enterprise Technical Support. To obtain the private fix, contact Symantec Enterprise Technical Support and reference this article during the call. A support representative will be available to assist in troubleshooting this issue. If it is determined that the private fix addresses the problem the support representative will further assist in obtaining the private fix.
Note: This fix specifically addresses the problem identified above. It has not been fully tested and should be applied in a test environment before placing into production. If the systems are not critically impaired, it is recommended to delay the installation of this private fix until the next scheduled maintenance release. Before applying this private fix, systems may be required to be upgraded to the latest code base. The support representative will help in determining the best course of action.
File information:
FilenameFile version

Applies To

SFW 5.1 Sp1

Virtualised node hosted within VMWare ESX or VSphere

EMC Clariion storage array

Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)