cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

SDK Extension - Design Studio 1.6 - Eclipse - Run as Applikation

Former Member

on ‎06-01-2017 10:28 AM

0 Kudos

Hello Everybody,

i tried the followed tutorial:

https://blogs.sap.com/2015/09/21/your-first-extension-part-0-setting-up-eclipse/

and i was not able to get design studio started from eclipse.

i set the target plattform and imported the SDK - Example Colored Box.

I got the followed error message :

!SESSION 2017-06-01 11:19:02.273 ----------------------------------------------- eclipse.buildId=@qualifier@ java.version=1.8.0_131 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE Framework arguments: -product com.sap.ip.bi.zen Command-line arguments: -product com.sap.ip.bi.zen -data C:\sdk_Workspace/../runtime-EclipseApplication(1) -dev file:C:/sdk_Workspace/.metadata/.plugins/org.eclipse.pde.core/Eclipse Application (1)/dev.properties -os win32 -ws win32 -arch x86_64 -consoleLog !ENTRY org.eclipse.equinox.ds 1 0 2017-06-01 11:19:06.686 !MESSAGE Could not bind a reference of component com.sap.ip.bi.base.application.DeclaredServiceActivator. The reference is: Reference[name = IActivatorBase, interface = com.sap.ip.bi.base.bundle.IActivatorBase, policy = dynamic, cardinality = 0..n, target = null, bind = addRICActivator, unbind = removeRICActivator] !ENTRY org.eclipse.update.configurator 4 0 2017-06-01 11:19:25.915 !MESSAGE Unable to find feature.xml in directory: C:\Program Files (x86)\SAP BusinessObjects\Design Studio\features\__sap.dir !ENTRY org.eclipse.update.configurator 4 0 2017-06-01 11:19:26.495 !MESSAGE Unable to find feature.xml in directory: C:\Program Files (x86)\SAP BusinessObjects\Design Studio\features\__sap.dir !ENTRY org.eclipse.osgi 4 0 2017-06-01 11:19:26.615 !MESSAGE An error occurred while automatically activating bundle org.eclipse.ui.workbench (464). !STACK 0 org.osgi.framework.BundleException: Error starting module.

any hints how i could fix this issue ?

Show replies
Show replies
TammyPowlas
Active Contributor
‎06-01-2017 10:48 AM
0 Kudos

Could you share more details? Which version/SP of Design Studio are you using? Which version of Eclipse?

Former Member
‎06-01-2017 11:01 AM
0 Kudos

Hallo Tammy,

thank you for the fast answer. Yes indeed the versions i use are the following :

Design Studio Version 16.4.2 --> Design Studio 1.6 SP 4 Patch 2

Eclipse Project --> Neon.2 Release (4.6.2)

Former Member
‎06-01-2017 1:02 PM
0 Kudos

i tried to fix the target plattform. i did took now care of the naming:

designstudio-pic1.png

designstudio-pic2.png

now it still don't work but the error is a bit different. followed the error code :

Command-line arguments: -product com.sap.ip.bi.zen -data C:\sdk_exercises/../runtime-EclipseApplication -dev file:C:/sdk_exercises/.metadata/.plugins/org.eclipse.pde.core/Eclipse Application/dev.properties -os win32 -ws win32 -arch x86 -consoleLog !ENTRY org.eclipse.equinox.ds 1 0 2017-06-01 13:51:47.200

!MESSAGE Could not bind a reference of component com.sap.ip.bi.base.application.DeclaredServiceActivator. The reference is: Reference[name = IActivatorBase, interface = com.sap.ip.bi.base.bundle.IActivatorBase, policy = dynamic, cardinality = 0..n, target = null, bind = addRICActivator, unbind = removeRICActivator] !ENTRY org.eclipse.update.configurator 4 0 2017-06-01 13:52:13.782

!MESSAGE Unable to find feature.xml in directory: C:\Program Files (x86)\SAP BusinessObjects\Design Studio\features\__sap.dir !ENTRY org.eclipse.osgi 4 0 2017-06-01 13:52:15.388

!MESSAGE An error occurred while automatically activating bundle com.sap.ip.bi.zen.ui (200). !STACK 0 org.osgi.framework.BundleException: Exception in com.sap.ip.bi.zen.ui.ZenUiPlugin.start() of bundle com.sap.ip.bi.zen.ui.

any idea ?

Former Member
‎06-01-2017 1:11 PM
0 Kudos

Here is the full Error Message :

!SESSION 2017-06-01 14:08:55.099 -----------------------------------------------
eclipse.buildId=@qualifier@
java.version=1.8.0_131
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Framework arguments:  -product com.sap.ip.bi.zen
Command-line arguments:  -product com.sap.ip.bi.zen -data C:\sdk_exercises/../runtime-EclipseApplication -dev file:C:/sdk_exercises/.metadata/.plugins/org.eclipse.pde.core/Eclipse Application/dev.properties -os win32 -ws win32 -arch x86 -consoleLog


!ENTRY org.eclipse.equinox.ds 1 0 2017-06-01 14:08:56.626
!MESSAGE Could not bind a reference of component com.sap.ip.bi.base.application.DeclaredServiceActivator. The reference is: Reference[name = IActivatorBase, interface = com.sap.ip.bi.base.bundle.IActivatorBase, policy = dynamic, cardinality = 0..n, target = null, bind = addRICActivator, unbind = removeRICActivator]


