cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
MariaD
‎09-23-2024
  • 483 Posts
  • 48 Likes Given
  • 20 Solutions
  • 55 Likes Received

Re: SAS Workspace: stop accepting client connections

by Barite | Level 11 in Administration and Deployment
‎11-06-2018 02:43 PM
‎11-06-2018 02:43 PM
Thanks @SASKiwi, we have an open ticket but until now we don’t have any conclusions... ... View more

Re: SAS Workspace: stop accepting client connections

by Barite | Level 11 in Administration and Deployment
‎11-06-2018 08:31 AM
‎11-06-2018 08:31 AM
Hi @SASKiwi,   A new update on this topic. After we reviewed a lot of workspace logs, we find the following messages:   2018-11-01T09:39:20,294 DEBUG [00000008] 4:user - IOM LOGIC DOSMGetClassImage(): image-name=sasoptsv 2018-11-01T09:39:20,300 DEBUG [00000008] 4:user - IOM RETURN W_OK=DOSMGetClassImage(): componentLD=00002AE1EFB272E0 2018-11-01T09:39:20,415 DEBUG [00000008] 4:user - IOM LOGIC DOSMGetClassImage(): image-name=sasfsv 2018-11-01T09:39:20,418 DEBUG [00000008] 4:user - IOM RETURN W_OK=DOSMGetClassImage(): componentLD=00002AE1EFB27620 2018-11-01T11:39:20,934 INFO [00003239] 4:user - A connection reset indicates the peer has closed their connection to this session. This session will remove the peer from its set of active peers. 2018-11-01T11:39:20,934 INFO [00003239] 4:user - The Bridge Protocol Engine Socket Access Method was unable to read peer data. ... 2018-11-01T11:39:20,940 INFO [00000009] :user - NOTE: SAS Institute Inc., SAS Campus Drive, Cary, NC USA 27513-2414 2018-11-01T11:39:20,940 INFO [00000009] :user - NOTE: The SAS System used (Total process time): 2018-11-01T11:39:20,940 INFO [00000009] :user - real time 2:00:02.12 2018-11-01T11:39:20,940 INFO [00000009] :user - cpu time 1.12 seconds   If you see, in this first case we have a gap of 2h without any process. Any idea why this happen?   In this other workspace server log, we have a similar situation:   2018-11-01T14:20:58,254 DEBUG [00000004] 4:user - IOM LOGIC VOIMapWrcodeToWoiStatus() Mapping error severity wrcode: 0x80403808 2018-11-01T14:20:58,255 DEBUG [00000004] 4:user - IOM LOGIC VOIMapWrcodeToWoiStatus() Mapping error severity wrcode: 0x80403808 2018-11-01T14:20:58,256 DEBUG [00000004] 4:user - IOM LOGIC VOIMapWrcodeToWoiStatus() Mapping error severity wrcode: 0x80403808 2018-11-01T14:20:58,258 DEBUG [00000004] 4:user - IOM LOGIC VOIMapWrcodeToWoiStatus() Mapping error severity wrcode: 0x80403808 2018-11-01T14:20:58,263 DEBUG [00000004] 4:user - IOM LOGIC VOIMapWrcodeToWoiStatus() Mapping error severity wrcode: 0x80403808 2018-11-01T14:20:58,286 DEBUG [00000004] 4:user - IOM LOGIC VOIMapWrcodeToWoiStatus() Mapping error severity wrcode: 0x80403808 2018-11-01T14:20:58,294 DEBUG [00000004] 4:user - IOM LOGIC VOIMapWrcodeToWoiStatus() Mapping error severity wrcode: 0x80403808 2018-11-01T14:20:58,296 DEBUG [00000004] 4:user - IOM LOGIC VOIMapWrcodeToWoiStatus() Mapping error severity wrcode: 0x80403808 2018-11-01T14:20:58,320 DEBUG [00000004] 4:user - IOM LOGIC VOIMapWrcodeToWoiStatus() Mapping error severity wrcode: 0x80403808 2018-11-01T14:20:58,332 DEBUG [00000004] 4:user - IOM LOGIC VOIMapWrcodeToWoiStatus() Mapping error severity wrcode: 0x80403808 2018-11-01T14:20:58,494 DEBUG [00000012] 4:user - IOM LOGIC DOSMGetClassImage(): image-name=sasbins 2018-11-01T14:20:58,495 DEBUG [00000012] 4:user - IOM RETURN W_OK=DOSMGetClassImage(): componentLD=00002B0027F56840 2018-11-01T14:31:29,136 INFO [00000009] :user - 20 The SAS System 14:18 Thursday, November 1, 2018 2018-11-01T14:31:29,136 INFO [00000009] :user - 2018-11-01T14:31:29,136 INFO [00000009] :user - NOTE: SAS Institute Inc., SAS Campus Drive, Cary, NC USA 27513-2414 2018-11-01T14:31:29,136 INFO [00000009] :user - NOTE: The SAS System used (Total process time): 2018-11-01T14:31:29,136 INFO [00000009] :user - real time 12:37.75 2018-11-01T14:31:29,136 INFO [00000009] :user - cpu time 1:21.73   In this second case, we have a gap of 12 minutos and a message about "Mapping error severity wrcode". Any idea?   Regards, ... View more

