Hi ,

I am facing issue while transporting BPM project.

My scenario is:

I am using single SLD for Dev and Test environments.

We have BPM already present on Dev and test environments.

Received a new change for the existing BPM. we have undeployed the existing BPM on Dev environment and created a new BPM on dev environment by adding the changes.

The changed BPM is deployed on dev successfully and tested also.

After we transport the new changed BPM to test environmet, it is giving error while importing the TR:

Error is:

-> Cannot deploy two applications with identical application aliases (context roots). Your application [xxx.com/logistics~xxx_bp

  m] defines an application alias (context root) [{urn_xxx_xxx_PurchaseOrderNotification}OutboundDeliveryConfirmation

  _In] that is already in use by application [xxx/logistics~xxx. There are two possibilities in order to proceed with

  deployment: 1) Define different application alias (context root) for your application [xxx/logistics~xxx_bpm] (this is the

  preferred option). 2) Undeploy the application [xxx/logistics~delivery~xxx'. "

But when I try to login to NWDI Track of Test system  to un-deploy, it is not showing any details.

Any ideas on my issue.

Regards,

SP

We have one NWDI system but one more NWDI system is required (due to access restrictions in the existing NWDI). The existing NWDI system uses our central SLD system. This is the only SLD system we have in the SAP landscape.

Is there any danger if the new (second) NWDI system also uses this central SLD? I have not found any text about this scenario.

Thank you

Br.

Ales

Hi experts ,

In nwds 7.31 sp 10 , selecting window-Prefrences -> Top search input filed  .. i gave system land scape directory , right side i got a pane where i can enter the URL , now on click of Ping , im getting the exception  as follows.

System landscape directory http://**.***.***.***:50000/ is not available

and complete stack trace is as follows

com.sap.sld.api.wbem.exception.CIMCommunicationException: CIM_ERR_FAILED: Received response is not a CIM Operation Response! Check "http://**.***.***.***:50000/sld/cimom/" is the correct URL for the SLD CIM Object Manager (default is "http://**.***.***.***:50000/sld/cimom") and that user "" has access to the SLD via http and is not required to change his/her password.

at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.processResponse(WBEMHttpRequestSender.java:550)

at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.sendImpl(WBEMHttpRequestSender.java:211)

at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:233)

at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:194)

at com.sap.sld.api.wbem.client.WBEMRequestSender.sendRequest(WBEMRequestSender.java:275)

at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:300)

at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:332)

at com.sap.sld.api.wbem.client.WBEMRemoteClient.getClassImpl(WBEMRemoteClient.java:264)

at com.sap.sld.api.wbem.client.WBEMAbstractClient.exists(WBEMAbstractClient.java:832)

at com.sap.sld.api.wbem.client.WBEMClientUtil.checkServer(WBEMClientUtil.java:141)

at com.sap.ide.dii05.lib.internal.login.PingManager.executeSldPing(PingManager.java:489)

at com.sap.ide.dii05.lib.internal.login.PingManager.pingLSDServer(PingManager.java:460)

at com.sap.ide.dii05.ui.internal.preference.DevConfPreferencePage$11.run(DevConfPreferencePage.java:338)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

actually im trying to connect to the dtr , to import the track .

Regards

Govarda

Hello All,

I am new to NWDI. I did some code modifications in my DC. When i check in my activity, it gets activated, but not getting deployed. At first i was getting authentication problem, that is resolved now. Now i get this CMS log:

20140819135816 Info :Aug 19, 2014 1:58:16 PM Info: com.sap.ASJ.dpl_api.001023 Deployment of [name: 'abc', vendor: 'XXXX.com' (sda)] finished.

