1. Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING) Click the link to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This message will disappear after you have made at least 12 posts. Thank you for your cooperation.

VSS error VSS_E_PROVIDER_VETO

Discussion in 'TSM Client' started by Samuel, Mar 16, 2010.

  1. Samuel

    Samuel New Member

    Joined:
    Jul 9, 2008
    Messages:
    286
    Likes Received:
    1
    Hello Guys,

    The admin Windows send me an error with windows 2003 R2 SP2 "VSS_E_PROVIDER_VETO" :
    03/15/2010 03:06:48 ANS5269E The Microsoft Volume Shadow Copy Services writer 'System Writer' current state (VSS_WS_FAILED_AT_PREPARE_BACKUP) is not valid for the current operation or cannot be determined. The last error reported is '00000000'.
    03/15/2010 03:06:48 ANS5250E An unexpected error was encountered.
    TSM function name : baHandleSnapshot
    TSM function : DVssSnapshot::startSnapshot(): VSS[QueryStatus:DoSnapshotSet: VSS_E_PROVIDER_VETO :confused:(See the Microsoft Application event log for additional VSS messages).
    TSM return code : -1
    TSM file : incrdrv.cpp (9936)
    03/15/2010 03:06:48 ANS1327W The snapshot operation for 'CHGE1INFR004\SystemState\NULL\System State\SystemState' failed with error code: -1.
    03/15/2010 03:06:48 ANS1228E Sending of object 'CHGE1INFR004\SystemState\NULL\System State\SystemState' failed
    03/15/2010 03:06:48 ANS5283E The operation was unsuccessful.
    03/15/2010 03:06:48 ANS1375E The snapshot operation failed.
    03/15/2010 03:06:51 ANS5283E The operation was unsuccessful.
    03/15/2010 03:06:51 ANS1512E Scheduled event '**2300' failed. Return code = 12.
     
  2.  
  3. Samuel

    Samuel New Member

    Joined:
    Jul 9, 2008
    Messages:
    286
    Likes Received:
    1
  4. toxy13

    toxy13 Senior Member

    Joined:
    Sep 24, 2003
    Messages:
    739
    Likes Received:
    12
    Occupation:
    Administrator
    Location:
    Leipzig
  5. Samuel

    Samuel New Member

    Joined:
    Jul 9, 2008
    Messages:
    286
    Likes Received:
    1
    Hi TOXY13,

    Actually we have windows 2003 r2 sp2 installed.
    I have just received an answers from IBM :
    1) Verify KB installed :
    http://www-01.ibm.com/support/docview.wss?uid=swg21242128
    2) Trace VSS :
    http://www.microsoft.com/downloads/...e4-0ccc-4626-826a-ed2c4c95c871&displaylang=en
    3) commands VSHADOW
    vshadow -wm2 > vs_wm2.out
    vshadow -ws > vs_ws.out
    vshadow -nw x: > vs_nw_c.out
    vshadow-nw -p x: > vs_p_c.out
    vshadow -p x: > vs_p_c.out
    where x: is the drive letter for the system drive (usually C:)

     
  6. toxy13

    toxy13 Senior Member

    Joined:
    Sep 24, 2003
    Messages:
    739
    Likes Received:
    12
    Occupation:
    Administrator
    Location:
    Leipzig
    Whats your tsm client version?
     
  7. Samuel

    Samuel New Member

    Joined:
    Jul 9, 2008
    Messages:
    286
    Likes Received:
    1
    The version is 5.5.2.2

     
  8. rznadmin

    rznadmin New Member

    Joined:
    Feb 20, 2004
    Messages:
    67
    Likes Received:
    2
    Hi,
    has your problem been fixed yet?
    I'm running into the same issue with some of my WIN2003 clients.
     
  9. Samuel

    Samuel New Member

    Joined:
    Jul 9, 2008
    Messages:
    286
    Likes Received:
    1
    The problem is resolved

    Yes, actually the problem is resolved after upgraded packages.

     
  10. rznadmin

    rznadmin New Member

    Joined:
    Feb 20, 2004
    Messages:
    67
    Likes Received:
    2
    Hi,
    still having problems:

    Win2003 SP2 with following Hotfixes installed:
    KB940349-v3
    KB934016
    KB951568

    TSM Client Version 5.5.2.10

    Corresponds this with your installation?
     
  11. domino

    domino Senior Member

    Joined:
    Nov 16, 2005
    Messages:
    717
    Likes Received:
    32
    Occupation:
    System Engineer
    Location:
    Germany
    Please Check, if VSS Writers are in good state (stable without errors)

    try: vssadmin list writers
     
  12. rznadmin

    rznadmin New Member

    Joined:
    Feb 20, 2004
    Messages:
    67
    Likes Received:
    2
    It says: "last error: no error" for all writers als long as the client session is running and
    also after it has timed out
    (Event ID 12310 in App Event Log).
     

Share This Page