Showing results for 
Search instead for 
Did you mean: 

Design Studio 1.5 Crashes during Startup.

Former Member
0 Kudos

Hello All,

Recently started facing this issue all of a sudden.

The Design Studio 1.5 Client crashes without an error pop up. This happens even before the logon prompt screen shows up.It just doesn't start.

I tried un-installation and re-installation but to no avail. Rebooted my machine but of no use. Upgraded the client from DS1.5 SP00 to SP01 but again in vain.

The log file located at C:\Users\<MyUser>\Analysis-workspace\.metadata contains the below -

!SUBENTRY 1 org.eclipse.equinox.registry 4 1 2015-09-11 10:28:58.851

!MESSAGE Plug-in "org.eclipse.equinox.p2.ui.sdk.scheduler" was unable to instantiate class "org.eclipse.equinox.internal.p2.ui.sdk.scheduler.AutomaticUpdateScheduler".


java.lang.NullPointerException: while trying to invoke the method org.eclipse.equinox.internal.p2.ui.sdk.scheduler.AutomaticUpdatePlugin.setScheduler(org.eclipse.equinox.internal.p2.ui.sdk.scheduler.AutomaticUpdateScheduler) of a null object returned from org.eclipse.equinox.internal.p2.ui.sdk.scheduler.AutomaticUpdatePlugin.getDefault()

  at org.eclipse.equinox.internal.p2.ui.sdk.scheduler.AutomaticUpdateScheduler.<init>(

  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

  at sun.reflect.NativeConstructorAccessorImpl.newInstance(

  at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(

  at java.lang.reflect.Constructor.newInstance(

  at java.lang.Class.newInstance(

  at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(

  at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(

  at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(

  at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(

  at org.eclipse.ui.internal.WorkbenchPlugin$

  at org.eclipse.swt.custom.BusyIndicator.showWhile(

  at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(

  at org.eclipse.ui.internal.EarlyStartupRunnable.getExecutableExtension(



  at org.eclipse.ui.internal.Workbench$


!ENTRY 4 2 2015-09-11 10:28:58.851

!MESSAGE An internal error occurred during: "Workbench early startup".


java.lang.NullPointerException: while trying to invoke the method org.osgi.util.tracker.ServiceTracker.getService() of a null object loaded from field org.eclipse.core.internal.runtime.InternalPlatform.extendedLogTracker of an object loaded from local variable 'this'

  at org.eclipse.core.internal.runtime.InternalPlatform.getLog(

  at org.eclipse.core.runtime.Plugin.getLog(

  at org.eclipse.ui.internal.WorkbenchPlugin.log(

  at org.eclipse.ui.internal.EarlyStartupRunnable.handleException(

  at org.eclipse.core.runtime.SafeRunner.handleException(


  at org.eclipse.ui.internal.Workbench$


!SESSION 2015-09-11 10:32:48.817 -----------------------------------------------



java.vendor=SAP AG

BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_IN

Framework arguments:  BusinessObjects Design Studio

Command-line arguments:  -os win32 -ws win32 -arch x86 BusinessObjects Design Studio

!ENTRY org.eclipse.equinox.ds 1 0 2015-09-11 10:32:50.049

!MESSAGE Could not bind a reference of component The reference is: Reference[name = IActivatorBase, interface =, policy = dynamic, cardinality = 0..n, target = null, bind = addRICActivator, unbind = removeRICActivator]

I have already raised the issue to SAP but the issue is very pressing now. Any help would really be appreciated.

Thanks & Regards,

Sreekul Nair

View Entire Topic
Active Contributor
0 Kudos

Try renaming Analysis-workspace and Analysis-config in your home directory and relaunching Design Studio.

Former Member
0 Kudos

Hi Mike,

I saw the response a little late and had already done the following to resolve the issue -

a) Uninstalled the Design Studio from FrontEnd machine.

b) Removed all the Design Studio Installation entries from Windows Registry.

c) Renamed the Analysis-workspace and Analysis-config.

d) Downloaded new DS 1.5 full Installation Dump from SMP. (Wasn't sure if the Dump I had got corrupted).

e) Reinstalled the DS1.5 with new installation.

And Voila... The issue got resolved.

Hard to say which step actually contributed to the resolution but my hunch is the one that you suggested. Renaming the Analysis-workspace and Analysis-config folders in my home directory.

Thanks & Regards,

Sreekul Nair