Problem Note 53172: An exception might be generated when you attempt to open the Store Groups detail view or the Size Profiling Home view
 |  |  |  |  |
You might encounter the following exception when you attempt to open the Store Groups detail view or the Size Profiling Home view in SAS® Size Profiling:
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) at org.eclipse.swt.SWT.error(SWT.java:3777) at org.eclipse.swt.SWT.error(SWT.java:3695) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3800) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.sas.solutions.di.studio.runtime.internal.StudioApplication.start(StudioApplication.java:187) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) at org.eclipse.equinox.launcher.Main.run(Main.java:1450) at org.eclipse.equinox.launcher.Main.main(Main.java:1426) Caused by: java.lang.NullPointerException at com.sas.solutions.di.studio.prf.sizeset.storegroups.ui.SizeSetStoreGroupsDetailComposite.refreshStoreGroupRuleCompositeForDeletedOrModifiedRule(SizeSetStoreGroupsDetailComposite.java:481) at com.sas.solutions.di.studio.prf.sizeset.storegroups.ui.StoreGroupsVCP.refreshHeader(StoreGroupsVCP.java:1274) at com.sas.solutions.di.studio.prf.sizeset.storegroups.ui.StoreGroupsVCP.refreshHeader(StoreGroupsVCP.java:1251) at com.sas.solutions.di.studio.prf.sizeset.storegroups.ui.StoreGroupsVCP.access$14(StoreGroupsVCP.java:1230) at com.sas.solutions.di.studio.prf.sizeset.storegroups.ui.StoreGroupsVCP$6.modelChangedUIThread(StoreGroupsVCP.java:499) at com.sas.solutions.di.studio.mvc.cm.CategorizedModelListenerSet$2.run(CategorizedModelListenerSet.java:93) at com.sas.solutions.di.commons.ui.swt.WidgetUtils$3.run(WidgetUtils.java:803) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133) ... 23 more
The problem occurs if you follow one of the two sequences of steps below:
Sequence of steps #1:
- Define a store grouping rule at a parent node (for example, at department level) and at some of the child nodes (for example, at subclass level).
- Create a profiling project at the parent node where the parent store grouping rule was defined and apply the store grouping rule to the project. Generate profiles on the parent profiling project.
- Create another profiling project at a child node where no store grouping rules were defined. Generate profiles on the child profiling project.
- View store groups detail for the parent profiling project by clicking on store groups count from the Size Sets view.
- View store groups detail for the child profiling project by clicking on store groups count from the Size Sets view.
- The exception is generated when you select Size Profiling Home from the View menu.
Sequence of steps #2:
- Select Size Profiling Home from the View menu.
- View store groups detail for the above parent profiling project by clicking on store groups count from the Size Sets view.
- The exception is generated when you view store groups detail for the above child profiling project by clicking on store groups count from the Size Sets view.
There are no workarounds for this issue.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Size Profiling | Linux for x64 | 3.2_M4 | 9.3 TS1M2 | ||
| 64-bit Enabled AIX | 3.2_M4 | 9.3 TS1M2 | ||||
| Microsoft® Windows® for x64 | 3.2_M4 | 9.3 TS1M2 | ||||
A fix for this issue for SAS Size Optimization 3.2_M4 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/P21.html#53172A fix for this issue for SAS Revenue Optimization 5.2_M4 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/P20.html#53172| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2014-06-23 16:44:45 |
| Date Created: | 2014-06-09 11:23:38 |