Hi All,

We are currently facing issues in one of the NWDI tracks while activating the activities. We have 2 main components on which there are like 40 activities.

It says "Unknown exception during generation Could not get ModelType com.sap.tc.webdynpro.modeltype.webservice.AdaptiveWebservice for model com.syngenta.test1.bp.mdm.web.ui.enrichbpdc.wd.models.getbusinesstypemodel.GetBusinessTypeModel(hint: check whether content archive is in classpath) " when activating the 1st(enrich) main component activities. But no problem or whatsoever in application.

On activating 2nd(Create) component, it says "The Component is broken" and "Invalid consistency with 1st(enrich) main component". FYI 2nd(Create) component uses 1st(enrich) component.

Since we have 40 activities, we do not know what/where the issue is. I tried to reimport the getbusinesstypemodel in 1st component. But nothing happened, same issue.

PFA the build log for both components. Please share your thoughts on this issue. Your help is much much appreciated

Thanks & Regards,

Manoj

Hi Everyone

I made some translation changes to the SAP standard ess package in Nwds.

I made a activity and made changes in the .xlf  file and activiated it. But the changes were not visible after activation in DEV

So I made changes in another .xlf file and activated the activity and changes became visible in DEV.

The changes made were in two different activity.

I released the latest activity to nwdi.

Now i need too check if the activity was transported from DEV to Quality. Because I cannot see the changes in Quality.

Where can i check it.

Thanks in advance

Regards

Abhinav Choudhury

Hi Experts,

NWDI Transports are failing: we are unable to see the changes moved via NWDI Activities i.e. Even after releasing the activities.

Earlier we were facing the same issues with local deployment through NWDS tool as well (unable to see the changes) but then it got resolved and we are able to view the code changes post deployment through NWDS tool.

But the issue is now appearing for NWDI. Please be informed that we've recently configured NWDI in our landscape.

In our case, Activity is activated and released successfully but code changes do not get reflected in Portal.

We are on NW Portal 7.4 SP 06 and NWDI 7.4 SP 06.

Any pointers will be highly appreciated.

BR,

Anurag

Dear All

I am on SAP PI 7.4 dual stack which NWDS version should i use because i tried with both NWDS 7.3 and NWDS 7.31 also

NWDS 7.3 its not connecting at all it says improper configuration

NWDS 7.31 connected to ESR and but ID it says only for single stack.

Can you please help

Regards

Sandeep

Hi there,

after a long time of trying to configure CM services on a NW 7.40 SP07 environment, we managed to use CMS instead.

CTS is running on a 7.11 PI system.

Building and Deployment of our BPM developments to DEV system is working fine.

Via assembling a transport request is created and appears in the import queue of the QUAL system in STMS of our CTS QUAL system.

But when I try to import the request, I get the following error message:

Client 010 does not exist. Choose another client.

The problem is that I can't specify the client of our CTS system when importing the transport.

These are the clients for our CTS systems:

DEV: T61 => client 010

QUAL: C61 => client 100

PROD: S61 => client 100

These are the NWDI systems:

DEV: T62

QUAL: C62

PROD: S62

This I can see from the transport log:

> createe071sentries='C62'

> including R3TRFILE

R3trans was called as follows: R3trans -w /usr/sap/trans/tmp/T62I900003.C62 /usr/sap/trans/tmp/T62KK90

Connected to DBMS = ORACLE    dbs_ora_tnsname = 'C61'    SYSTEM = 'C61'.

0 0

  trace at level 1 opened for a given file pointer

 

 

================== STEP 1 =====================

date&time        : 30.01.2015 - 08:09:52

function         : IMPORT

data file        : /usr/sap/trans/data/R900003.T62

Continuation     : /usr/sap/trans/data/R900003_#.T62

filedirectory    : /usr/sap/trans/data/T62K900003

buffersync       : YES

clients          : as exported

repeatimport     : YES (corresponds to unconditional mode 1)

repeatclimport   : NO

c.s.i.           : NO

charsetadapt     : YES

def. charset     : WEUROPEAN

createe071sentries: C62

commit           : 100000

table cache      : dynamic

INCLUDING        : 'R3TRFILE'

As you can see, it says "clients: as exported".

But in the CMS configuration I can't specify any client...

Can you tell me where the target client of our CTS QUAL system can be specified?

Thanks in advance!

Best regards,

Thorsten.

Hi,

We are configuring the NWDI for ESS, no problem with check-in tab

From the Check-in tab, I had checkedin the Dependent Software componets & SAP_ESS 633 Software Component.

But in the Development tab, Import getting the error "Import Failed".

