Your friend is also using EG?  And connecting EG to the same SAS server as you are using?  If you are using different SAS servers then there might be differences in how they are setup.  Perhaps as simple as different options, like VALIDVARNAME or VALIDMEMNAME.   Can you see the tables if you use SAS code , like PROC CONTENTS, instead of the whatever GUI buttons you were clicking on? ... View more

Hi there @Riana,   alright, so what I can see here is the following:   Your libname to a dsn ImpalaJ I cannot see it defined anywhere else. The odbc.ini, it should be most probably in the same location as the odbcinst.ini, since one is related to the other. The odbc,ini file will actually have the configuration to your database: host, port, schema, and other details. You will also need to export the variable for ODBC and ODBCINST   In general, i think your first objective would be to focus on testing the Impala connection OUTSIDE from SAS, from the Linux command line. This should help you, hopefully:   https://www.cloudera.com/documentation/enterprise/5-11-x/topics/impala_odbc.html http://doc.mapr.com/display/MapR/Configure+the+MapR+Impala+ODBC+Driver+for+Linux+and+Mac+OS+X   Once you can validate connections from Linux to Impala databases and query them, you can move forward to the next step: to query them from SAS. ... View more

Hi @Riana,   I think it could be a good idea to get more information on what happens when you save the flow/resonsibilities.   You can do it with the console mode of SAS Management Console and/or running SMC on debug mode:   http://support.sas.com/kb/43/157.html   Could you do this and check if there is any error when you save it? ... View more

Hi Riana,   Most likely what is happening is you're trying to open a project in SAS Enterprise Miner that isn't the right file type (I know I've gotten this error myself before!). The folder where you saved your project should have the following folders and files in it:   I just navigated to where my project was saved on my machine, "C:\users\jess\EMTest\Project", and those folders appeared. Click the file "project.emp" to open the Enterprise Miner project.  Enterprise Miner projects will always have this name and filetype: "project.emp".   If you are still get the error "Please select another one. The current selection is not a mining project", feel free to open up a Technical Support track and we'd be happy to help you out further  Here's the link to open a track: http://support.sas.com/ctx/supportform/createForm     Hope this helps!   Jess Mayo SAS Technical Support ... View more

Hello @Riana,   the slowness depends on many things, but I would make my first bet that it is slow just due to Java - JVM boundaries that are reached. Here is what I would do, for starters:   0. Check if any non-SAS service/process is consuming your server resources. If any, manage it to give resources back to SAS. 1 . I would restart the middle tier, and before starting the services, I would clean/archive the temporary files (SASServerX_X\work \temp and \log) 2. Once it is restarted, if performance is still slow, I would recommend you to clean/archive your audit tables in WIP database ( http://support.sas.com/kb/58/599.html ), then restart the middle-tier.     ... View more

I would appreciate if someone answer this question. Thanks. ... View more

Agreed with @JuanS_OCS that you can only define one "Logical" IOM server type (Workspace, Stored Process, Pooled Workspace) per server context (SASApp).  However, you can define multiple server components within each Logical server definition.  Based on what you have said, I'm guessing you have two Workspace Server components defined within the single Logical Workspace definition - is that correct?  This type of configuration is generally performed to configure load balancing across multiple physical SAS servers and would require a shared file system between the two servers in order to have a shared location for data and program files.   If you don't have a shared file system for your SAS servers, then you should define an additional server context (e.g. SASApp2) for the second Workspace Server component. You can control access to each server either through metadata permissions (by granting ReadMetadata access appropriately), or you can instruct your SAS users to select one server context vs. the other from within their SAS client application based on the type of work they are doing, or some other use case you may have.   ... View more

It's also a small possibility somebody didn't install it correctly, especially if you did an upgrade at some point. ... View more