Re: SAS EG | Exporting using PCFF

by Barite | Level 11 in SAS Enterprise Guide
‎10-31-2018 05:36 PM
‎10-31-2018 05:36 PM
Hi @SASKiwi,   We open the windows explorer on PCFF's machine and we can access the network drive without any problem, using "\\ machine \ folder" or "Z: \ folder". Do you think could be a permission problem to access network drive? Would be better to add the SERVERUSER and SERVERPASS options on PROC IMPORT?   Regards,     ... View more

Re: SAS EG | Exporting using PCFF

by Barite | Level 11 in SAS Enterprise Guide
‎10-31-2018 03:04 PM
‎10-31-2018 03:04 PM
Hi @tomrvincent, you mean Excel for example? We don't tried but I'll test and let you know. ... View more

SAS EG | Exporting using PCFF

by Barite | Level 11 in SAS Enterprise Guide
‎10-31-2018 02:21 PM
‎10-31-2018 02:21 PM
Hi Folks,   We are using SAS PCFF to export to local disk in SAS EG. We use a code like below:   proc export data=sashelp.class         dbms=ACCESSCS          outtable="Class" replace;        database="C:\temp\Test.accdb";       server="xx.xx.xx.xx";       port=9621; run;   If we export to local disk, C or D, the codes execute fine. But if we replace to network drive (\\computer\folder or Z:\folder) the following error appear:   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           1.23 seconds       cpu time            0.01 seconds   Of course the user has permission to write in the network drive. There is any limitations to export to network drive (mapped or not)?   Regards,  ... View more

Re: SAS Workspace: stop accepting client connections

by Barite | Level 11 in Administration and Deployment
‎10-30-2018 06:26 PM
‎10-30-2018 06:26 PM
Thanks, @SASKiwi. As I mentioned, we are working with SAS support but until now we don't be able to identify what is the problem. I'm share here to validate if somebody has encountered this kind of problem before.   On Metadata log there is no relevant messages or details.   I have a question, last week our country supposes to change to daylight saving time but the date was changed for two weeks laters. I understand SAS use the time from OS but what about the Java used for SAS (JRE)? There is any change this problem will related with time zone defined on Java?   Regards,   ... View more

Re: SAS Workspace: stop accepting client connections

by Barite | Level 11 in Administration and Deployment
‎10-30-2018 12:20 PM
‎10-30-2018 12:20 PM
Hi Folks,    I opened a tech support about this issue, but until now we don't have success to restore the normal operation.   Updating on what is going on. For sometimes the server working fine and it process normally. After a time, the server stop to accept new connection and now nobody can login using SASEG or SAS MC. The connection with metadata, to validate the user permissions, returns timeout. Although we were able to connect to metadata using SAS code running directly over the server.   After that, we restarted again SAS services and now the environment is working normal again. But we staying in some kind of looping, normal for a couple of hours and then everything again.   Any suggestion? ... View more

Re: SAS Workspace: stop accepting client connections

by Barite | Level 11 in Administration and Deployment
‎10-29-2018 04:55 PM
‎10-29-2018 04:55 PM
Thanks. Today SAS environments works fine until we started the scheduling process. We use LSF. After 2h, appear the following message:   IntiPaths(): Cannot access job <xxxxx> spool directory /sasbin/Platform_Suite/Lsf/spool. Permission denied.   I verify the permission for /sasbin/Platform_Suite/Lsf/spool and is set to "rwxrwxr-x".   Any suggestion?   Regards, ... View more

Re: SAS Workspace: stop accepting client connections

by Barite | Level 11 in Administration and Deployment
‎10-29-2018 09:32 AM
‎10-29-2018 09:32 AM
Hi @PaulHomes,   Yes, the server is up and running, and the object spawner is running too (verified using "sas.servers status" script). As you mentioned, we have several ObjectSpawner created.   For example, in this exactly moment, nobody can't access SASApp from SAS EG. SAS EG open and validate the user in Metatadata without any problem, but when user tried to open SASApp connection, the application stay processing and nothing happen.    Any suggestion what is going on? ... View more