SAP NetWeaver 7.3 EHp1, Software Component: SAP_ESS 633 level 1 In NWDI,  CMS (Change Management Service),

Please find below the error log:

20141203112454 Info   :Starting Step Repository-import at 2014-12-03 11:24:54.0313 +5:00
20141203112454 Info   :Component:sap.com/SAP_ESS
20141203112454 Info   :Version  :MAIN_ERP553PA_C.20120802180711
20141203112454 Info   :1. propagation request is of type TCSSoftwareComponent
20141203112454 Info   :Propagatable:6ffb6762dc7a11e19f5b0000002c4c0b exists allready in the repository. No import necessary.
20141203112838 Fatal  :VcmFailure received
20141203112838 Fatal  :caused by Exception:com.tssap.dtr.client.lib.deltavlib.VcmFailure: Internal Server Error [(pre||post)-condition failed: Internal Server Error]:Internal Server Error [(pre||post)-condition failed: Internal Server Error]
com.tssap.dtr.client.lib.deltavlib.VcmFailure: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
at com.tssap.dtr.client.lib.deltavlib.impl.AbstractCommand.checkedExecute(AbstractCommand.java:197)
at com.tssap.dtr.client.lib.deltavlib.impl.VersionSet.integrate(VersionSet.java:165)
at com.tssap.dtr.client.lib.deltavlib.impl.VersionSet.integrate(VersionSet.java:153)
at com.sap.cms.tcs.client.DTRCommunicator.integrateChangelist(DTRCommunicator.java:545)
at com.sap.cms.tcs.core.RepositoryImportTask.integrateResource(RepositoryImportTask.java:816)
at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:367)
at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:651)
at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:448)
at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:175)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:499)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:112)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:638)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:610)
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:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:172)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:99)
at com.sun.proxy.$Proxy1047.startImport(Unknown Source)
at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1456)
at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2809)
at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:1158)
at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2856)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:326)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:373)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:499)
at com.sap.tc.webdynpro.serverimpl.wdc.ForwardServlet.doPost(ForwardServlet.java:73)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
20141203112838 Fatal  :caused by Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]:communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
at com.sap.cms.tcs.client.DTRCommunicator.integrateChangelist(DTRCommunicator.java:564)
at com.sap.cms.tcs.core.RepositoryImportTask.integrateResource(RepositoryImportTask.java:816)
at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:367)
at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:651)
at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:448)
at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:175)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:499)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:112)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:638)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:610)
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:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:172)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:99)
at com.sun.proxy.$Proxy1047.startImport(Unknown Source)
at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1456)
at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2809)
at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:1158)
at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2856)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:326)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:373)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:499)
at com.sap.tc.webdynpro.serverimpl.wdc.ForwardServlet.doPost(ForwardServlet.java:73)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

20141203112844 Info   :Step Repository-import ended with result 'fatal error' ,stopping execution at 2014-12-03 11:28:44.0337 +5:00

Kindly help.

Thanks and Regards,

Srinivas

Hi All,

We are working on ESS Components which are having few modifications and everything went on well till yesterday. Today we are seeing strange behaviors while activating the activity. It juts throws an error like cache verification failure. Please find below the CBS Request log. Sorry for posting the Build log.

