The SAS PC File Server runs as a Windows Service on the Windows Server, so you need to first check that the service is running. If not, start it.
Please post the SAS log of your PROC EXPORT if you still have errors.
thanks for the reply, yes the service is running !
PLEASE SEE BELOW LOG, tried 2 kinds of codes, one for unix location and another for windows
1 The SAS System 02:54 Monday, September 28, 2020
1 ;*';*";*/;quit;run;
2 OPTIONS PAGENO=MIN;
3 %LET _CLIENTTASKLABEL='Program';
4 %LET _CLIENTPROCESSFLOWNAME='Process Flow';
5 %LET _CLIENTPROJECTPATH='';
6 %LET _CLIENTPROJECTNAME='';
7 %LET _SASPROGRAMFILE=;
8
9 ODS _ALL_ CLOSE;
10 OPTIONS DEV=ACTIVEX;
11 GOPTIONS XPIXELS=0 YPIXELS=0;
12 FILENAME EGSR TEMP;
13 ODS tagsets.sasreport13(ID=EGSR) FILE=EGSR
14 STYLE=HtmlBlue
15 STYLESHEET=(URL="file:///C:/Program%20Files/SASHome2/SASEnterpriseGuide/7.1/Styles/HtmlBlue.css")
16 NOGTITLE
17 NOGFOOTNOTE
18 GPATH=&sasworklocation
19 ENCODING=UTF8
20 options(rolap="on")
21 ;
NOTE: Writing TAGSETS.SASREPORT13(EGSR) Body file: EGSR
22
23 GOPTIONS ACCESSIBLE;
24 /*Tried for unix location*/
25 PROC EXPORT DATA=sashelp.class
26 OUTTABLE="class"
27 DBMS= ACCESSCS REPLACE ;
28 DATABASE="/tmp/class.mdb";
29 SERVER='pscpmverstudio01.juniper.com';
30 PORT=9621;
31 RUN;
ERROR: Connection Failed. See log for details.
NOTE: The SAS System stopped processing this step because of errors.
NOTE: PROCEDURE EXPORT used (Total process time):
real time 0.07 seconds
user cpu time 0.00 seconds
system cpu time 0.01 seconds
memory 462.18k
OS Memory 21412.00k
Timestamp 09/28/2020 02:58:34 AM
Step Count 6 Switch Count 0
Page Faults 0
Page Reclaims 122
Page Swaps 0
Voluntary Context Switches 20
Involuntary Context Switches 3
Block Input Operations 0
Block Output Operations 0
32 /*Tried for windows location*/
33 PROC EXPORT DATA=sashelp.class
34 OUTTABLE="class"
2 The SAS System 02:54 Monday, September 28, 2020
35 DBMS= ACCESSCS REPLACE ;
36 DATABASE="C:\temp\class.mdb";
37 SERVER='pscpmverstudio01.juniper.com';
38 PORT=9621;
39 RUN;
ERROR: Connection Failed. See log for details.
NOTE: The SAS System stopped processing this step because of errors.
NOTE: PROCEDURE EXPORT used (Total process time):
real time 0.07 seconds
user cpu time 0.00 seconds
system cpu time 0.00 seconds
memory 438.65k
OS Memory 21668.00k
Timestamp 09/28/2020 02:58:34 AM
Step Count 7 Switch Count 0
Page Faults 0
Page Reclaims 38
Page Swaps 0
Voluntary Context Switches 24
Involuntary Context Switches 1
Block Input Operations 0
Block Output Operations 0
40
41 GOPTIONS NOACCESSIBLE;
42 %LET _CLIENTTASKLABEL=;
43 %LET _CLIENTPROCESSFLOWNAME=;
44 %LET _CLIENTPROJECTPATH=;
45 %LET _CLIENTPROJECTNAME=;
46 %LET _SASPROGRAMFILE=;
47
48 ;*';*";*/;quit;run;
49 ODS _ALL_ CLOSE;
50
51
52 QUIT; RUN;
53
Is this the full log? Are there any firewalls which is dropping the connection to the port? "Connection failed" is a very generic error. See if you can add some debug options for more detailed logging.
there is not firewall for sure, I just tried telnet from sas app servers also, its all good, and in workspace server logging I see the same "connection failed" log, nothing more, can you suggest me the options I can use in code for more log ? and can you confirm I dont ahve to install anything else on windows server expcet for pc files server ?
Have you tried adding a userid and password using the SERVERUSER and SERVERPASS parameters? These need to be valid for the Windows server running the SAS PC Files Server.
hi thanks for the prompt repiles, first i tried giving my credentials, and I saw "username cant be validated" error, then I realized the credentials should have server access, then I used the right service account which used to install pc files server, then again I see "ERROR: Connection Failed. See log for details.", the same error have been getting
PROC EXPORT DATA=sashelp.class
OUTTABLE="class"
DBMS= ACCESSCS REPLACE ;
DATABASE="C:\temp\class.mdb";
SERVER='pscpmverstudio01.juniper.com';
SERVERUSER='DRYROCK\service_erwinprd';
SERVERPASS='XXX';
PORT=9621;
RUN;
I suggest you open a track with Tech Support as they are in the best position to diagnose this.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.