Error Code details
V-40-49159-33
Severity: n/a 
Component: Storage Foundation 
Message:
Failed to flush registry key %2, status (%3)

 

Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2009-11-10 02:32:17 PDT
Platform: Generic
Release: Generic
Content:

Symptoms
 
  • Status code V-40-49159-33
  • ERROR: "Failed to flush registry key  %2, status (%3)"
Notice

To provide our customers with as many troubleshooting resources as possible, Symantec Enterprise Technical Support is currently working to research and provide information for all possible status codes and errors that may appear while using Veritas Storage Foundation for Windows. An explanation, work-around, or solution for each status code will be added once this information has been developed. This is an on-going process.

If you have received this status code and require assistance, contact Symantec Enterprise Technical Support:
http://www.symantec.com/enterprise/support/index.jsp

 
Reference: http://entsupport.symantec.com/docs/287209
http://entsupport.symantec.com/docs/306653
http://entsupport.symantec.com/docs/306632
Solution 2 Vote: [Useful] [Not useful]
Last Modified: 2009-11-10 05:21:42 PDT
Platform: Generic
Release: Generic
Content:

V-40-49159-33 - The IRP (%2) is failing with error status (%3) after VxDMP has attempted to send it through all connected paths.

Possible causes

DMP has tried to do fail-over all connected paths to continue IO, but it could not.  This is just to inform that DMP can not do a fail-over on the disk. Possible causes: all paths all the device are getting errors such as device disconnect, SCSI-2 reservation conflict.  

  •  

  • Solution

    Check and make sure all paths are connected correctly.
     
Solution 3 Vote: [Useful] [Not useful]
Last Modified: 2009-11-10 05:33:16 PDT
Platform: Generic
Release: Generic
Content:

V-40-49159-33 - Failed to flush registry key  %2, status (%3)

Possible causes

Registry operation failure.  The error indicates which registry have failed.  The chance of getting this error is almost impossible..

  •  

  • Solution

    Check system resources

 

User solutions
No user solutions yet.

 

Read and accept Terms of Service