REQUEST PROCESSING started at 2010-09-02 21:59:15.053 GMT

    ACTIVATION request in Build Space "MRCK_HTRESSDV_D" at Node ID: 14,793,550

     [id: 24,237; parentID: 0; type: 4]

     [options: NO OPTIONS]

    Waiting for access: 3 ms

    ===== Pre-Processing =====  started at 2010-09-02 21:59:15.057 GMT

        List of requested for activation activities:

            'sap.com_SAP_ESS_1' compartment

                DHTR094 - TIR236 BE ADDR Subtype Text Display Problem

                    [ISN 171][created by KUMARAPP at 2010-09-02 17:56:21.0][OID 303b3c5db6d211df875b00237da9de6a]

            There is 1 activity in compartment sap.com_SAP_ESS_1

            1 activity will be processed by this request

        Analyze dependencies to predecessor activities... started at 2010-09-02 21:59:15.069 GMT

            Analyzing predecessors in compartment "sap.com_SAP_ESS_1"

                No dependencies to predecessor activities found.

        Analyze dependencies to predecessor activities... finished at 2010-09-02 21:59:15.112 GMT and took 43 ms

        Analyze versions... started at 2010-09-02 21:59:15.112 GMT

            List Active Versions Report: "HTTP/1.1 207 Multi-Status" finished at 2010-09-02 21:59:15.168 GMT and took 55 ms

            Synchronize metadata for [sap.com/ess/be/addr] started at 2010-09-02 21:59:15.170 GMT

                Verification of DL [ws/HTRESSDV/sap.com_SAP_ESS/dev/active/] finished at 2010-09-02 21:59:15.272 GMT and took 19 ms

                Verification of cache (level 2: Comparison of attributes) finished at 2010-09-02 21:59:15.294 GMT and took 21 ms

            Synchronize metadata for [sap.com/ess/be/addr] finished at 2010-09-02 21:59:15.303 GMT and took 133 ms

            < CHANGE > 'sap.com/ess/be/addr' DC

        Analyze versions... finished at 2010-09-02 21:59:15.304 GMT and took 192 ms

        Analyze activities... started at 2010-09-02 21:59:15.304 GMT

            Loading component definitions

            1 component to be build in compartment "sap.com_SAP_ESS_1"

        Analyze activities... finished at 2010-09-02 21:59:15.382 GMT and took 78 ms

        Calculate all combinations of components and variants to be built...

        Analyze request DC BV... started at 2010-09-02 21:59:15.385 GMT

                'sap.com/ess/be/addr' variant 'default'

        Analyze request DC BV... finished at 2010-09-02 21:59:15.487 GMT and took 102 ms

        Prepare build environment in the file system... started at 2010-09-02 21:59:15.488 GMT

            Synchronize development configuration... started at 2010-09-02 21:59:15.488 GMT

            Synchronize development configuration... finished at 2010-09-02 21:59:15.489 GMT and took 1 ms

            Synchronize sources for [sap.com/ess/be/addr] started at 2010-09-02 21:59:15.518 GMT

                Verification of DL [ws/HTRESSDV/sap.com_SAP_ESS/dev/active/] finished at 2010-09-02 21:59:17.890 GMT and took 13 ms

                    Verification of cache FAILED due to the following reasons:

                    Cache inconsistency detected: comparison of cache items on the paths:

                        [/usr/sap/trans/nwdi/CBS/52/.CACHE/1375/DCs/sap.com/ess/be/addr/_comp/src/packages/com/sap/xss/hr/per/be/address/detail/DetailView.wdview_bg.xlf]

                        [ws/HTRESSDV/sap.com_SAP_ESS/dev/active/DCs/sap.com/ess/be/addr/_comp/src/packages/com/sap/xss/hr/per/be/address/detail/DetailView.wdview_bg.xlf]

                    on verification level 2 FAILED:

                    Difference in attribute 'Timestamp' [Thu Oct 23 15:14:02 EDT 2008][Thu Oct 23 15:14:03 EDT 2008]

                    Cache inconsistency detected: comparison of cache items on the paths:

                        [/usr/sap/trans/nwdi/CBS/52/.CACHE/1375/DCs/sap.com/ess/be/addr/_comp/src/packages/com/sap/xss/hr/per/be/address/detail/DetailView.wdview_el.xlf]

                        [ws/HTRESSDV/sap.com_SAP_ESS/dev/active/DCs/sap.com/ess/be/addr/_comp/src/packages/com/sap/xss/hr/per/be/address/detail/DetailView.wdview_el.xlf]

                    on verification level 2 FAILED:

                    Difference in attribute 'Timestamp' [Thu Oct 23 15:14:02 EDT 2008][Thu Oct 23 15:14:03 EDT 2008]

                    Cache inconsistency detected: comparison of cache items on the paths:

                        [/usr/sap/trans/nwdi/CBS/52/.CACHE/1375/DCs/sap.com/ess/be/addr/_comp/src/packages/com/sap/xss/hr/per/be/address/detail/DetailView.wdview_es.xlf]

                        [ws/HTRESSDV/sap.com_SAP_ESS/dev/active/DCs/sap.com/ess/be/addr/_comp/src/packages/com/sap/xss/hr/per/be/address/detail/DetailView.wdview_es.xlf]

                    on verification level 2 FAILED:                    Difference in attribute 'Timestamp' [Thu Oct 23 15:14:02 EDT 2008][Thu Oct 23 15:14:03 EDT 2008]

    Difference in attribute 'Timestamp' [Thu Oct 23 15:14:02 EDT 2008][Thu Oct 23 15:14:03 EDT 2008]

                Verification of cache (level 2: Comparison of attributes) finished at 2010-09-02 21:59:18.498 GMT and took 608 ms

            Synchronize sources for [sap.com/ess/be/addr] finished at 2010-09-02 21:59:18.857 GMT and took 3 s 339 ms

            Synchronize used libraries... started at 2010-09-02 21:59:19.056 GMT

                PP 'FloorplanManager' of DC 'sap.com/pcui_gp/xssfpm' [DCID=1188] (in SC 'sap.com_SAPPCUI_GP_1' [SCID=1373]) ... OK

                PP 'default' of DC 'sap.com/tc/wd/webdynpro' [DCID=592] (in SC 'sap.com_SAP-JEE_1' [SCID=1372]) ... OK

                PP 'default' of DC 'sap.com/com.sap.exception' [DCID=8] (in SC 'sap.com_SAP-JEE_1' [SCID=1372]) ... OK

                PP 'default' of DC 'sap.com/tc/ddic/ddicruntime' [DCID=400] (in SC 'sap.com_SAP_JTECHS_1' [SCID=1376]) ... OK

                PP 'default' of DC 'sap.com/tc/col/api' [DCID=397] (in SC 'sap.com_SAP_JTECHS_1' [SCID=1376]) ... OK

                PP 'default' of DC 'sap.com/tc/wdp/metamodel/content' [DCID=415] (in SC 'sap.com_SAP_JTECHS_1' [SCID=1376]) ... OK

                PP 'default' of DC 'sap.com/com.sap.mw.jco' [DCID=12] (in SC 'sap.com_SAP-JEE_1' [SCID=1372]) ... OK

                PP 'default' of DC 'sap.com/com.sap.aii.proxy.framework' [DCID=336] (in SC 'sap.com_SAP_JTECHS_1' [SCID=1376]) ... OK

                PP 'default' of DC 'sap.com/tc/logging' [DCID=11] (in SC 'sap.com_SAP-JEE_1' [SCID=1372]) ... OK

                PP 'default' of DC 'sap.com/com.sap.aii.util.misc' [DCID=337] (in SC 'sap.com_SAP_JTECHS_1' [SCID=1376]) ... OK

                PP 'FPMUtils' of DC 'sap.com/pcui_gp/xssutils' [DCID=1189] (in SC 'sap.com_SAPPCUI_GP_1' [SCID=1373]) ... OK

                PP 'default' of DC 'sap.com/tc/ddic/metamodel/content' [DCID=117] (in SC 'sap.com_SAP_JTECHS_1' [SCID=1376]) ... OK

                PP 'default' of DC 'sap.com/tc/cmi' [DCID=396] (in SC 'sap.com_SAP_JTECHS_1' [SCID=1376]) ... OK

                PP 'InternationalPersInfo' of DC 'sap.com/ess/per' [DCID=844] (in SC 'sap.com_SAP_ESS_1' [SCID=1375]) ... OK

            Synchronize used libraries... finished at 2010-09-02 21:59:20.986 GMT and took 1 s 930 ms

            Error! The state of the source cache is INCONSISTENT for at least one of the request DCs. The build might produce incorrect results.

        Prepare build environment in the file system... finished at 2010-09-02 21:59:20.987 GMT and took 5 s 499 ms

    ===== Pre-Processing =====  finished at 2010-09-02 21:59:20.988 GMT and took 5 s 931 ms

    Waiting for access: 3 ms

    ===== Processing =====  started at 2010-09-02 21:59:20.991 GMT

        BUILD DCs

            'sap.com/ess/be/addr' in variant 'default'

                The build was SUCCESSFUL. Archives have been created.

    ===== Processing =====  finished at 2010-09-02 22:00:31.588 GMT and took 1 m 10 s 597 ms

    ===== Post-Processing =====

    Waiting for access: 14 ms

    ===== Post-Processing =====  started at 2010-09-02 22:00:31.603 GMT

        Check whether build was successful for all required variants...

            "sap.com/ess/be/addr" in variant "default"   OK

        STORE activation build results... started at 2010-09-02 22:00:33.402 GMT

            Update DC metadata... started at 2010-09-02 22:00:33.408 GMT

                'sap.com/ess/be/addr' DC is CHANGED

            Update DC metadata... finished at 2010-09-02 22:00:33.539 GMT and took 131 ms

            STORE build results... started at 2010-09-02 22:00:33.540 GMT

                "sap.com/ess/be/addr": store meta-data

                "sap.com/ess/be/addr" in "default" variant  is PROCESSED

            STORE build results... finished at 2010-09-02 22:00:35.549 GMT and took 2 s 9 ms

        STORE activation build results... finished at 2010-09-02 22:00:35.549 GMT and took 2 s 147 ms

        Change request state from PROCESSING to SUCCEEDED

        Analyze effect of applied changes to buildspace state... started at 2010-09-02 22:00:35.550 GMT

            Handle Cycles... started at 2010-09-02 22:00:35.572 GMT

                No new cycles detected.

            Handle Cycles... finished at 2010-09-02 22:00:39.175 GMT and took 3 s 603 ms

            Determine components that have become DIRTY due to the results of this request started at 2010-09-02 22:00:39.296 GMT

                No such components have been found.

            Determine components that have become DIRTY due to the results of this request finished at 2010-09-02 22:00:39.297 GMT and took 1 ms

            The following Internal Build Requests will be canceled because Request DCBVs are already built by this request

            INTERNAL BUILD request in Build Space "MRCK_HTRESSDV_D" at Node ID: 14,793,550

     [id: 24,165; parentID: 23,837; type: 32]

        Analyze effect of applied changes to buildspace state... finished at 2010-09-02 22:00:41.498 GMT and took 5 s 948 ms

        Integrate activities into active workspace(s)...

        Integration of activities in compartment "sap.com_SAP_ESS_1" started at 2010-09-02 22:00:41.505 GMT

        Integration of 1 activities in compartment "sap.com_SAP_ESS_1" finished at 2010-09-02 22:00:42.826 GMT and took 1 s 321 ms

        An incomplete integration in compartment "sap.com_SAP_ESS_1" of buildspace "MRCK_HTRESSDV_D" has resulted because of errors during request processing!

