SUPPORT

Select Your Region

Visit the Cary, NC, US corporate headquarters site

Americas

Europe

Middle East & Africa

Asia Pacific

View our worldwide contacts list for help finding your region

Americas

Europe

Middle East & Africa

Asia Pacific

Sign In

Get access to My SAS, trials, communities and more.

Sign Out

Get access to My SAS, trials, communities and more.

SAS Sites

sas.com
Support
Blogs
Communities
Developer
Curiosity
Videos

Documentation

Learn
Brand
PartnerNet
Merchandise
SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 53172: An exception might be generated when you attempt to open the Store Groups detail view or the Size Profiling Home view

DetailsHotfixAboutRate It

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:

  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).
  2. 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.
  3. Create another profiling project at a child node where no store grouping rules were defined. Generate profiles on the child profiling project.
  4. View store groups detail for the parent profiling project by clicking on store groups count from the Size Sets view.
  5. View store groups detail for the child profiling project by clicking on store groups count from the Size Sets view.
  6. The exception is generated when you select Size Profiling Home from the View menu.

Sequence of steps #2:

  1. Select Size Profiling Home from the View menu.
  2. View store groups detail for the above parent profiling project by clicking on store groups count from the Size Sets view.
  3. 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 FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Size ProfilingLinux for x643.2_M49.3 TS1M2
64-bit Enabled AIX3.2_M49.3 TS1M2
Microsoft® Windows® for x643.2_M49.3 TS1M2
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.