SAS Workspace: stop accepting client connections

by Barite | Level 11 in Administration and Deployment
‎10-28-2018 02:45 PM
1 Like
‎10-28-2018 02:45 PM
1 Like
Hi folks,   We have SAS 9.4 TSM3 installed on a grid (Linux server). Our users uses SAS EG as primary client and some of our users uses SAS EM too. Last week, some strange behaviour on the server started. The server start normally, but after some time (in some case 2h, in other 6h, we don't find any pattern over the time), the server stop to accept new connections and freeze the existing ones. The only solutions is restart the services. As mentioned, in some case the server works fine for 3h, in other for 6h, etc.   In ObjectSpawner log, I find the following message:   2016-08-26T23:38:08,500 INFO [00000067] :sas - Attempt to connect to peer iom://mor-sasprd04.server:11013;;noredirect,classfactory=6A829631-BE4A-4CFF-82F6-B378705DF34C,user=,encr=SASProprietary,encrlvl=credentials/ for cluster Guide_CRM - Logical Pooled Workspace Server (A5RC0EOG.AW000023) failed with exception <?xml version="1.0" ?><Exceptions><Exception><SASMessage severity="Error">A connection refused usually indicates the target server is not active. Or, if active, it may be listening on a different port or service.</SASMessage></Exception><Exception><SASMessage severity="Error">The Bridge Protocol Engine Socket Access Method was unable to connect to host mor-sasprd04.server, port 11013.</SASMessage></Exception><Exception><SASMessage severity="Error">The TCP/IP tcpSockConnect() support routine failed with error 111 (The connection was refused.).</SASMessage></Exception></Exceptions>.   Searching over SAS Notes, I find the following notes:   When you encounter this problem, you must stop and restart the SAS Object Spawner to release the connections. However, over time as new SAS Pooled Workspace Servers are started and stopped many times, the sockets become slowly exhausted again. You might be able to work around this problem by setting the Inactive process shutdown timeout to 0 for the SAS Pooled Workspace Server. Then, the SAS Pooled Workspace Servers will be started and not shut down so that only a few extra sockets are used.   Anyone has encounter similar problem? Anyone knows if the message found in SAS Notes apply to this problem?   Regards, ... View more

SAS EG 7.1 - Output tables

by Barite | Level 11 in SAS Enterprise Guide
‎10-26-2018 09:32 AM
‎10-26-2018 09:32 AM
Hi Folks,   Normally, when you create more than one table on any process, the output tab show all tables generated. For example, if we created 3 tables, the output show "Output (3)" and we can navigate for any of the results.   For some strange reason, in one of our SAS EG installation, when I create more than one table, the output tab show only one of them. But if I verify the log, I could see that all tables were created ok. Any idea why this happen?   Regards, ... View more

SAS ECL + Regulatory Content for IFRS 9 | Includes Miner?

by Barite | Level 11 in SAS Risk Management
‎10-23-2018 02:41 PM
‎10-23-2018 02:41 PM
Hi Folks,   Anyone can inform me if the SAS ECL with SAS Regulatory Content for IFRS 9 includes SAS Enterprise Miner to development predictive models?   Regards, ... View more

Re: Oracle Libname: special chars

by Barite | Level 11 in SAS Programming
‎10-23-2018 08:14 AM
‎10-23-2018 08:14 AM
So to solves the problem I need to set the NLS_LANG environment variable in my SAS server, That is correct? ... View more

Oracle Libname: special chars

by Barite | Level 11 in SAS Programming
‎10-23-2018 07:25 AM
‎10-23-2018 07:25 AM
Hi Folks,   I use some Oracle tables that I access from a libname (Access to Oracle). Some of my Oracle's tables has special characters inside (not in column or table name but in the data values). Por example, I have a column call City and inside has values like "São Paulo". When I access the table from Oracle client, I saw the value "São Paulo" correctly. But when access from SAS EG, the value appear something like "S?o Paulo".   There is any option I can use on libname statement to see the correct characters in SAS EG?   I undestand that the option PRESERVE_COLUMN_NAME is only when the problem is on columns name, not on the values. And the option PRESERVE_TAB_NAMES is only for problems with the name of the table.   Regards, ... View more
Contact Me
Online Status
Offline
Date Last Visited
‎09-23-2024 06:47 PM
Group Hubs for MariaD
View All
Likes given to
Likes from
Quick links