Request 24238 has been created to re-initialize the compartment

    ===== Post-Processing =====  finished at 2010-09-02 22:00:42.852 GMT and took 11 s 249 ms

    Change request state from SUCCEEDED to FAILED

    Error! The following problem(s) occurred  during request processing:

    Error! Communication error when performing integrations. Integration failed with unexpected CONFLICT status [com.sap.dtr.client.lib.protocol.entities.ErrorEntity@5719ce2c]. Request FAILED.

REQUEST PROCESSING finished at 2010-09-02 22:00:42.865 GMT and took 1 m 27 s 812 ms

Regards,

Nagarajan

Good morning experts.

I have got a problem with SAP NWDS 7.3.

I would like to deploy a JSP-Site on SAP NetWeaver Portal 7.3.

The following steps I have done up to now:

- Creating a Track in SAP NWDI with 1 Software Component (including SAP ENGFACADE 7.30 and SAP BUILD 7.30)

- Creating a new DC: Java EE -> Web Module in Development Infrastructure Perspective

- Java EE Perspective: In the Project Explorer: Right-Click on my Software Compoent: New -> JSP

- Writing the sourcecode of the JSP (only HTML)

- Open Activities View: Checked-In the Open Activity

- Activation View: Activate the Activity

So: What do I have to do, if I want to deploy my JSP on a SAP NetWeaver Portal 7.3 - System?