20140819135816 Info :Aug 19, 2014 1:58:16 PM Info: com.sap.ASJ.dpl_api.001052 +++ Deployment of session ID [467] finished with status [Error] +++. [[ deployerId=7 ]] [[#49: 4.031 sec]] [

20140819135816 Info :===== Summary - Deploy Result - Start =====

20140819135816 Info :------------------------

20140819135816 Info :Type | Status : Count

20140819135816 Info :------------------------

20140819135816 Info :> SCA(s)

20140819135816 Info :> SDA(s)

20140819135816 Info :- [Aborted] : [1]

20140819135816 Info :------------------------

20140819135816 Info :------------------------

20140819135816 Info :Type | Status : Id

20140819135816 Info :------------------------

20140819135816 Info :> SCA(s)

20140819135816 Info :> SDA(s)

20140819135816 Info :- [Aborted] : name: 'abc', vendor: 'XXXX.com',

20140819135816 Info :------------------------

20140819135816 Info :===== Summary - Deploy Result - End =====

20140819135816 Info :]

20140819135816 Info :end of log

20140819135816 Info :End deployment:

20140819135816 Info :

20140819135816 Info :Summary of deployment

20140819135816 Info :==> deployment finished for abc (103) with rc=12

20140819135816 Info :deployment finished for buildspace: NDI_NDITK080_D

Thanks.

Hi guys, i´m working in a PO system the thing is that the basis team upgrade to a new SP, but we are having problems with the development configuration, we created it using CM Services at first place and now, after the upgrade the buildspace in CBS only contain the custom DC´s, all the sap.com DC´s are gone.

In the development configuration management inside CM Services via devinf we can see that the software component definition have the related SC´s but when we syncronize the all thing in the CBS we only have the custom DC´s and we can´t build the all thing anymore.

The Basis team told me that they don´t see some components in the comparison between de runtime and build and is the respective configuration that have problems to import the sap dc´s.

The difference between a configuration that imports the sap dc´s correctly and the above scenario are that we can see each component in the column imported in NWDI buildspace/workspace, I´m not sure if this could be the problem.

What do I need to check in order to get the SAP DC´s imported to CBS ? or

thanks any help will be appreciated.

hi,

I have just created a new composite application from nwds, and once it is created I am not able to check in. It has below error message:

The operation was aborted because: Project "projectname": Generated code is not in sync with the model. Regenerate the project before check-in.:operation failed at13:25:45.760

What does it means with regenerate?

I have tried to build the dc and still it does not work.

Any help there?

Thanks!

below is the error I see from Nwdi log /sapmnt/SID/global/TCS/LOG

cannot create a connection for the buildspace:  NWDITRACK_D //connect to deploy tool failed:The user 'Administrator' could not be connected to the specified host

please advice on fix.

Thanks

Hi there,

I'm using Jenkins for my development tasks and continuous integration.

Recently I came to a project using NWDI. I'm a JavaScript developer using SAPUI5, and all the source code is checked into NWDI. As I want to continue using Jenkins, I'm searching for a plugin to access the source code inside of NWDI out of Jenkins.

I want to check for changed files for a DC. If there are changed files, checkout the whole project and perform the unit tests and integration tests. However, I don't know how to get the sources out of NWDI.

I don't want to use Eclipse (NWDS) to check out files, or even switch to Subversion and don't use NWDI at all.

Do you know about a solution for this issue?

Best regards

Tobias

Dear Team,

Here I am configuring NWDI 7.3.

Successfully created a standalone Developmenmt configuration and while synchronizing the services using CM services the screen throws an error

( on clicking any button on the synchronize service screen I am getting same error)

400 session not found

Failed to process the request:Request refers to an unknown session

Thru SDN got the below link and checked the parameters.Our AS JAVA version is 7.31 and the parameters are already set to false.

http://wiki.sdn.sap.com/wiki/display/TechTSG/(JSTTSG)(Web)Problems-P203

Please help on this

Regards

Prasad

Hi Dude,

the version of my NWDS is:

SAP NetWeaver Developer Studio

SAP Enhancement Package 1 for SAP NetWeaver Developer Studio 7.3 SP03 PAT0000

the update file downloaded is:

updatesite-management-tool-7.3-SP03-PAT0000-win32

whereas after the file updatesite-management-tool-7.3-SP03-PAT0000-win32.rar has been extracted, nothing happended when the executable file updatesite_tool had been triggered.

please find the message displayed in the console in the attached file.

so my question is:

how can i use this update file to update my NWDS to 7.31 version?

the java installed on my pc is:

1.6.0_07 SE runtime environment

thanks

We are going to update EP to 7.4 from 7.01.

And one of the post update requirment would be to re-compile  all the WD JAVA application

But we are in situation where NWDI tracks whave got corrupted somehow.

Could any bodyplease  tell me if there is/are any licensed toolto recover those tracks.

Thanks

Kamal

Hello SAP Gurus,

I have an object to enhance the standard wed Dynpro Java leave ESS application.

while importing the development configurations from NWDI in the NWDS, I am facing the below error.

Could anyone kindly please provide a solution to me to reolve this as soon as possible.

!ENTRY org.eclipse.jface 4 2 Sep 02, 2013 19:29:41.716

!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".

!STACK 0

java.lang.NullPointerException

at org.eclipse.jface.viewers.CustomHashtable.put(CustomHashtable.java:284)

at org.eclipse.jface.viewers.StructuredViewer.mapElement(StructuredViewer.java:745)

at org.eclipse.jface.viewers.StructuredViewer.associate(StructuredViewer.java:232)

at org.eclipse.jface.viewers.AbstractTreeViewer.associate(AbstractTreeViewer.java:247)

at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:396)