!ENTRY org.eclipse.update.configurator 4 0 2017-06-01 14:09:22.499
!MESSAGE Unable to find feature.xml in directory: C:\Program Files (x86)\SAP BusinessObjects\Design Studio\features\__sap.dir


!ENTRY org.eclipse.osgi 4 0 2017-06-01 14:09:23.197
!MESSAGE An error occurred while automatically activating bundle com.sap.ip.bi.zen.ui (200).
!STACK 0
org.osgi.framework.BundleException: Exception in com.sap.ip.bi.zen.ui.ZenUiPlugin.start() of bundle com.sap.ip.bi.zen.ui.
	at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:792)
	at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:721)
	at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:941)
	at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:318)
	at org.eclipse.osgi.container.Module.doStart(Module.java:571)
	at org.eclipse.osgi.container.Module.start(Module.java:439)
	at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:454)
	at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
	at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:531)
	at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:324)
	at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:327)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:402)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
	at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:573)
	at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)
	at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
	at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
	at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:191)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
Caused by: java.lang.UnsatisfiedLinkError: Cannot load 32-bit SWT libraries on 64-bit JVM
	at org.eclipse.swt.internal.Library.loadLibrary(Library.java:259)
	at org.eclipse.swt.internal.Library.loadLibrary(Library.java:236)
	at org.eclipse.swt.internal.C.<clinit>(C.java:16)
	at org.eclipse.swt.widgets.Display.<clinit>(Display.java:138)
	at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:734)
	at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:162)
	at com.sap.ip.bi.zen.ui.ZenUiPlugin.start(ZenUiPlugin.java:115)
	at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:771)
	at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:764)
	... 33 moreRoot exception:
java.lang.UnsatisfiedLinkError: Cannot load 32-bit SWT libraries on 64-bit JVM
errorfile.txt
Former Member
‎06-01-2017 1:35 PM
0 Kudos

after change the Java Version from 64bit to 32bit i could start the Design Studio but still with some errors i got the followed message after change the java runtime version:

1. Change Java Version

java-32bit.png

2. Run Design Studio from Eclipse

comsapipbi-is-missing.png

3. no Project Explorer in Design Studio

empty-project-explorer.png

4. Error Message 

!SESSION 2017-06-01 14:29:35.534 -----------------------------------------------
eclipse.buildId=@qualifier@
java.version=1.8.0_131
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Framework arguments:  -product com.sap.ip.bi.zen
Command-line arguments:  -product com.sap.ip.bi.zen -data C:\sdk_exercises/../runtime-EclipseApplication -dev file:C:/sdk_exercises/.metadata/.plugins/org.eclipse.pde.core/Eclipse Application/dev.properties -os win32 -ws win32 -arch x86 -consoleLog


!ENTRY org.eclipse.equinox.ds 1 0 2017-06-01 14:29:36.289
!MESSAGE Could not bind a reference of component com.sap.ip.bi.base.application.DeclaredServiceActivator. The reference is: Reference[name = IActivatorBase, interface = com.sap.ip.bi.base.bundle.IActivatorBase, policy = dynamic, cardinality = 0..n, target = null, bind = addRICActivator, unbind = removeRICActivator]


!ENTRY org.eclipse.update.configurator 4 0 2017-06-01 14:29:43.382
!MESSAGE Unable to find feature.xml in directory: C:\Program Files (x86)\SAP BusinessObjects\Design Studio\features\__sap.dir
..........

.....at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
Jun 01, 2017 2:29:47 PM java.util.prefs.WindowsPreferences <init>


WARNUNG: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(...) returned error code 5.

and so on...............

<br>
Former Member
‎06-01-2017 1:56 PM
0 Kudos

now i tried this one :

https://stackoverflow.com/questions/16428098/groovy-shell-warning-could-not-open-create-prefs-root-n...

so i got at least the design studio running with a project explorer but i could not see any colored box in it 😞

and i still got the issue that at the start of the design studio a window appears which tells me that the com.sap.ip.bi is missing.

How i could fix the issue with the com.sap.ip.bi is missing window ?

TammyPowlas
Active Contributor
‎06-01-2017 10:18 PM
0 Kudos

Hi Marc - a co-worker uses Neon Eclipse (I do not, I am using Kepler Eclipse) but I was able to follow the SDK help to create a sample extension - https://help.sap.com/viewer/7979f8ee98004609ae4ae22b5e4a335d/1.6.4.0/en-US/29b5faad83f941d38593e42d9... - any chance of you starting over and following the SAP Help?

Former Member
‎06-02-2017 11:53 AM
0 Kudos

well no idea whats the reason, for the missing com.sap.ip.bi is, may i have to reinstall both again.

the help link from you is pointing to create new extensions i do have problems to see the sample one in design studio by starting the design studio from eclipse.

Former Member
‎06-02-2017 2:47 PM
0 Kudos

after looking on the installed BIT Versions i saw that my design studio installation was on 32bit.

now i used JAVA, Eclipse and Design Studio in 64 bit. And i was able to start the Design Studio from Eclipse.

I saw then also in the SAPUI5 mode the colored box example in the SAPUI5m mode i could not see the example the root is may that it is an old example.

but the missing com.sap.ip.bi warning i still get. is this normal ?

Answer

Accepted Solutions (0)

Answers (0)

Ask a Question