What Setiings do I have to set up in the Preferences in the NWDS?

(Do I have to set up a "SAP AS Java" in the Prefernences?

What do I have to write in the fields: Instance Host Name, Instance Number) ?

Thank you for answering.

Dear Experts ,

I am working on SAP PI 7.31 and , want to learn BPM but I am confused about it .

What is the  advantage of BPM and Why should we use BPM in SAP PI .

If possible  please send me some references of BPM

Regards ,

Pradeep

Dear all,

After some struggling I managed to configure NWDI (but "only" with CMS, not CM services).

Deployment to DEV system works.

And I really enjoy to have code versioning now!

But I've still some questions:

In NWDS in the 'Composite Designer' perspective not all the DCs appear the same way:

Some seem to belong to Development Configuration T62_dev, some to T62_T62_D.
What's the reason for that difference?

In CMS I have only one track:

In NWDS DTR perspective I see only Development Configuration T62_62...

It seems that T62_62 is the internal name:

Can I make that somehow align in "Composite designer' perspective?

By the way:
Why do I see so many availabel Development Configurations in NWDS?

Most of them have already been deleted...

How can I delete SANDBOX_dev etc.?

Thanks in advance!

Best regards,

Thorsten.

HI Experts,

We are experiencing an broken DC's in CBS.

The DC's are not broken in NWDS and the whole application is working when deployed in the Enterprise Portal.

We are getting this error in the log file:

[wdgen] [Warning]ContextAttribute 'Uin.structureElement': All attributes of the corresponding context node have to be bound to fields of a dictionary structure

[wdgen] [Error]ContextAttribute 'Uin.referencedProperty': The context attribute references a model property which has been removed //WebDynpro/ModelClass:com.dc_model.models.prfmodel.Zfxx_Prf_Hd/Property:Uin Hint:Delete the model binding or rebind the attribute.

Checked the model and context attribute is in prf_hd.