at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:119)

at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1006)

at org.eclipse.core.runtime.Platform.run(Platform.java:413)

at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:1271)

at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:320)

at org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:303)

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

at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:289)

at org.eclipse.jface.viewers.AbstractTreeViewer$5.run(AbstractTreeViewer.java:729)

at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:801)

at org.eclipse.jface.viewers.AbstractTreeViewer.inputChanged(AbstractTreeViewer.java:721)

at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:238)

at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:991)

at com.tssap.dtr.client.eclipse.ui.treeBrowser.RepositoryTreeViewer.setInput(RepositoryTreeViewer.java:392)

at com.tssap.dtr.client.eclipse.ui.treeBrowser.RepositoryView$37.run(RepositoryView.java:1212)

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

at com.tssap.dtr.client.eclipse.ui.treeBrowser.RepositoryView.onActiveClientChanged(RepositoryView.java:1209)

at com.tssap.dtr.client.lib.vfs.config.impl.Configuration.setActiveClient(Configuration.java:477)

at com.sap.ide.eclipse.component.wizard.DevConfWizard.updateDTR(DevConfWizard.java:687)

at com.sap.ide.eclipse.component.wizard.DevConfWizard.addDevConf(DevConfWizard.java:546)

at com.sap.ide.eclipse.component.wizard.DevConfWizard.access$100(DevConfWizard.java:67)

at com.sap.ide.eclipse.component.wizard.DevConfWizard$1.run(DevConfWizard.java:348)

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

at com.sap.ide.eclipse.component.wizard.DevConfWizard.performFinish(DevConfWizard.java:346)

at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)

at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)

at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)

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.DevConfNewMenuAction.openWizard(DevConfNewMenuAction.java:39)

at com.sap.ide.eclipse.component.provider.actions.DevConfNewMenuAction.run(DevConfNewMenuAction.java:33)

at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)

at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:207)

at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)

at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)

at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)

at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)

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)

Hi everybody!

I have to develop an extension for a SAP product and I will have to work whit the NWDI.

From my developer studio I tried to import a configuration just created from the infrastriucture configuration panel on the NWA.

On the NWDS I select -import development configuration from SLD then I select my configuration and I can see all the software components associated... but when I click to finish and enter my credential I get the following error:

/**********************************************************************************************/

com.sap.tc.devconf.SyncException: Could not import configuration: Cannot perform login (com.sap.tc.devconf.DevConfigException: Could not create mountpoint for SC in compartment sap.com_SAP-WEC-FRW: Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW (Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW) (Could not create mountpoint for SC in compartment sap.com_SAP-WEC-FRW: Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW (Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW)) (Could not create mountpoint for SC in compartment sap.com_SAP-WEC-FRW: Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW (Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW) (Could not create mountpoint for SC in compartment sap.com_SAP-WEC-FRW: Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW (Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW)))) (Cannot perform login (com.sap.tc.devconf.DevConfigException: Could not create mountpoint for SC in compartment sap.com_SAP-WEC-FRW: Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW (Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW) (Could not create mountpoint for SC in compartment sap.com_SAP-WEC-FRW: Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW (Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW)) (Could not create mountpoint for SC in compartment sap.com_SAP-WEC-FRW: Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW (Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW) (Could not create mountpoint for SC in compartment sap.com_SAP-WEC-FRW: Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW (Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW)))))

  at com.sap.tc.devconf.DevelopmentConfigurationFactory.addConfiguration(DevelopmentConfigurationFactory.java:799)

  at com.sap.tc.devconf.DevelopmentConfigurationFactory.addConfiguration(DevelopmentConfigurationFactory.java:717)

  at com.sap.tc.devconf.DevelopmentConfigurationFactory.addConfiguration(DevelopmentConfigurationFactory.java:688)

  at com.sap.ide.dii05.lib.internal.commands.devconf.BasicWizardHelper.addDevConf(BasicWizardHelper.java:300)

  at com.sap.ide.dii08.internal.commandz.ImportDevConfigCommand.execute(ImportDevConfigCommand.java:127)

  at com.sap.ide.dii08.internal.service.InternalDiiCommandService.importDevelopmentConfiguration(InternalDiiCommandService.java:476)

  at com.sap.ide.dii05.ui.internal.devconf.wizard.DevConfImportSldWizard$1.run(DevConfImportSldWizard.java:103)

  at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)

