I believe that the trouble is in mapping some of the characters in the
file name to the ANSI code page in which Windows is running (notice the
'?' character in the file name). Files whose names contain characters that
are not in the ANSI code page can't be backed up by pre-TSM 4.2 software.
This is discussed in the TSM Windows client manual "Using the
Backup-Archive Client", chapter 1, section "Migrating to the
Unicode-Enabled Client".
TSM 4.2 includes Unicode support. You must have the 4.2 client AND server
in order to use this support.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"Rooij, FC de" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
11/22/2001 08:20
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: fioScanDirEntry(): Can't map object 'xxxx' into the local
ANSI c
odepage, skipping ...
I got the following message at the Windows backup, can somebody explain
how
this can happen and how to solve this. Is this a windows problem or a TSM
problem?
My client is win 4.2.0.0 and the TSM is running server 4.1.3.
message:
11/22/2001 00:09:32 fioScanDirEntry(): Can't map object
'G:\Data\Projecten\Logistieke Doorbraak\Sales & Operations Planning\00
Personal folders\Pim\SOP_058 PB Visit hel?S sweden 07.04.98.doC' into the
local ANSI codepage, skipping ...
Fred de Rooij
