Re: ANS1357S Session rejected: Downlevel client code version

Are you using same nodename on all platforms, i.e. connect as nodename A 
from NetWare, Linux and Windows?
You should use separare nodes for each platform. After you have connected 
from Windows, the node was "upgraded" to work with Unicode-enabled 
filespaces. After that "upgrade" you will not be able to connect using 
client which is not Unicode-enabled.

If you connect from Windows system using nodename B it would also "stop 
working".

Zlatko Krastev
IT Consultant






Marek Wełpa <marekwel AT POLCARD.COM DOT PL>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04.06.2003 15:44
Please respond to "ADSM: Dist Stor Manager"

 
        To:     ADSM-L AT VM.MARIST DOT EDU
        cc: 
        Subject:        ANS1357S Session rejected: Downlevel client code version


Hi!

I use one TSM client for archiving different physical client (NT, Novell,
TRU 64, Linux, O/S 2)
When I tray archive new data I got error:  "ANS1357S Session rejected:
Downlevel client code version".
It is occur when I connect client as nodename A (?archive client?) ? it
doesn?t meter witch command will be used (q sess, inc, etc.) , When I
connect normal client (as nodename B) in the same client all is OK. I
checked it is happed on client:
-     Platform: DEC UNIX, Client OS Level: V5.1, Client Version: Version 
4,
Release 2, Level 0.0
-     Platform: NetWare, Client OS Level: 5.0, Client Version: Version 4,
Release 2, Level 2.0
On NT all is correct:
-     Platform: WinNT, Client OS Level: 4.00, Client Version: Version 4,
Release 2, Level 2.
My TSM server is:
-     Server Type: Windows, Server Version: Ver. 4, Rel. 2, Lev. 3.3
Can someone correct me this error?

Regards

Marek Welpa
DBA
PolCard S.A.
ul. Ostrobramska 103
04-041 Warszawa
e-mail:welpam AT polcard.com DOT pl
tel. (+48-22) 515-38-06
fax. (+48-22) 515-36-35