cannot import development configuration in NWDS

[Former Member]

Dear all, i hit this error when i tried to import the development configuration in NWDS.

CIM_ERR_FAILED: No object manager started (application stopped)

com.sap.lcr.api.cimclient.LcrException: CIM_ERR_FAILED: No object manager started (application stopped)

at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.raiseExceptionOnError(SimpleResponseAnalyser.java:120)

at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.getIResult(SimpleResponseAnalyser.java:53)

at com.sap.lcr.api.cimclient.CIMOMClient.sendImpl(CIMOMClient.java:215)

at com.sap.lcr.api.cimclient.CIMOMClient.send(CIMOMClient.java:147)

at com.sap.lcr.api.cimclient.CIMOMClient.enumerateInstancesImpl(CIMOMClient.java:436)

at com.sap.lcr.api.cimclient.CIMOMClient.enumerateInstances(CIMOMClient.java:740)

at com.sap.lcr.api.cimclient.CIMClient.enumerateInstances(CIMClient.java:983)

at com.sap.lcr.api.sapmodel.JavaCIMObjectAccessor.enumerateInstances(JavaCIMObjectAccessor.java:211)

at com.sap.lcr.api.sapmodel.SAP_DesignTimeConfigurationAccessor.enumerateInstances(SAP_DesignTimeConfigurationAccessor.java:168)

at com.sap.ide.eclipse.component.devconf.DevConfManager$3.run(DevConfManager.java:507)

at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)

at com.sap.ide.eclipse.component.devconf.DevConfManager.listRemoteDevConfNames(DevConfManager.java:500)

at com.sap.ide.eclipse.component.wizard.LoadDevConfPage.fillTable(LoadDevConfPage.java:225)

at com.sap.ide.eclipse.component.wizard.LoadDevConfPage$5.widgetSelected(LoadDevConfPage.java:281)

at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)

at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)

at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)

at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)

at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)

at org.eclipse.jface.window.Window.open(Window.java:563)

at com.sap.ide.eclipse.component.provider.actions.DevConfNewAction.run(DevConfNewAction.java:46)

at com.tssap.selena.model.extension.action.SelenaActionCollector$GenericElementActionWrapper.run(SelenaActionCollector.java:229)

at com.tssap.util.ui.menu.MenuFactory$MuSiAction.saveRunAction(MenuFactory.java:1425)

at com.tssap.util.ui.menu.MenuFactory$MuSiAction.run(MenuFactory.java:1391)

at com.tssap.util.ui.menu.MenuFactory$DelegateAction.processInternal(MenuFactory.java:616)

at com.tssap.util.ui.menu.MenuFactory$DelegateAction.access$100(MenuFactory.java:586)

at com.tssap.util.ui.menu.MenuFactory$DelegateAction$BusyProcessWorker.run(MenuFactory.java:716)

at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)

at com.tssap.util.ui.menu.MenuFactory$DelegateAction.process(MenuFactory.java:610)

at com.tssap.util.ui.menu.internal.MenuListenerFactory$ProcessAdapter.widgetSelected(MenuListenerFactory.java:172)

at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)

at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)

at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)

at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)

at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)

at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)

at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)

at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)

at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:286)

at com.sap.ide.eclipse.startup.Main.run(Main.java:795)

at com.sap.ide.eclipse.startup.Main.main(Main.java:602)

anyidea what's the problem and how to solve it? thank you

[Former Member]

Hi,

It seems that object server has not been defined in SLD.

Follow the steps as given under "Setup of the Name Server" in the link,

http://help.sap.com/saphelp_nw04/helpdata/en/e1/2aa0753d12479cb6f21c38371299a7/content.htm

Ensure that the SLD server is up and running.

Hope this helps.

Regards

Srinivasan T

[Former Member]

Hi Srinivasan,

The SLD server is up and runing,and the same SLD configuration is used by another software development track,everything is working fine. except for this newly created track,any idea? thx

[Former Member]

Hi,

Then check whether the dependencies are missing in SLD between Development Configuration (Design Time Configuration) and CMS

Select the problematic Design Time Configuration from the SLD->Administration -> Content Maintenance -> Landscape Description and see in details whether Associated Instances is '0'. If so, delete and set proper dependencies as per the JDI installation doc.

Then from the CMS, save the affected track. If 'restore system state' is asked for, do it after saving.

Thereafter, import dev. config in NWDS should work fine.

Regards

Srinivasan T

[Former Member]

Hi Srinivasan,

Now i am able to import it.the track that i've just imported is the EMI_01dev.but it doesnt allow me to create New dc

http://img244.imageshack.us/img244/2518/79849545wz1.jpg

unlike the ESST00_dev

http://img299.imageshack.us/img299/5780/31140507rr7.jpg

anyidea? thanks

[Former Member]

Hi,

Check this forum link,

Regards

Srinivasan T

[Former Member]

Hi Joan,

It looks like your track is missing required DC, if we look into http://img299.imageshack.us/img299/5780/31140507rr7.jpg

track EMI01 is empty, EMI01 is a copy of ESST00 or newly created track. If its newly created verfiy all steps are done or not.

Let me know.

Regards

Praveen

[Former Member]

Dear Praveen,

I check with my basis team,it seems that they can't locate the software compoent created by them when they need to add it at the track data tab under the add software compoent section. Any idea? thank you.

[Former Member]

Hi,

Ensure that the SC created by your team is available in the SLD. If so, update CMS using the button 'Update CMS' in the the CMS Web UI->Landscape Configurator->Domain Data tab.

Now, the SC should appear in the 'Add SC'.

Regards

Srinivasan T