Caused by: com.sap.tc.devconf.DevConfigException: Cannot perform login (com.sap.tc.devconf.DevConfigException: Could not create mountpoint for SC in compartment sap.com_SAP-WEC-FRW: Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW (Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW) (Could not create mountpoint for SC in compartment sap.com_SAP-WEC-FRW: Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW (Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW)) (Could not create mountpoint for SC in compartment sap.com_SAP-WEC-FRW: Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW (Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW) (Could not create mountpoint for SC in compartment sap.com_SAP-WEC-FRW: Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW (Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW))))

  at com.sap.tc.devconf.internal.DevelopmentConfiguration.goOnline(DevelopmentConfiguration.java:4363)

  at com.sap.tc.devconf.DevelopmentConfigurationFactory.addConfiguration(DevelopmentConfigurationFactory.java:792)

  ... 7 more

Caused by: com.sap.tc.devconf.login.LoginException: com.sap.tc.devconf.DevConfigException: Could not create mountpoint for SC in compartment sap.com_SAP-WEC-FRW: Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW (Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW) (Could not create mountpoint for SC in compartment sap.com_SAP-WEC-FRW: Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW (Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW)) (Could not create mountpoint for SC in compartment sap.com_SAP-WEC-FRW: Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW (Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW) (Could not create mountpoint for SC in compartment sap.com_SAP-WEC-FRW: Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW (Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW)))

  at com.sap.tc.devconf.internal.DevelopmentConfiguration.performLogin(DevelopmentConfiguration.java:5124)

  at com.sap.tc.devconf.impl.login.LoginContext.login(LoginContext.java:56)

  at com.sap.tc.devconf.internal.DevelopmentConfiguration.goOnline(DevelopmentConfiguration.java:4359)

  ... 8 more

Caused by: com.sap.tc.devconf.DevConfigException: Could not create mountpoint for SC in compartment sap.com_SAP-WEC-FRW: Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW (Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW) (Could not create mountpoint for SC in compartment sap.com_SAP-WEC-FRW: Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW (Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW))

  at com.sap.tc.devconf.internal.DevelopmentConfiguration._goOnline(DevelopmentConfiguration.java:4419)

  at com.sap.tc.devconf.internal.DevelopmentConfiguration.performLogin(DevelopmentConfiguration.java:5121)

  ... 10 more

Caused by: com.sap.tc.devconf.SyncException: Could not create mountpoint for SC in compartment sap.com_SAP-WEC-FRW: Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW (Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW)

  at com.sap.tc.devconf.impl.dtr.DtrServiceAdapter.findOrCreateMountPointForSC(DtrServiceAdapter.java:271)

  at com.sap.tc.devconf.impl.dtr.DtrServiceAdapter.createMountPointsForSCs(DtrServiceAdapter.java:1427)

  at com.sap.tc.devconf.internal.DevelopmentConfiguration._goOnline(DevelopmentConfiguration.java:4414)

  ... 11 more

Caused by: com.sap.tc.devconf.DevConfigException: Getting name workspace name failed. There is no such workspace configured for compartment sap.com_SAP-WEC-FRW

  at com.sap.tc.devconf.impl.ConfigUtils.getWorkspaceName(ConfigUtils.java:763)

  at com.sap.tc.devconf.impl.dtr.DtrServiceAdapter.findOrCreateMountPointForSC(DtrServiceAdapter.java:233)

  ... 13 more