What could be the cause of this problem and how can we solve this?

Regards,

Greg

Hi Exports,

1>>> I have a DC like ESS personal Information Application (This application was standard java Application) in this application i wanted to customised  .. i this application i wanted to add some custom fields.

  In my company client not Using NWDI  ..  basically in this scenario we will create NWDI track and import into NWDS..

in  my case  my client  not using NWDI...  so i wanted to customize this application kindly help me how can we do ASAP.

Please kindly send me set by step process i am very new to this

Regards,

Vreddy

Hi All,

I am working on a BPM process and we have NWDI configured. Lately I had to change my laptop and since then I have been having this problem that when I make changes to any of the BPMs , I am able to build the DC, however checking-in of the activity fails with either of the 2 errors:

• FAILED: CHECKIN on activity <activy name> failed : :Failed to execute operations. macro execution failed [cause: Bad Request]
• FAILED: CHECKIN on activity <activity name>failed : :Failed to execute operations. macro execution failed [cause: Communication error [cause: Connection reset]]

Mostly, I get the first error once and then subsequent attempts end in second error.

Please note that I have tried to create new workspace, creating new DCs etc, but no luck so far.

NWDS version: SAP Enhancement Package 1 for SAP NetWeaver Developer Studio 7.3 SP10 PAT0008

NWDI: 7.4 SP 5

Full text of error log from second exceptions is below:

java.net.SocketException: Connection reset

  at java.net.SocketInputStream.read(SocketInputStream.java:168)

  at java.net.SocketInputStream.read(SocketInputStream.java:182)

  at com.sap.dtr.client.lib.protocol.streams.ChunkedInputStream.readLine(ChunkedInputStream.java:328)

  at com.sap.dtr.client.lib.protocol.streams.ResponseStream.readLine(ResponseStream.java:274)

  at com.sap.dtr.client.lib.protocol.impl.Response.initialize(Response.java:478)

  at com.sap.dtr.client.lib.protocol.Connection.getResponse(Connection.java:2698)

  at com.sap.dtr.client.lib.protocol.Connection.sendInternal(Connection.java:1615)

  at com.sap.dtr.client.lib.protocol.Connection.send(Connection.java:1478)

  at com.sap.dtr.client.lib.protocol.requests.RequestBase.perform(RequestBase.java:555)

  at com.sap.dtr.client.lib.protocol.requests.RequestBase.perform(RequestBase.java:685)

  at com.tssap.dtr.client.lib.deltavlib.impl.DeltavCommand.uncheckedExecute(DeltavCommand.java:189)

  at com.tssap.dtr.client.lib.deltavlib.impl.DeltavCommand.execute(DeltavCommand.java:49)

  at com.tssap.dtr.client.lib.deltavlib.impl.Macro.executeMacro(Macro.java:338)

  at com.tssap.dtr.client.lib.deltavlib.impl.Macro.execute(Macro.java:446)

  at com.tssap.dtr.client.lib.vfs.impl.VFSOperationsGroup.executeMacro(VFSOperationsGroup.java:492)

  at com.tssap.dtr.client.lib.vfs.impl.VFSOperationsGroup.perform(VFSOperationsGroup.java:421)

  at com.tssap.dtr.client.lib.vfs.actions.CheckinAction.pureExecute(CheckinAction.java:70)

  at com.tssap.dtr.client.lib.vfs.actions.BaseAction$1.run(BaseAction.java:55)

  at com.tssap.dtr.client.lib.vfs.impl.VfsEventManager.run(VfsEventManager.java:146)

  at com.tssap.dtr.client.lib.vfs.actions.BaseAction.execute(BaseAction.java:51)

  at com.tssap.dtr.client.eclipse.ui.actions.VfsObjectSelectionAction$4.doDtrJobInWorkerThread(VfsObjectSelectionAction.java:540)

  at com.tssap.dtr.client.eclipse.job.DtrJob$2.run(DtrJob.java:154)

  at com.sap.ide.dii05.util.internal.lock.DiiConsistencyServiceImpl$1.run(DiiConsistencyServiceImpl.java:120)

  at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)

  at com.sap.ide.dii05.util.internal.lock.DiiConsistencyServiceImpl.executeConsistentWorkspaceRunnable(DiiConsistencyServiceImpl.java:90)

  at com.sap.ide.dii05.util.internal.lock.DiiConsistencyServiceImpl.executeConsistentWorkspaceRunnable(DiiConsistencyServiceImpl.java:52)

  at com.sap.ide.dii05.util.internal.lock.DiiConsistencyServiceImpl.executeInWorkspaceAndDevConfLocks(DiiConsistencyServiceImpl.java:126)

  at com.tssap.dtr.client.eclipse.job.DtrJob.runInSync(DtrJob.java:147)

  at com.tssap.dtr.client.eclipse.job.DtrJob.syncExec(DtrJob.java:127)

  at com.tssap.dtr.client.eclipse.ui.actions.VfsObjectSelectionAction.executeFinalVfsAction(VfsObjectSelectionAction.java:549)

  at com.tssap.dtr.client.eclipse.ui.actions.CheckinActivityAction$2.doDtrJobInWorkerThread(CheckinActivityAction.java:136)

  at com.tssap.dtr.client.eclipse.job.DtrJob$2.run(DtrJob.java:154)

  at com.sap.ide.dii05.util.internal.lock.DiiConsistencyServiceImpl$1.run(DiiConsistencyServiceImpl.java:120)

  at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)

  at com.sap.ide.dii05.util.internal.lock.DiiConsistencyServiceImpl.executeConsistentWorkspaceRunnable(DiiConsistencyServiceImpl.java:90)

  at com.sap.ide.dii05.util.internal.lock.DiiConsistencyServiceImpl.executeConsistentWorkspaceRunnable(DiiConsistencyServiceImpl.java:52)

  at com.sap.ide.dii05.util.internal.lock.DiiConsistencyServiceImpl.executeInWorkspaceAndDevConfLocks(DiiConsistencyServiceImpl.java:126)

  at com.tssap.dtr.client.eclipse.job.DtrJob.runInSync(DtrJob.java:147)

  at com.tssap.dtr.client.eclipse.job.DtrJob.access$000(DtrJob.java:27)

  at com.tssap.dtr.client.eclipse.job.DtrJob$1.run(DtrJob.java:94)

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

      [Error: com.sap.dtr.client.lib.protocol.requests.RequestBase  Thread[ModalContext,6,main]]

