SAS Enterprise Miner 14.3 - Corrupted Diagram

MariaD — Tue, 11 Dec 2018 18:53:15 GMT

Hi Folks,

One of our users has he SAS EM diagram corrupted. While it was executing the following error appear:

java.lang.NullPointerException
    @ com.sas.analytics.eminer.impl.MiningDGraphImpl.connect(MiningDGraphImpl.java:155)
    @ com.sas.analytics.eminer.impl.MiningDGraphImpl.<init>(MiningDGraphImpl.java:59)
    @ com.sas.analytics.eminer.impl.MiningWorkspaceImpl.setLayout(MiningWorkspaceImpl.java:1092)
    @ com.sas.analytics.eminer.impl.MiningWorkspaceImpl.open(MiningWorkspaceImpl.java:1059)
    @ com.sas.analytics.eminer.impl.MiningWorkspaceImpl.open(MiningWorkspaceImpl.java:992)
    @ com.sas.analytics.eminer.visuals.MainDesktop.open(MainDesktop.java:727)
    @ com.sas.analytics.eminer.visuals.MainDesktop.execute(MainDesktop.java:324)
    @ com.sas.analytics.eminer.visuals.actions.WorkspaceAction.actionPerformed(WorkspaceAction.java:300)
    @ com.sas.analytics.eminer.visuals.actions.EMAction.execute(EMAction.java:22)
    @ com.sas.analytics.eminer.visuals.ProjectTree.doubleClick(ProjectTree.java:420)
    @ com.sas.analytics.eminer.visuals.ProjectTree.maybeShowPopup(ProjectTree.java:620)
    @ com.sas.analytics.eminer.visuals.ProjectTree$DnDJTreeMouseAdapter.mouseClicked(ProjectTree.java:60)
    @ java.awt.AWTEventMulticaster.mouseClicked(AWTEventMulticaster.java:270)
    @ java.awt.Component.processMouseEvent(Component.java:6519)
    @ javax.swing.JComponent.processMouseEvent(JComponent.java:3320)
    @ java.awt.Component.processEvent(Component.java:6281)
    @ java.awt.Container.processEvent(Container.java:2230)
    @ java.awt.Component.dispatchEventImpl(Component.java:4872)
    @ java.awt.Container.dispatchEventImpl(Container.java:2288)
    @ java.awt.Component.dispatchEvent(Component.java:4698)
    @ java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4840)
    @ java.awt.LightweightDispatcher.processMouseEvent(Container.java:4509)
    @ java.awt.LightweightDispatcher.dispatchEvent(Container.java:4430)
    @ java.awt.Container.dispatchEventImpl(Container.java:2274)
    @ java.awt.Window.dispatchEventImpl(Window.java:2718)
    @ java.awt.Component.dispatchEvent(Component.java:4698)
    @ java.awt.EventQueue.dispatchEventImpl(EventQueue.java:747)
    @ java.awt.EventQueue.access$300(EventQueue.java:103)
    @ java.awt.EventQueue$3.run(EventQueue.java:706)
    @ java.awt.EventQueue$3.run(EventQueue.java:704)
    @ java.security.AccessController.doPrivileged(Native Method)
    @ java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
    @ java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
    @ java.awt.EventQueue$4.run(EventQueue.java:720)
    @ java.awt.EventQueue$4.run(EventQueue.java:718)
    @ java.security.AccessController.doPrivileged(Native Method)
    @ java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
    @ java.awt.EventQueue.dispatchEvent(EventQueue.java:717)
    @ java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:218)
    @ java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:133)
    @ java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:122)
    @ java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:118)
    @ java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:110)
    @ java.awt.EventDispatchThread.run(EventDispatchThread.java:91)

After that, it's not possible to open the diagram, but other diagrams in the same SAS EM project opens without a problem.

This behaviour happens twice in the last days. Now, we enabled the DEBUG option on SAS Enterprise Miner log. Any idea why this happens? We have SAS EM 14.3 running on AIX (9.4M5).

Regards,

Re: SAS Enterprise Miner 14.3 - Corrupted Diagram

DougWielenga — Tue, 15 Jan 2019 21:50:07 GMT

The java error message you are encountering is a generic one that can appear for various reasons (even though it is uncommon). If it is only an issue in a particular diagram, you might consider building a new diagram (or a new project). If you are encountering the error in different projects, there might be a configuration issue (e.g. did your client update to a newer version of Java which isn't supported?). If building a new diagram in a new project does not address the problem, you will likely need to contact SAS Technical Support.

When contacting SAS Technical Support, you will likely be asked questions such as:

1. Is this happening with all users or with just one user?

2. Is this happening with all data sources or just certain data sources?

3. Are their certain steps you are performing whenever this error occurs?

4. When is the last time you have restarted the SAS services/sessions on your server?

5. Can you reproduce the error in a new project and diagram?

You might also check on whether you are running out of Java memory and/or allotted memory for the user. Usually, you can overcome problematic nodes by just dragging in a new node, and you can overcome problematic diagrams by building a new diagram. It is important not to import a corrupted diagram when testing building a new diagram as their might be artifacts associated with the previously used diagrams that are carried over.

Hope this helps!

Doug

topic Re: SAS Enterprise Miner 14.3 - Corrupted Diagram in SAS Data Science

SAS Enterprise Miner 14.3 - Corrupted Diagram

Re: SAS Enterprise Miner 14.3 - Corrupted Diagram