The server cannot accept the client session because the client does not use unicode and the node already contains a unicode filespace. The server records whether or not the client's data is unicode, and does not let the node change this attribute.
Processing stops.
Logon to the server from a client with a platform that uses unicode data. For example, the original platform that was used to create the existing filespaces for this node. Alternatively, if the client node needs to change to the platform that is currently being attempted, contact the server administrator to remove the existing filespaces that contain unicode data and try the node connection again.