IBM Support

IT22707: ANS5250E ENCOUNTERED DURING 'RESTORE SYSTEMSTATE' IN HARDLINKSWRITE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Restoring the system state of a Windows system might fail with
    following error:
    
    mm/dd/yyyy hh:mm:ss ANS5250E An unexpected error was
    encountered.
       TSM function name : HardLinksWrite
       TSM function      : Internal error, buffer size differs from
    bytes to write
       TSM return code   : -1
       TSM file          : ..\..\common\winnt\psmech.cpp (5915)
    mm/dd/yyyy hh:mm:ss ANS5283E The operation was unsuccessful.
    
    The problem can (but will not always) surface during system
    state restore for objects backed up by a client version that
    meets either of these criteria:
    * The version number is lower than 6.4.3.
    * The version number is 7.1.0.0 - 7.1.1.x.
    
    IBM Spectrum Protect Versions Affected:
    Tivoli Storage Manager client on Windows 7.1.2.x
    IBM Spectrum Protect client on Windows 7.1.3 and newer
    IBM Spectrum Protect client on Windows 8.1.0 and newer
    
    Customer/L2 Diagnostics:
    
    1. Collect a SERVICE trace of the problem restore.
    
    2. Starting from the bottom of the trace, find the last entry
    that looks like this.
    
    ...
    ..\..\common\winnt\psmech.cpp(5693):
    HardLinksOpen(\\?\Volume{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}\W
    indows\winsxs\amd64_microsoft.transactions.bridge.dtc_b03f5f7f11
    d50a3a_6.0.6001.18096_none_a78007807e645ae6\Microsoft.Transactio
    ns.Bridge.Dtc.dll): Entry.
    ..\..\common\winnt\psmech.cpp(5878):
    HardLinksWrite(\\?\Volume{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}\
    Windows\winsxs\amd64_microsoft.transactions.bridge.dtc_b03f5f7f1
    1d50a3a_6.0.6001.18096_none_a78007807e645ae6\Microsoft.Transacti
    ons.Bridge.Dtc.dll): Entry.
    ..\..\common\winnt\psmech.cpp(5885): HardLinksWrite(): Dump of
    write buffer for
    '\\?\Volume{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}\Windows\winsxs
    \amd64_microsoft.transactions.bridge.dtc_b03f5f7f11d50a3a_6.0.60
    01.18096_none_a78007807e645ae6\Microsoft.Transactions.Bridge.Dtc
    .dll':
    
    *** 782 Byte Write Buffer ***
    
    
    Dumping Memory Range 00000000060DBFD0 - 00000000060DC2DE (782
    Bytes)
    
    00000000060DBFD0: 03 0E 00 02 00 00 00 95 63 00 3A 00 5C 00 57
    00     .......?c.:.\.W.
    060DBFE0: 69 00 6E 00 64 00 6F 00 77 00 73 00 5C 00 77 00
    i.n.d.o.w.s.\.w.
    ...
    
    Note: the file name from the trace example can be different,
    depending where the failure happens.
    
    3. Look at the "*** 782 Byte Write buffer ***" lines and the
    "Dumping Memory Range ..." lines.
       Note the number of bytes to write is 782 (we expect in all
    cases that these numbers are the same, and they are the correct
    number of bytes to write).
    
    4. Look at the first five bytes of the hexadecimal data. In the
    above example, the first five bytes are:
    
       03 0E 00 02 00
    
    5. The problem is a match to this APAR when all of the following
    are true:
    
      * The first byte is 03
      * The next four bytes, in reverse order, represent a value
    that does not equal the number of byte to write (from step 3).
      * The object was backed up by a client lower than 6.4.3, or
    between 7.1.0.0 and 7.1.1.x.
    
    In this case, the first byte is 03. The next four bytes, in
    reverse order, are 0002000E or decimal valuee 131086, which is
    not equal to the number of bytes to write, 782.
    
    Initial Impact: Medium
    
    Additional Keywords: TSM, Tivoli, Storage, Manager, system,
    state
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * IBM Spectrum Protect backup-archive clients versions 7.1.6,  *
    * 7.1.8, 8.1.0 and 8.1.2 running on all Windows platforms.     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See ERROR DESCRIPTION                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixing level when available. This problem is currently *
    * projected to be fixed in level 8.1.4.                        *
    * Note that this is subject to change at the discretion of     *
    * IBM.                                                         *
    ****************************************************************
    

Problem conclusion

  • The routine that handles hard links creation has been modified
    to correctly process objectes that were backed up previous
    version of the TSM client.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT22707

  • Reported component name

    TSM CLIENT

  • Reported component ID

    5698ISMCL

  • Reported release

    71W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-10-18

  • Closed date

    2017-10-20

  • Last modified date

    2017-10-20

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • DSM      DSMC     DSMCSVC
    

Fix information

  • Fixed component name

    TSM CLIENT

  • Fixed component ID

    5698ISMCL

Applicable component levels

  • R81W PSY

       UP



Document information

More support for: Tivoli Storage Manager

Software version: 71W

Reference #: IT22707

Modified date: 20 October 2017