I don't see any logs in the .log file for first exception.

Has anyone had this error before?

Thanks,

Sanjeev.

Hi experts,

Just wanted to ask if anybody also encounter the issue me and my colleagues get when using NWDS 7.3?

Whenever we click something, the response time is very slow.

This is such a pain, especially when checking Context Mappings.

We have tried closing all other projects we have except for the one we are working on but the application is still hanging up.

We also do not encounter this issue in NWDS 7.0 even if we have a lot of open projects.

Any advise we could do?

NWDS Version:

SAP Enhancement Package 1 for SAP NetWeaver Developer Studio 7.3 SP08 PAT0002

Thanks,

Vey

Hello,

I checkout and checkin,activate my changes for Webdynpro Java Applications in NWDS. But after running the Activation process...the Activation status shows as Succeeded but the Deployment status shows as 'Unknown' with a Question mark..my question is why the Deployment status is not shown as Succeeded....

Any help would be highly appreciated.

Regards,

Shikhil

Hi

When I am trying to Import the track in NWDS 7.3 I am getting the following error.

"some infrastructure servers cannot be contacted"

I am trying to Import from System Landscape Directory

and in Windows --> Preferences --> Development Infrastructure --> System Landscape Directory

When I place the URL and click on Ping

The Ping is successful

When I am trying to import a New Development Configuration by doing Import from System Landscape Directory and I can see all my tracks and everything

I can see Remote Development Configuration

But when I try to logon to Development Infrastructure it gives me the following error

"some infrastructure servers cannot be contacted"

Can some one let me know what I need to do to resolve this error.

Regards

JM

hi experts ,

im deleted a dc directly in the DTR at dev- inactive work space  and now im trying to delete the same from the configuration at my studio , but im getting the below error can any one please help me to resolve the issue..

