Architecting, installing and maintaining your SAS environment

SAS Connect Server Error:

Reply
Occasional Contributor
Posts: 17

SAS Connect Server Error:

When an user runs the below code in SAS EG they have received the below error. We have check the configuration files it seems to be good when compared with other application servers which are in working condition.

 

Note: User is connecting from local PC to the production environment

 

Code:


options metaserver         = 'prod94.metadata.int.bell.ca'
        metaport         = 8562
        metarepository     = 'Foundation'
        metauser         = 'hdroogen'
        metapass         = 'Dec.2016.';
signon server='BIApp - Connect Server' ;
libname rmtwork server=local slibref=work;
%let freq = norow nocol nopercent missing;
options nocenter;
rsubmit;
%include "/users/&sysuserid/sas/autoexec_prod94.sas";
endrsubmit;

 

 

Log:

 

21         
22         GOPTIONS ACCESSIBLE;
23         
24         options metaserver         = 'prod94.metadata.XXX'
25                 metaport         = 8562
26                 metarepository     = 'Foundation'
27                 metauser         = 'XXXXX'
28                 metapass         = XXXXXXXXXXX;
29             
30         
31         
32         signon server='App - Connect Server' ;
ERROR: IOM call failed because of a data conversion error.
ERROR: Failed to transcode data from U_UTF8_CE to U_LATIN1_CE encoding because it contained characters which are not supported by
your SAS session encoding.  Please review your encoding= and locale= SAS system options to ensure that they can accommodate the
data that you want to process.  A portion of the source string, in hex representation is:
NOTE: 7f5b5b17f130: 3c 47 65 74 4d 65 74 61 64 61 74 61 4f 62 6a 65 |<GetMetadataObje|
NOTE: 7f5b5b17f140: 63 74 73 3e 3c 52 65 70 6f 73 69 64 3e 41 30 30 |cts><Reposid>A00|
ERROR: Some code points did not transcode.
ERROR: XML request to SAS Metadata Server failed.
ERROR: Unable to retrieve the SAS/CONNECT server definition "APP - CONNECT SERVER".
ERROR: Remote signon to APP - CONNECT SERVER canceled.
33         
34         
35         
36         libname rmtwork server=local slibref=work;
ERROR: Attempt to connect to server LOCAL failed.
ERROR: A communication subsystem partner link setup request failure has occurred.
ERROR: Cannot find TCP service 'local'.
ERROR: Error in the LIBNAME statement.
37         
38         %let freq = norow nocol nopercent missing;
39         options nocenter;
40         
41         rsubmit;
ERROR: Invalid or unspecified remote session ID. Set OPTIONS REMOTE=session_id.
NOTE: Subsequent lines will be ignored until ENDRSUBMIT.
2 The SAS System                                                                                     07:46 Tuesday, January 10, 2017

ERROR: Remote submit to UNKNOWN canceled.
42         
43         
44         GOPTIONS NOACCESSIBLE;
45         %LET _CLIENTTASKLABEL=;
46         %LET _CLIENTPROJECTPATH=;
47         %LET _CLIENTPROJECTNAME=;
48         %LET _SASPROGRAMFILE=;
49         
50         ;*';*";*/;quit;run;
51         ODS _ALL_ CLOSE;
52         
53         
54         QUIT; RUN;
55        

Super User
Posts: 5,254

Re: SAS Connect Server Error:

Perhaps I'm missing something obious, but EG, local PC SAS and production environment sounds like there is one component too much.

Why don't you connect directly to prod from EG (no need for SAS/CONNECT signon then)?

Data never sleeps
Super User
Posts: 6,926

Re: SAS Connect Server Error:

I see this

signon server='BIApp - Connect Server' ;

in your code, but this

32         signon server='App - Connect Server' ;

in your log. The 'BI' is somehow swallowed. Look how those characters are entered in the code, there might be unexpected UTF encodings there (maybe from a copy/paste?)

 

And I also would omit the SAS/CONNECT part and use the production workspace server directly from EG. KISS.

---------------------------------------------------------------------------------------------
Maxims of Maximally Efficient SAS Programmers
Occasional Contributor
Posts: 17

Re: SAS Connect Server Error:

Hi Kurt,

 

I edited the "BIApp" to "App" before attaching the logs. Please leave this part.

 

User wants to connect from PC server to Prod environment. And he is getting this kind of error. Yes they can connect in EG and directly connect to Prod. But they want to use connect server logic. Kindly suggest in this scenario.

 

Regards,

Aravind

Super User
Posts: 6,926

Re: SAS Connect Server Error:

My first action would be to make your SAS environment homogenous, so that the desktop clients run with the same setting(s) that the server uses.

If your server uses a session encoding of Latin1, then your desktops should do the same.

---------------------------------------------------------------------------------------------
Maxims of Maximally Efficient SAS Programmers
Occasional Contributor
Posts: 17

Re: SAS Connect Server Error:

Could you please let me know how to give the same session encoding for desktops. In which file or any in detail help pls?
Super User
Posts: 6,926

Re: SAS Connect Server Error:

You will have to modify the sasv9.cfg in your Program Files\SAS\SASFoundation path.

 

-encoding=wlatin1

---------------------------------------------------------------------------------------------
Maxims of Maximally Efficient SAS Programmers
Ask a Question
Discussion stats
  • 6 replies
  • 578 views
  • 0 likes
  • 3 in conversation