Forum Discussion

Krishna123's avatar
Krishna123
Level 3
11 years ago

Trouble shoot tips for Error code 156(Snapshot error)

Hi to all,

Can any one provide me techno note on troubleshooting for error code 156( Snapshot error).

regards,

Krishna.

  • you can find the lot of T/N in the google about this...thouch 156 is the same status code the reason might be different for each case... you need to deal with it case by case.. rather than looking into the generic docs..

    i would suggest you to start from below.. 

    http://www.symantec.com/business/support/index?page=content&id=TECH47808

    lot more in google...

6 Replies

  • you can find the lot of T/N in the google about this...thouch 156 is the same status code the reason might be different for each case... you need to deal with it case by case.. rather than looking into the generic docs..

    i would suggest you to start from below.. 

    http://www.symantec.com/business/support/index?page=content&id=TECH47808

    lot more in google...

  • I agree with Nagalla. Google is your friend.

    Another TN I have found:

    VMware status 156:
    http://www.symantec.com/docs/HOWTO44492

    It helps to add the error message before you see status 156 and detail such as the OS version and backup type.

     

  • General Steps :

    1) vssadmin list writers : Ensure all ur writes are stable

    2) Make sure u have good snap size configured for given drive i.e.10% of utilization.

    3) Always use bpfis logs for troubleshooting.

    4) Application logs in windows log viewer are helpful.

    5) Many times in 156 ; System state backups fails ; make sure any dll is not crashing and not faulting bpbkar ; this can be seen in apllication viewer ; many times i see 6.5 on 2008 windows machines which is not supported.....so on and so forth.....................................................

    Help your self :)

  • Thanks for this, from me also it helps. Those 156 snapshot errors can be caused by different reasons as someone pointed out and I am constantly finding out.