Pulling data from a Windows server (WELSFGO.NETIZENS.BANK-DSb.COM) to your SAS Application server using EG is likely to be a permissions problem, not a syntax one. Your ACCESSCS program syntax looks OK. I suggest you engage with your SAS administrator as they have likely been involved in setting up this approach. Confirming your server name, port and folder share details is a good start. If this is a first time test then you could be blocked by server firewall rules. Only your IT folks can help with that as they need to make a rule change. By default servers usually block all communication ports, then add a rule for each port where traffic is allowed. Ask about a firewall rule for port 7845  on both servers. ... View more

Here is wishing you all the best from the Southern Hemisphere. Many thanks for the heaps I've learnt from you over the years! ... View more

@Quentin - Thanks for pointing out the differences. I work in a Windows-only world currently so I'm not so familiar with linux-based data connections. Interesting to see that some file configuration is still required there. ... View more

@DrAbhijeetSafai  - This is a common issue with many SAS-type files. I suggest you try the instructions in this link: https://sas.service-now.com/csm?id=kb_article_view&sysparm_article=KB0036488  ... View more

Nice to know. It is also worth pointing out that for some database connections you can avoid DSNs entirely and define everything in your connection strings like so: libname sqllegno sqlsvr noprompt='Driver=SQLServer_Legacy;Address=machine2.reg.company.com,1433;Database=users; UID=myuser;PWD=mypass;' schema=myschema; This works well for SQL Server in my experience. ... View more

You would be best to work with Tech Support on this if you haven't opened a track already, as this is going to require some troubleshooting. The first error suggests that the Metadata Server service is down so I would start by looking at the Metadata Server logs. ... View more

@atesera  - Up to you where you put the %INCLUDE statements. My preference is to have them in a controlling SAS program - see @quickbluefish 's example earlier in this thread. ... View more

What version of EG is this? It works fine for me in EG 8.4. If you are on an older version you could try updating. Covered: Uncovered: I suggest you contact SAS Tech Support ... View more

Do LIB1 and LIB2 point to external databases by any chance? If so it is possible that SAS can't push the functions you are using and so is reading all data to SAS first before joining. What happens if you remove the TRIM and UPCASE functions? ... View more

There are probably more elegant ways but you could try this: data Have; input id date :yymmdd10. type; format date yymmdd10.; datalines; 1 2020-01-01 0 1 2018-07-06 0 2 2015-02-15 1 3 2020-02-01 0 3 2021-07-05 1 3 2021-08-09 0 4 2020-01-30 0 5 2018-10-10 1 5 2019-10-11 1 ; RUN; data onetype zerotype; keep id date type; merge Have (in = H1) Have (in = H2 where = (type2 = 1) keep = id type rename = (type = type2)) ; by id; retain onetype; if first.id then do; if H2 then onetype = 1; else onetype = 0; end; if onetype then output onetype; else output zerotype; run;   ... View more

Reorganising your data would make your report a lot easier: data have; input @1 Type $2. @5 Month monyy7. @12 Amount 6.; format month monyy7.; Year = year(month); datalines; A Jul2022 512284 A Jul2023 511247 A Jul2024 537950 A Aug2022 467846 A Aug2023 494399 A Aug2024 494519 A Sep2022 456741 A Sep2023 477914 A Sep2024 585883 A Oct2022 441665 A Oct2023 473957 A Oct2024 554541 A Nov2022 352226 A Nov2023 342704 A Nov2024 720150 A Dec2022 584206 A Dec2023 451450 A Dec2024 366774 B Jul2022 32906 B Jul2023 32906 B Jul2024 92393 B Aug2022 35597 B Aug2023 38010 B Aug2024 40322 B Sep2022 36720 B Sep2023 42826 B Sep2024 36455 B Oct2022 51224 B Oct2023 43689 B Oct2024 46408 B Nov2022 35151 B Nov2023 52637 B Nov2024 44017 C Jul2022 346722 C Jul2023 308021 C Jul2024 293111 C Aug2022 328668 C Aug2023 304660 C Aug2024 270731 C Sep2022 683099 C Sep2023 576012 C Sep2024 527964 C Oct2022 992834 C Oct2023 811538 C Oct2024 751706 C Nov2022 910997 C Nov2023 818528 C Nov2024 748760 C Dec2022 724850 C Dec2023 552243 C Dec2024 749465 ; run; proc report data=have nowd; column Type year Amount, Month ; define Type/ group style=header; define Year / group; define Month / across style=header order=internal format = monname3.; define Amount / ' ' sum; run;   ... View more

The question is what has changed in the last week to cause this problem? Are other reports working OK and this is the only problem one or are other reports affected? I suggest you check with your SAS administrator regarding any known problems. ... View more

I ran into this exact problem myself. Since I knew I had a valid certificate as it was working in SAS web apps, I just exported the certificate out of the MS Edge browser using the Certificate Viewer and applied it successfully in Deployment Manager. That workaround was provided by Tech Support. ... View more

Please post your program in that case. ... View more

What does your SAS log show? That your PROC SQL query never completes or something else? My guess is that the query never completes and that EG is prompting you if you want to continue running it or not.   What type of solution do you want? For the message not to pop up every 60 minutes, which I suspect might be an EG setting, or for your query to run faster so it completes in less than 60 minutes avoiding the message? ... View more