Solved: Unable to login to NWDI

Hi Everyone

I am unable to login in to NWDI

When I try to login through Development Configuration Perspective

the following error occurs

Landscape Directory Invalid server response (XML not valid)

Please Help

Thanks in advance

SAP Managed Tags:
NW Java Development Infrastructure (NWDI)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

make sure put the right url in the preference. http://host:port

don't put /sld at the end.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Jun

Thanks for the quick reply

I have put the right url in the preference. without putting /sld.

I am able to ping the NWDI.

But the issue persists I am still unable to log on to it.

Please help

Hi Abhinav,

Are you assigned to NWDI Developers Group?

Check if SAP_SLD_DEVELOPER role is assigned to the group NWDI.Developers.

Also, try to login to SLD with your User ID in the web browser.

BR,

Anurag

Hi Anurag

Thanks for the respone

How do you check if the following roles has been assigned to you?

I have the following role assigned in user management ------->identity management.

SAP_JAVA_NWADMIN_CENTRAL Central NetWeaver Administrator UME Database

SAP_JAVA_NWADMIN_LOCAL Local NetWeaver Administrator UME Database

Hi Abhinav,

Please assign your User ID to the group NWDI.Developers and then try again.

BR,

Anurag

Hi Abhinav,

Please login to NWA with J2EE_ADMIN and check the below roles

"NWA_SUPERADMIN

NWA_JAVA_SUPPORT

SAP_JAVA_NWADMIN_LOCAL

SAP_JAVA_NWADMIN_LOCAL_READONLY

SAP_JAVA_NWADMIN_CENTRAL

SAP_JAVA_NWADMIN_CENTRAL_READONLY

Thanks,

Hamendra

Hi Anurag

Thanks for the reply

My user id is assigned to both the groups

NWDI.developer

NWDI.Administrator

But still it gives the invalid server response(xml not valid).

Regards

Abhinav

how about other guys?

Hi Jun

There are no other guys.

Regards

Abhinav Choudhury

first time to use nwdi?

what's the version of nwdi and nwds?

Hi Jun

Thanks for the reply.

First time for me. Before me my predecessors have imported configurations from nwdi. But recently the nwdi port has changed.

NWDS version is 7.01

what's the change? can you detail it?

Hi Abhinav

You say you are using NWDS 7.01.

There exist two paths where you can find some DTR settings.

C:\Users\<username>\.dtr

C:\Users\<username>\.dtc

When you check the path C:\Users\<username>\.dtc you will see several files.

Check the content of these files. Maybe some of the files contain the old NWDI port number. In that case you could try to adapt it and restart the studio (the studio should be closed at this time anyway).

Also check the .dtr path.

Or you can just install NWDS on another computer and try it again with a fresh Setup. Maybe it works there.

BTW: You can find out the path when you open the NWDS->Window->Preferences->Java Development Infrastructure->Development Configuration

There will you see the field "Root folder".

Hope this will help you a bit.

Cheers

Klaudio

Hi Klaudio

Thanks for the reply

I know the old port number. But when I ping it it gives unable to open sso connection to host.

I get the following error

Landscape Directory Invalid server response (XML not valid)

details:---

com.sap.lcr.api.cimclient.LcrException: com.sap.lcr.api.cimclient.CIMClientException: Invalid server response (XML not valid)

at com.sap.lcr.api.cimclient.HttpRequestSender.processResponse(HttpRequestSender.java:658)

at com.sap.lcr.api.cimclient.HttpRequestSender.send(HttpRequestSender.java:341)

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

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

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

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

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

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:291)

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

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

Caused by: com.sap.lcr.api.cim.ItemConstructionExcp: java.lang.IllegalArgumentException: InputStream cannot be null

at com.sap.lcr.api.cim.Xml2Cim.xml2Cim(Xml2Cim.java:121)

at com.sap.lcr.api.cimclient.HttpRequestSender.processResponse(HttpRequestSender.java:649)

... 47 more

caused by:

com.sap.lcr.api.cim.ItemConstructionExcp: java.lang.IllegalArgumentException: InputStream cannot be null

at javax.xml.parsers.SAXParser.parse(SAXParser.java:139)

at com.sap.lcr.api.cim.Xml2Cim.xml2Cim(Xml2Cim.java:117)