/**********************************************************************************************/

Looks like it cannot create the workspace but I don't really know where it is suppose to create it.

If anyone can help me will pay with a ton of points!

Enrico

Dear Reader(s),

Below is the ERROR MESSAGE I get when I deploy from my local NetWeaver Developer Studio to the (remote) J2EE application server.

-

In NWDS I made the following settings:

NWDS/Window/Preferences/SAP J2EE Engine

Message Server Host: serversap01

Message Server Port: 3601

-

I assume the J2EE_ADMIN user is used when establishing a connection between NWDS and the application server?

When I use the remote GUI from SDM on the server I can see the http server configuration on port 50019 is not running. Can this be the reason?

-

ERROR MESSAGE:

SDM host : serversap01

SDM port : 50018

URL to deploy : file:/C:/DOCUME_{1/jasper/LOCALS}1/Temp/temp16161Calculator_Sol_EAR.ear

Deployment exception : Server serversap01 did not accept login request as admin on port 50018.

Details: ERROR: Could not establish connection to server serversap01 at port 50018: Connection timed out: connect

Inner exception was :

Server serversap01 did not accept login request as admin on port 50018. Details:

ERROR: Could not establish connection to server serversap01 at port 50018: Connection timed out: connect

-

Please can anyone advise? Thanks in advance, Jasper

Hi,

I have an unique error.

In our project, we have installed NetWeaver 7.0 EHP1 SP4 as the Portal Devlopment Server.

I have done all the steps for Post Installation Steps of NWDI.

Now, there is an SAP SRS Compnent being deployed in Portal and functional consultant are

also using it.

Component Name : ISRSRS05_0-20002510.SCA

Version: SP05 for IS-R-SRS 602.

Now, this component is already being deployed in our Portal Server SAP NetWeaver 7.0 EHP1 SP4.

I was able to import this component in our NWDI track.

The dependent components of this .SCA are EP-BUILDT 7.0, SAP-JEE 7.0, SAP-BUILDT 7.0 and SAP_JTECHS 7.0

All the mandatory steps in Landscape Configurator and Transport Studio in CMS were done without error.

Then, I imported the NWDI track Configuration in NWDS 7.01 SP4.

I am able to import the inactive dcs of IS-R-SRS but when checking out, I am getting

Checkout failed: Checkout file failed (server response: Communication error [cause: Read timed out]):/TST/sap.com_IS-R-SRS/dev/inactive/DCs/sap.com/is/isr/srs/men/app/_comp/src/packages/com/sap/is/isr/srs/men/app/MainAppComp.wdcomponent /DJ1_TST_D~is~isr~srs~men~app~sap.com/src/packages/com/sap/is/isr/srs/men/app/MainAppComp.wdcomponent

The error in NWDS .metadata log is

!MESSAGE Feb 2, 2010 5:48:46 PM       com.sap.dtr.client.lib.protocol.requests.RequestBase     [Thread[main,5,main]] Error: 
java.net.SocketTimeoutException: Read timed out     at java.net.SocketInputStream.socketRead0(Native Method)     at java.net.SocketInputStream.read(SocketInputStream.java:129)     at java.net.SocketInputStream.read(SocketInputStream.java:182)     at com.sap.dtr.client.lib.protocol.streams.ChunkedInputStream.readLine(ChunkedInputStream.java:327)

But I can create activities successfully in NWDS (DTR).

I am able to write code in Compnent Controller of my custom SC VIN_PRD.

Now, my question is whether this is java.net.SocketException or incompatibility of software.

My delivery manager told me to get the older version of NWDS ie., NWDS 6.40 but I am sure

that will not work with SAP NetWeaver 7.0 EHP1 SP4.

There is an error in DTR log  server but on earlier date:

com.tssap.dtr.pvc.basics.transaction.AbstractSessionBoundTask#Java#background.outOfDBConnections#com.tssap.dtr.server.deltav.resources.log_messages#Service unavailable, running background task {0} failed. Database connection pool is out of connections. Check connection pool and database settings.#1#com.tssap.dtr.server.deltav.runtimeconfig.impl.ConfigParamsCheckerTas

Regards

