I want to report an issue with our SAS stored procedures exposed via the SAS BI WS as an rest API which we are currently not able to solve.   The issue is as follows:   We are currently exposing 4 APIs via the SAS BI WS to other application within our organisation. These APIs are consumed via an API proxy gateway, meaning that the consumer will call the API gateway, and that will in turn call the endpoint of the web service on our server running SAS.   Three out of four APIs are built by using x-www-form-urlencoded key-value pairs. The keys are defined via de stored procedure definition as input prompts. The problem arises when one of the keys is spelled wrong (i.e in the above case countryCode1 instead of countryCode).   The stored procedure runs in to error ( as expected) and an HTTP 500 message is returned. However, when a new call is made to the API proxy with the correct parameters, or even a call to one of the other APIs that we host on the server, still http 500 is returned, even though the input is correct. The stored procedure is never executed nor produces any log ( so it goes wrong before that)   I have done some analysis on the SAS server logs and access logs (path = /opt/sas/local/config/web/Lev1/Web/WebAppServer/SASServer1_1/logs) , and the calls do seem to be reaching our server as I can see entries in our logs (so the calls are not stopped at the proxy).   What I do notice is when the second call ( with correct parameters) is made: Server.log / Catelina.out:   2024-09-19 15:58:09,321 ERROR (tomcat-http--32) [org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/SASBIWS].[mvc]] Servlet.service() for servlet [mvc] in context with path [/SASBIWS] threw exception [Request processing failed; nested exception is com.sas.svcs.security.authentication.client.TicketCreationException: Unable to acquire ticket: <400 Bad Request,{Date=[Thu, 19 Sep 2024 13:58:09 GMT], Server=[Apache], X-UA-Compatible=[IE=edge], Content-Length=[0], X-Frame-Options=[SAMEORIGIN], X-XSS-Protection=[1; mode=block], X-Content-Type-Options=[nosniff],     To me it seems like that whenever a bad call was made (with wrong input parameters), it blocks the connection from that consumer (the proxy in this case) and is no longer able to issue a ticket from SASLogon ( HTTP 400 response from SASlogon – “Unable to acquire ticket”).   Whenever I make a call via postman directly on our server endpoint (so circumventing the proxy) it ‘resets’ and the proxy will again be able to call the SAS BI WS as normal. Could you please assist here on what we can do to allow new correct calls from a consumer after a wrong request was made?   FYI we are using the following setup: SAS 9.4 M7( will be upgraded to M8 soon) running on Linux RHEL 6.8 (this will be upgraded to 8.10)   ... View more

In our SAS environment, SAS Stored process server has 9 multibridge connection. Maximum cost=500 session cost=1, context cost =100, cost per client=1 Hence according to theory, 4 requests can execute on one multibridge connection simultaneously. So total of (9*4=36) requests should execute in parallel on the SAS Stored process server.   But when I open 12 tabs in a browser and hit one SAS stored process URL at the same time(with a very time gap of miliiseconds), what i observe is that, only 6 requests get executed at a time. and when 6 request completes its execution then next 6 requests gets executed. In the STP log, it is observed that all 12 requests are being submitted only on  6 multibridge connections port. So my question is, why not all 12 request to SAS Stored process from a single user are not executed at the same time on SAS STP server? ... View more

In our SAS environment, SAS Stored process server has 9 multibridge connection. Maximum cost=500 session cost=1, context cost =100, cost per client=1 Hence according to theory, 4 requests can execute on one multibridge connection simultaneously. So total of (9*4=36) requests should execute in parallel on the SAS Stored process server.   But when I open 12 tabs in a browser and hit one SAS stored process URL at the same time(with a very time gap of miliiseconds), what i observe is that, only 6 requests get executed at a time. and when 6 request completes its execution then next 6 requests gets executed. In the STP log, it is observed that all 12 requests are being submitted only on  6 multibridge connections port. So my question is, why not all 12 request to SAS Stored process from a single user are not executed at the same time on SAS STP server? ... View more

While using file writer transformation to export data in csv file with semicolon as delimiter, missing values are exported as dot. but instead there should be two consecutive delimiters. Any suggestion to get the expected result?   ... View more

The ddmmyyp. format is used for one of the date field in information map and wrs report is based on that info map. The wrs report was working fine earlier. Suddenly we have started getting error while opening wrs report as Missing Report Element. ... View more

Hi,   I am working on SAS 9.04 SPDS platform. When i run the query in SAS EG which extract data from SQL server table below are the time statistics given in the log :   NOTE: PROCEDURE SQL used (Total process time):       real time           3:03.14       cpu time            1.97 seconds     Please let me know, the CPU time mentioned here of 1.97 seconds, does it include the actual CPU time of SQL server + SAS Server? ... View more

Hi,   I need to define pdf templates in SAS. Data will be populated in these templates from source database. I need to understand, can we create complex pdf template in SAS. If yes, how do we do this? I have attached sample pdf template report. ... View more

Hi,   I am getting below error while trying to open SAS WRS report. "Relasjonsspørringer som inneholder over 31 kategorier, støttes ikke med summering eller brøker av summer." Information map is been used as an input to WRS report srx. In the information, I have added one new data item and when i select single column in it, the report works fine. But the moment I put an expression in that data item, report shows an error. Find the attachment for details.   Please let me know what is the problem here. ... View more

Hi All,   When I am running below peice of code, I am getting error message : /****Code *****/ %put %str(NOTE: Creating indexes in Parallel...); proc datasets lib = VL00 nolist; modify VL0004_005D_Employee_Sensitive (asyncindex=YES); index create VL0004_004D_Employee_Sk ; index create Employee_Id ; index create Person_Id ; quit;     /*****Log ********/ MPRINT(ETLS_LOADER): ; NOTE: Creating indexes in Parallel... MPRINT(ETLS_LOADER): proc datasets lib = VL00 nolist; MPRINT(ETLS_LOADER): modify VL0004_005D_Employee_Sensitive (asyncindex=YES); MPRINT(ETLS_LOADER): index create VL0004_004D_Employee_Sk ; NOTE: Because ASYNC operations create indexes in parallel, the status for all defined indexes will be determined at closing time. NOTE: Simple index VL0004_004D_Employee_Sk has been defined. MPRINT(ETLS_LOADER): index create Employee_Id ; ERROR: Specified resource already exists. MPRINT(ETLS_LOADER): index create Person_Id ; MPRINT(ETLS_LOADER): quit; 　 NOTE: Statements not processed because of errors noted above. NOTE: The SAS System stopped processing this step because of errors. NOTE: SAS set option OBS=0 and will continue to check statements. This might cause NOTE: No observations in data set. NOTE: PROCEDURE DATASETS used (Total process time): real time 1.55 seconds cpu time 0.00 seconds ... View more

Hi All,   When I am running below peice of code, I am getting error message : /****Code *****/ %put %str(NOTE: Creating indexes in Parallel...); proc datasets lib = VL00 nolist; modify VL0004_005D_Employee_Sensitive (asyncindex=YES); index create VL0004_004D_Employee_Sk ; index create Employee_Id ; index create Person_Id ; quit;     /*****Log ********/ MPRINT(ETLS_LOADER): ; NOTE: Creating indexes in Parallel... MPRINT(ETLS_LOADER): proc datasets lib = VL00 nolist; MPRINT(ETLS_LOADER): modify VL0004_005D_Employee_Sensitive (asyncindex=YES); MPRINT(ETLS_LOADER): index create VL0004_004D_Employee_Sk ; NOTE: Because ASYNC operations create indexes in parallel, the status for all defined indexes will be determined at closing time. NOTE: Simple index VL0004_004D_Employee_Sk has been defined. MPRINT(ETLS_LOADER): index create Employee_Id ; ERROR: Specified resource already exists. MPRINT(ETLS_LOADER): index create Person_Id ; MPRINT(ETLS_LOADER): quit; 　 NOTE: Statements not processed because of errors noted above. NOTE: The SAS System stopped processing this step because of errors. NOTE: SAS set option OBS=0 and will continue to check statements. This might cause NOTE: No observations in data set. NOTE: PROCEDURE DATASETS used (Total process time): real time 1.55 seconds cpu time 0.00 seconds   ... View more