Hello Bud,
this error is caused by the support of UNICODE.
With the TSM server version 4.2 and above and TSM client version 4.2 and above,
Tivoli is supporting UNICODE filespaces.
If you query the filespaces on your TSM server, you will see an additional
column, wether this filespace is UNICODE or not.
If your TSM server is not version 4.2 or your filespace for this node is not
UNICODE, you will receive this "error"-message.
For fixing this problem, you have to
a) update your TSM server to version 4.2.x or
b) rename the old filespace for this node or delete the filespace
Mit freundlichen Grüßen / Best Regards
Uwe Schreiber
[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
22.02.2002 20:22
Please respond to ADSM-L
To: [EMAIL PROTECTED]
bcc:
Subject: Can't Map Object?
Has anybody seen this error before? I have about 20 files that the B/A
client is 'skipping. . .' The common theme is that the files do not
have file extensions.
02/22/2002 00:47:14 fioScanDirEntry(): Can't map object 'E:\Dept\Public
Relations\ Graphic Archives\Trauma Conference\Trauma Conf logo?no year'
into the local ANSI codepage, skipping ...
Bud Brown
Information Services
Systems Administrator