Kaushik Banerjee

Hi experts ,

In nwds 7.31 sp 10 , selecting window-Prefrences -> Top search input filed  .. i gave system land scape directory , right side i got a pane where i can enter the URL , now on click of Ping , im getting the exception  as follows.

System landscape directory http://**.***.***.***:50000/ is not available

and complete stack trace is as follows

com.sap.sld.api.wbem.exception.CIMCommunicationException: CIM_ERR_FAILED: Received response is not a CIM Operation Response! Check "http://**.***.***.***:50000/sld/cimom/" is the correct URL for the SLD CIM Object Manager (default is "http://**.***.***.***:50000/sld/cimom") and that user "" has access to the SLD via http and is not required to change his/her password.

at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.processResponse(WBEMHttpRequestSender.java:550)

at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.sendImpl(WBEMHttpRequestSender.java:211)

at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:233)

at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:194)

at com.sap.sld.api.wbem.client.WBEMRequestSender.sendRequest(WBEMRequestSender.java:275)

at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:300)

at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:332)

at com.sap.sld.api.wbem.client.WBEMRemoteClient.getClassImpl(WBEMRemoteClient.java:264)

at com.sap.sld.api.wbem.client.WBEMAbstractClient.exists(WBEMAbstractClient.java:832)

at com.sap.sld.api.wbem.client.WBEMClientUtil.checkServer(WBEMClientUtil.java:141)

at com.sap.ide.dii05.lib.internal.login.PingManager.executeSldPing(PingManager.java:489)

at com.sap.ide.dii05.lib.internal.login.PingManager.pingLSDServer(PingManager.java:460)

at com.sap.ide.dii05.ui.internal.preference.DevConfPreferencePage$11.run(DevConfPreferencePage.java:338)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

actually im trying to connect to the dtr , to import the track .

Regards

Govarda

below is the error I see from Nwdi log /sapmnt/SID/global/TCS/LOG

cannot create a connection for the buildspace:  NWDITRACK_D //connect to deploy tool failed:The user 'Administrator' could not be connected to the specified host

please advice on fix.

Thanks

Hi,

I am trying to publish/deploy a web service (.ear) from NWDS. The version I am using is NWDS 7.3 SP10

SAP AS Java window has been configured:

In NWA SOA the Service Registry has been configured and port 5004 is accessible.

When I try to deploy the .ear from NWDS it gives an error saying the system given in SAP AS Java (above screenshot) is not responding, when I know the system is up and running:

!ENTRY com.sap.logging.adapter 4 0 2014-03-28 11:01:44.189

!MESSAGE Error during deployment      [Error: com.sap.ide.wtpserver.engineadapter.SapDeployer  Thread[Thread-10,5,main]]

!STACK 0

com.sap.ide.eclipse.sdm.deploy.DeploymentException: System Z99 not responding.

  at com.sap.ide.eclipse.sdm.threading.DeployThreadManager.deploy(DeployThreadManager.java:267)

  at com.sap.ide.eclipse.sdm.SDMManager.deployArchives(SDMManager.java:194)

  at com.sap.ide.wtpserver.engineadapter.SapDeployer.deployArchives(SapDeployer.java:46)

  at com.sap.ide.wtpserver.engineadapter.SAPPublisher$DeployRunnable.run(SAPPublisher.java:453)

  at java.lang.Thread.run(Thread.java:678)

   ------------- Nested exception -------------------

com.sap.ide.eclipse.deployer.api.APIException: System Z99 not responding.

  at com.sap.ide.eclipse.deployer.DeployerPlugin.getCurrentServerInfo(DeployerPlugin.java:94)

  at com.sap.ide.eclipse.deployer.DeployerPlugin.getClient(DeployerPlugin.java:246)

  at com.sap.ide.eclipse.sdm.threading.DeployThreadManager.deploy(DeployThreadManager.java:259)

  at com.sap.ide.eclipse.sdm.SDMManager.deployArchives(SDMManager.java:194)

  at com.sap.ide.wtpserver.engineadapter.SapDeployer.deployArchives(SapDeployer.java:46)

  at com.sap.ide.wtpserver.engineadapter.SAPPublisher$DeployRunnable.run(SAPPublisher.java:453)

  at java.lang.Thread.run(Thread.java:678)