Error while getting component root folder: Could not get VFS folder item (DTR client returned null) for browsePath :/WDJADEV/****.com_MYCOMPONENTS/dev/inactive/DCs/****/prt_dev/****util/_comp/ (Could not get VFS folder item (DTR client returned null) for browsePath :/WDJADEV/****.com_MYCOMPONENTS/dev/inactive/DCs/****/prt_dev/****util/_comp/)

com.sap.tc.devconf.RepositoryAccessException: Error while getting component root folder: Could not get VFS folder item (DTR client returned null) for browsePath :/WDJADEV/****.com_MYCOMPONENTS/dev/inactive/DCs/****/prt_dev/****util/_comp/ (Could not get VFS folder item (DTR client returned null) for browsePath :/WDJADEV/****.com_MYCOMPONENTS/dev/inactive/DCs/****/prt_dev/****util/_comp/)

at com.sap.tc.devconf.impl.dtr.DtrServiceAdapter.getVfsComponentRootFolder(DtrServiceAdapter.java:694)

at com.sap.tc.devconf.internal.DevelopmentComponentNode.getVfsComponentRootFolder(DevelopmentComponentNode.java:596)

at com.sap.ide.dii08.internal.commandz.RefreshChildrenCommand$1.caseDevelopmentComponent(RefreshChildrenCommand.java:365)

at com.sap.ide.dii05.model.internal.util.ComponentModelSwitch.doSwitch(ComponentModelSwitch.java:230)

at com.sap.ide.dii05.model.internal.util.ComponentModelSwitch.doSwitch(ComponentModelSwitch.java:144)

at com.sap.ide.dii05.model.internal.util.ComponentModelSwitch.doSwitch(ComponentModelSwitch.java:130)

at com.sap.ide.dii08.internal.commandz.RefreshChildrenCommand.execute(RefreshChildrenCommand.java:104)

at com.sap.ide.dii08.internal.service.CommandExecutor.executeInDevConfLock(CommandExecutor.java:34)

at com.sap.ide.dii08.internal.service.InternalDiiCommandService.refreshChildren(InternalDiiCommandService.java:630)

at com.sap.ide.dii05.ui.internal.views.browser.contentprovider.WaitingNodeProvider$RefreshInBackgroundAndThenExpand$2.run(WaitingNodeProvider.java:77)

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

Caused by: com.sap.tc.devconf.NoRemoteFolderItemException: Could not get VFS folder item (DTR client returned null) for browsePath :/WDJADEV/****.com_MYCOMPONENTS/dev/inactive/DCs/****/prt_dev/****util/_comp/

at com.sap.tc.devconf.impl.dtr.VFSHandler.getSubFolderFromVfsFolder(VFSHandler.java:803)

at com.sap.tc.devconf.impl.dtr.DtrServiceAdapter.getVfsComponentRootFolder(DtrServiceAdapter.java:683)

... 10 more

Regards

Govardan Raj

Dear experts,

I am trying to import a track from NWDI so I can add development components to a software component in the track.  The problem I am having is:

I keep getting this error " Syntax of 'nibco.com/nbdc/nibcotst' is not valid : Invalid name: appropriate prefix not found; choose another name or another name server".  We haven't had this problem in the past...When I go to CMS->Landscape Configurator and click on display development configuration button I get this configuration:

The url for name-server-url property is correct: http://xxxxxxxx:xxxxx/sld/cimom

But when I import to NWDS the url get's changed:

One NWDS:

Another NWDS:

For some reason it is changing the naming server url on import to http://xxxxxx:xxxxx/sld/name and http://xxxxxxxx:xxxxx/sld.  Any help is much appreciated.

Thanks,

Bradley Sorensen

Hello,

This is our first time using SUM/MOpz for a release upgrade procedure as the last JSPM update disabled the launch program.

During our test upgrade of our Enterprise Portal HUB landscape (source NW 7.02 -> target NW 7.4) with EHP5 for ERP 6.0 - XSS Self Services for backend ERP system installed. I've encountered an issue with SUM in the Configuration stage - Target Release Components screen. the only 5 objects SUM cannot handle automatically are the XSS Self Services target release components:

SAPPCUI_GP         633

SAP_ESS               633

SAP_ESS_LGP     633

SAP_MSS               630

UTXSSLGP             633

The only option I have is to scan inbox to rebuild the component list. I'm assuming, since these components are being modified by us and delivered/deployed thru NWDI track, their source location on the system is now the track name instead of the SAP delivered MAIN_ERP53VAL_C. Which means that SUM is expecting updated modified SCAs from NWDI for new 633 versions in the download directory before proceeding to next phase. However, in NWDI landscape configurator for this track, I have checked the option to mark system in NWDI control and verified SUM recognizes the system as NWDI controlled.

I'm struggling to understand the where the disconnect is between SUM and NWDI for theses components as I thought that SUM is supposed to ignore the DEV NWDI developed and wait for updates modified SCAs only in QA and PROD. Does anyone else have experience with this process to help me?

Regards,

Paul

Hi Experts,

I had created a J2EE DC some months back and I didn't check in the same since I had been asked to stop the development for a while. After that, I had to re-import the DTR track for some other requirement and I think because of which that particular DC got deleted. Now I have to continue to work on the same and I am in trouble since I am unable to find the DC's. Is it possible to recover DC's which has got deleted. I am able to see the DC's under inactive sources of my DC. Is there any chance for recovering them ?

Any help would be much appreciated.

thanks and regards

Shriniwash