BookmarkSubscribeRSS Feed
☑ This topic is solved. Need further help from the community? Please sign in and ask a new question.
Kubo_VF2019
Calcite | Level 5

New to SAS Server Administration.

Currently running Base SAS Software 9.4_M6 with SAS/ACCESS Interface to R/3 4.4_M4. We are running into the issue described in hot fix L3P001 for M6. SAP support does not recommend reverting to a previous version of the NetWeaver RFC libraries. There is not a hot fix for M4 so I will need to do an upgrade. I'm not able to find the download or instructions to upgrade to M6. All help will be appreciated.

L3P001 = https://support.sas.com/kb/68/720.html

 

TIA,

Vince

1 ACCEPTED SOLUTION

Accepted Solutions
Patrick
Opal | Level 21

If I understand this right then as per the link you share SAS states:
"...The workaround is to use a version of the SAP NetWeaver RFC SDK that is earlier than Patch Level 8."

 

The fix list shows you that the issue has been reported in M6 but there is no fix yet.

Patrick_1-1665831326429.png

 

I understand your dilemma with SAP telling you to not revert to an earlier version of the NetWeaver RFC libraries.

 

Bit of a dilemma here. 

 

If you've got a written "not recommended" statement from SAP then I suggest you contact SAS Tech Support directly, share the info from SAP and ask for advice how to resolve this. 

 

View solution in original post

5 REPLIES 5
SASKiwi
PROC Star

Are Base SAS and SAS/ACCESS Interface to R/3 installed on the same SAS Compute server?! It is very unusual and not recommended to be running different maintenance levels in the same SAS installation. How did this even happen in the first place? Please run this program and post the results:

proc product_status;
run;
Kubo_VF2019
Calcite | Level 5

Here is the command.

 

1 ;*';*";*/;quit;run;
2 OPTIONS PAGENO=MIN;
3 %LET _CLIENTTASKLABEL='Program';
4 %LET _CLIENTPROCESSFLOWNAME='Standalone Not In Project';
5 %LET _CLIENTPROJECTPATH='';
6 %LET _CLIENTPROJECTPATHHOST='';
7 %LET _CLIENTPROJECTNAME='';
8 %LET _SASPROGRAMFILE='';
9 %LET _SASPROGRAMFILEHOST='';
10
11 ODS _ALL_ CLOSE;
12 OPTIONS DEV=SVG;
13 GOPTIONS XPIXELS=0 YPIXELS=0;
14 %macro HTML5AccessibleGraphSupported;
15 %if %_SAS_VERCOMP(9, 4, 4) >= 0 %then ACCESSIBLE_GRAPH;
16 %mend;
17 FILENAME EGHTML TEMP;
18 ODS HTML5(ID=EGHTML) FILE=EGHTML
19 OPTIONS(BITMAP_MODE='INLINE')
20 %HTML5AccessibleGraphSupported
21 ENCODING='utf-8'
22 STYLE=HtmlBlue
23 NOGTITLE
24 NOGFOOTNOTE
25 GPATH=&sasworklocation
26 ;
NOTE: Writing HTML5(EGHTML) Body file: EGHTML
27
28 proc product_status; run;

For Base SAS Software ...
Custom version information: 9.4_M6
Image version information: 9.04.01M6P110718
For SAS/STAT ...
Custom version information: 15.1
For SAS/GRAPH ...
Custom version information: 9.4_M6
For SAS Integration Technologies ...
Custom version information: 9.4_M6
For High Performance Suite ...
Custom version information: 2.2_M7
For SAS/ACCESS Interface to PC Files ...
Custom version information: 9.4_M6
For SAS/ACCESS Interface to ODBC ...
Custom version information: 9.4_M6
For SAS/ACCESS Interface to R/3 ...
Custom version information: 4.4_M4
NOTE: PROCEDURE PRODUCT_STATUS used (Total process time):
real time 0.14 seconds
cpu time 0.03 seconds

29
30 %LET _CLIENTTASKLABEL=;
31 %LET _CLIENTPROCESSFLOWNAME=;
32 %LET _CLIENTPROJECTPATH=;
33 %LET _CLIENTPROJECTPATHHOST=;
34 %LET _CLIENTPROJECTNAME=;
2 The SAS System 10:43 Friday, October 21, 2022

35 %LET _SASPROGRAMFILE=;
36 %LET _SASPROGRAMFILEHOST=;
37
38 ;*';*";*/;quit;run;
39 ODS _ALL_ CLOSE;
40
41
42 QUIT; RUN;
43

SASKiwi
PROC Star

That confirms what you have already stated. Lets wait to see what Tech Support says.

Patrick
Opal | Level 21

If I understand this right then as per the link you share SAS states:
"...The workaround is to use a version of the SAP NetWeaver RFC SDK that is earlier than Patch Level 8."

 

The fix list shows you that the issue has been reported in M6 but there is no fix yet.

Patrick_1-1665831326429.png

 

I understand your dilemma with SAP telling you to not revert to an earlier version of the NetWeaver RFC libraries.

 

Bit of a dilemma here. 

 

If you've got a written "not recommended" statement from SAP then I suggest you contact SAS Tech Support directly, share the info from SAP and ask for advice how to resolve this. 

 

Sajid01
Meteorite | Level 14

The appropriate action would be to open a ticket with SAS Technical Support. You will surely get the needed assistance.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

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.

Discussion stats
  • 5 replies
  • 832 views
  • 0 likes
  • 4 in conversation