!ENTRY com.sap.ide.wtpserver 4 0 2014-03-28 11:01:44.438

!MESSAGE Error during deployment

!STACK 1

com.sap.ide.wtpserver.SAPServerException: Error during deployment: System Z99 not responding.

  at com.sap.ide.wtpserver.engineadapter.SapDeployer.handleDeploymentException(SapDeployer.java:75)

  at com.sap.ide.wtpserver.engineadapter.SapDeployer.deployArchives(SapDeployer.java:48)

  at com.sap.ide.wtpserver.engineadapter.SAPPublisher$DeployRunnable.run(SAPPublisher.java:453)

  at java.lang.Thread.run(Thread.java:678)

Caused by: com.sap.ide.eclipse.sdm.deploy.DeploymentException: System Z99 not responding.

  at com.sap.ide.eclipse.sdm.threading.DeployThreadManager.deploy(DeployThreadManager.java:267)

  at com.sap.ide.eclipse.sdm.SDMManager.deployArchives(SDMManager.java:194)

  at com.sap.ide.wtpserver.engineadapter.SapDeployer.deployArchives(SapDeployer.java:46)

  ... 2 more

!SUBENTRY 1 com.sap.ide.wtpserver 4 0 2014-03-28 11:01:44.438

!MESSAGE Error during deployment: System Z99 not responding.

!STACK 0

com.sap.ide.eclipse.sdm.deploy.DeploymentException: System Z99 not responding.

  at com.sap.ide.eclipse.sdm.threading.DeployThreadManager.deploy(DeployThreadManager.java:267)

  at com.sap.ide.eclipse.sdm.SDMManager.deployArchives(SDMManager.java:194)

  at com.sap.ide.wtpserver.engineadapter.SapDeployer.deployArchives(SapDeployer.java:46)

  at com.sap.ide.wtpserver.engineadapter.SAPPublisher$DeployRunnable.run(SAPPublisher.java:453)

  at java.lang.Thread.run(Thread.java:678)

   ------------- Nested exception -------------------

com.sap.ide.eclipse.deployer.api.APIException: System Z99 not responding.

  at com.sap.ide.eclipse.deployer.DeployerPlugin.getCurrentServerInfo(DeployerPlugin.java:94)

  at com.sap.ide.eclipse.deployer.DeployerPlugin.getClient(DeployerPlugin.java:246)

  at com.sap.ide.eclipse.sdm.threading.DeployThreadManager.deploy(DeployThreadManager.java:259)

  at com.sap.ide.eclipse.sdm.SDMManager.deployArchives(SDMManager.java:194)

  at com.sap.ide.wtpserver.engineadapter.SapDeployer.deployArchives(SapDeployer.java:46)

  at com.sap.ide.wtpserver.engineadapter.SAPPublisher$DeployRunnable.run(SAPPublisher.java:453)

  at java.lang.Thread.run(Thread.java:678)

Is it possible to get a more detailed log of the error from somewhere?

Any help appreciated.

Che

Hello All,

While checking in the activity for one of my DC, i got error saying

"Name reservation failed for name TMP_CANDIDATE_REC3

  Name already reserved by yourself before; caption: Database Object Reservation

  Name already reserved by yourself before; caption: Database Object Reservation

    The exception was caught in the attached stack.

    com.sap.ide.dii05.util.api.log.Stacktrace

  at com.sap.ide.dii05.util.api.log.LogManager.internalCreateStatus(LogManager.java:359)

  at com.sap.ide.dii05.util.api.log.LogManager.createStatus(LogManager.java:340)

  at com.sap.ide.dii05.lib.internal.namereservation.NameReservation.reserve(NameReservation.java:153)

  at com.sap.dictionary.tools.nameserver.DdicNameReservationListener.validateNameReservation(DdicNameReservationListener.java:82)

  at com.sap.ide.dii05.lib.internal.namereservation.VetoListener.reactOnCheckIn(VetoListener.java:196)

  at com.sap.ide.dii05.lib.internal.namereservation.DiiCheckinValidator.validateCheckIn(DiiCheckinValidator.java:17)

  at com.tssap.dtr.client.eclipse.ui.actions.CheckinActivityAction$CheckinValidatorService.validateCheckIn(CheckinActivityAction.java:235)

  at com.tssap.dtr.client.eclipse.ui.actions.CheckinActivityAction$1.run(CheckinActivityAction.java:109)

  at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) "

