topic signon session encoding not compatible in Administration and Deployment

signon session encoding not compatible

bbb_NG — Tue, 18 Apr 2017 09:13:21 GMT

Hi, I have problem with sign on encoding.

with the error;

NOTE: Remote signon to REMHOST commencing (SAS Release 9.03.01M2P081512).
NOTE: Script file 'tcpwin.scr' entered.
NOTE: Logged onto Windows... Starting remote SAS now.
NOTE: SAS/CONNECT conversation established.
ERROR: The client session encoding utf-8 is not compatible with the server session encoding wlatin1.

Can SB give a hand as how to solve the above problem.

Thanks in advance.

Re: signon session encoding not compatible

BrunoMueller — Tue, 18 Apr 2017 09:35:35 GMT

Please have a look here http://support.sas.com/documentation/cdl/en/connref/69581/HTML/default/viewer.htm#n1smv71b6303yen17kx46uxc0nxh.htm which gives some explanation on the error you get.

If possible use the same encoding for the client and server sessions.

Bruno

Re: signon session encoding not compatible

bbb_NG — Wed, 19 Apr 2017 00:44:53 GMT

HI Bruno,

I've found the instructions already, sorry I still have no idea how to solve it.

Actually, the same code (signon-singoff rsubmit-endrsubmit) can run successfully on SAS 9.3.

While I embedded the SAS file into a BAT file. It reports the above error.

Can you figure out that?

Thanks in advance.

Re: signon session encoding not compatible

BrunoMueller — Wed, 19 Apr 2017 06:08:38 GMT

I think it is best to contact technical support for this. While you say it runs under some circumstances but not others, one has to figure out the differences between the two, like SAS version for client and server, session encoding for client and server, etc.

You can run the following on the client as well as on the server to get information on version and session encoding.

%put NOTE: &=sysvlong &=sysscpl;
proc options group=languagecontrol;
run;

Bruno

Re: signon session encoding not compatible

bbb_NG — Wed, 19 Apr 2017 06:52:13 GMT

Hi Bruno,

Thanks a lot for your help.