It isn't really the client code level, it's a bug involving Unicode vs. non-unicode clients.
If you have access to the new IBM/TSM support site, search on ANR0428W and there is a post with instructions for patching the database entries for the damaged client. I had to do this for 2 clients in the same situation this week, and it worked with no problem. If you aren't comfortable doing that on your own, you should place a call to support and let them walk you through the process. -----Original Message----- From: Stefan Johansson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 05, 2003 5:16 AM To: [EMAIL PROTECTED] Subject: Incorrect platform Hi! On a system running TSM server 4.2.1 on W2K a customer has accessed a node from a WinNT console, thereby changing the platform from Netware to WinNT. All attempts to run dsmc results in; 2003-02-05 10:08:50 ANR0428W Session 20221 for node LTK_NWFS1 (NetWare) refused - client is down-level with this server version. I�ve tried to upgrade the client to the latest version, 5.1.5.6 from 5.1.5 with no luck, and also to downgrade to 5.1 with the same result. Now, the only ways I know to reset the node to Netware platform is; restore the TSM DB to a date before the change (2 weeks now), resulting in 2 lost weeks of backups for all clients, OR deleting the node and then re-create it, resulting in total loss of backup for that node (2 years of data on what of course has to be the biggest fileserver, about 250 GB). None of the options is really acceptable to the owners of the data, so PLEASE, is there a third option? Is there perhaps a way to "manipulate" the "platform"-value in TSM:s database? Kindly Regards Med v�nliga h�lsningar Kjell Svensson E-post; [EMAIL PROTECTED] Mobiltel; +46733-67 17 95