Below is the error log:

com.sap.ide.dii05.lib.api.util.DiiLibraryException: Name reservation failed for name TMP_CANDIDATE_REC3

  at com.sap.ide.dii05.lib.internal.namereservation.NameReservation.reserve(NameReservation.java:153)

  at com.sap.dictionary.tools.nameserver.DdicNameReservationListener.validateNameReservation(DdicNameReservationListener.java:82)

  at com.sap.ide.dii05.lib.internal.namereservation.VetoListener.reactOnCheckIn(VetoListener.java:196)

  at com.sap.ide.dii05.lib.internal.namereservation.DiiCheckinValidator.validateCheckIn(DiiCheckinValidator.java:17)

  at com.tssap.dtr.client.eclipse.ui.actions.CheckinActivityAction$CheckinValidatorService.validateCheckIn(CheckinActivityAction.java:235)

  at com.tssap.dtr.client.eclipse.ui.actions.CheckinActivityAction$1.run(CheckinActivityAction.java:109)

  at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)

Caused by: com.sap.lcr.namealloc.api.ReservedBeforeException: Name already reserved by yourself before; caption: Database Object Reservation

  at com.sap.lcr.namealloc.NameAllocator.allocateName(NameAllocator.java:973)

  at com.sap.lcr.namealloc.NameAllocator.reservePreliminary(NameAllocator.java:1290)

  at com.sap.ide.dii05.lib.internal.namereservation.NameReservation.reserve(NameReservation.java:136)

  ... 6 more

Contains: The exception was caught in the attached stack.

com.sap.ide.dii05.util.api.log.Stacktrace

  at com.sap.ide.dii05.util.api.log.LogManager.internalCreateStatus(LogManager.java:359)

  at com.sap.ide.dii05.util.api.log.LogManager.createStatus(LogManager.java:340)

  at com.sap.ide.dii05.lib.internal.namereservation.NameReservation.reserve(NameReservation.java:153)

  at com.sap.dictionary.tools.nameserver.DdicNameReservationListener.validateNameReservation(DdicNameReservationListener.java:82)

  at com.sap.ide.dii05.lib.internal.namereservation.VetoListener.reactOnCheckIn(VetoListener.java:196)

  at com.sap.ide.dii05.lib.internal.namereservation.DiiCheckinValidator.validateCheckIn(DiiCheckinValidator.java:17)

  at com.tssap.dtr.client.eclipse.ui.actions.CheckinActivityAction$CheckinValidatorService.validateCheckIn(CheckinActivityAction.java:235)

  at com.tssap.dtr.client.eclipse.ui.actions.CheckinActivityAction$1.run(CheckinActivityAction.java:109)

  at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)

  at com.sap.ide.dii05.util.api.log.LogManager.internalCreateStatus(LogManager.java:359)

  at com.sap.ide.dii05.util.api.log.LogManager.createStatus(LogManager.java:340)

  at com.sap.ide.dii05.lib.internal.namereservation.NameReservation.reserve(NameReservation.java:153)

  at com.sap.dictionary.tools.nameserver.DdicNameReservationListener.validateNameReservation(DdicNameReservationListener.java:82)

  at com.sap.ide.dii05.lib.internal.namereservation.VetoListener.reactOnCheckIn(VetoListener.java:196)

  at com.sap.ide.dii05.lib.internal.namereservation.DiiCheckinValidator.validateCheckIn(DiiCheckinValidator.java:17)

  at com.tssap.dtr.client.eclipse.ui.actions.CheckinActivityAction$CheckinValidatorService.validateCheckIn(CheckinActivityAction.java:235)

  at com.tssap.dtr.client.eclipse.ui.actions.CheckinActivityAction$1.run(CheckinActivityAction.java:109)

  at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)

Plz help me out with probable solution.

Thanks,

Pranay

I have to consume webservice from third party system.

1. I have imported the WSDL.

2. I selected the Java DC and trying to generate client , but getting message like "Specified project is a java project"

From Hook DC i have to call webservice that's why going for standalone proxy.