hi,

i have placed EPBUILDT13_0-10003786.SCA in the inbox folder but while trying to check in in CMS, its not listed in the table.

Is there any setting to be done.??

NW version : 7.0 SP 13.

--

harish

Hi,

Last week we had several errors appearing related to CBS workspaces not being owned correctly and NWDI)(CBS) Cannot instantiate buildspace administrator.

I found a similar details on this link so followed the instructions given

https://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29%28CBS%29+Cannot+instantiate+buildspace+administrator

Now when I go back into CMS Landscape Configurator and select Save on the Track Data, the spinning icon comes up for a couple of seconds

and then an error appears at the bottom of the page :

I have traced this back to the application log file which reports :

[037ffffffa0ffffffd20020ffffffd4]#n/a##3a8a47c08a6f11e2c0b5001a648f9412#SAPEngine_Application_Thread[impl:3]_19ID\#(J2EE306565100)ID0833399350DB58f018f154848257b22f8732705a50ab4bda9dc0End.29ffa6118a6b11e29843001a648f9412##0#0#Error#1#com.sap.cms.pcs.conf.manager.CmsConfManager#Plain###com.sap.cms.util.exception.CMSUnexpectedException

at com.sap.cms.pcs.conf.manager.CmsConfManager.editTrackConfiguration(CmsConfManager.java:808)

at com.sap.cms.pcs.conf.manager.proxy.CmsConfProxyBean.editTrackConfiguration(CmsConfProxyBean.java:289)

at com.sap.cms.pcs.conf.manager.proxy.LocalCmsConfProxyLocalObjectImpl0_0.editTrackConfiguration(LocalCmsConfProxyLocalObjectImpl0_0.java:1936)

at com.sap.cms.ui.landconf.LandConfController.editTrack(LandConfController.java:2936)

at com.sap.cms.ui.landconf.wdp.InternalLandConfController.editTrack(InternalLandConfController.java:1310)

at com.sap.cms.ui.landconf.LandConfController.decideSaveOrEdit(LandConfController.java:5170)

at com.sap.cms.ui.landconf.wdp.InternalLandConfController.decideSaveOrEdit(InternalLandConfController.java:1378)

at com.sap.cms.ui.landconf.SingleTrack.saveTrack(SingleTrack.java:318)

at com.sap.cms.ui.landconf.wdp.InternalSingleTrack.saveTrack(InternalSingleTrack.java:1522)

at com.sap.cms.ui.landconf.SingleTrack.onActionSaveTrack(SingleTrack.java:696)

at com.sap.cms.ui.landconf.wdp.InternalSingleTrack.wdInvokeEventHandler(InternalSingleTrack.java:1575)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)

at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101)

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304)

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)

at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

Caused by: com.sap.cms.util.exception.CMSUnexpectedException

at com.sap.cms.pcs.conf.communicator.DTRConfCommunicator.createWorkspace(DTRConfCommunicator.java:143)

at com.sap.cms.pcs.conf.core.services.SystemManagerObject.addCompartment(SystemManagerObject.java:567)

at com.sap.cms.pcs.conf.core.plugin.DefaultTrack.newTrack(DefaultTrack.java:163)

at com.sap.cms.pcs.conf.core.TrackManager.editTrack(TrackManager.java:139)

at com.sap.cms.pcs.conf.manager.CmsConfManager.editTrackConfiguration(CmsConfManager.java:744)

... 36 more

Caused by: java.lang.NullPointerException

at com.sap.cms.pcs.conf.communicator.DTRConfCommunicator.createWorkspace(DTRConfCommunicator.java:124)

... 40 more

#

#1.5 #001A648F94120077000007CB00002B7C0004D7A95177E994#1363022123097#/Applications/CMS#sap.com/tc~wd~dispwda#com.sap.cms.ui.landconf.LandConfController#Administrator#38347##n/a##3a8a47c08a6f11e2c0b5001a648f9412#SAPEngine_Application_Thread[impl:3]_19ID\#(J2EE306565100)ID0833399350DB58f018f154848257b22f8732705a50ab4bda9dc0End.29ffa6118a6b11e29843001a648f9412##0#0#Error#1#com.sap.cms.ui.landconf.LandConfController#Plain###CMSUnexpectedExcepiton null#

The Default.Trc file doesn't get update when I generate the error, so wondering if there are anymore log files with more info.

Many thanks,

Sean Collins

Hi All,

I am new to NWDI. Currently we have to move some tracks from old NWDI [for 7.0 portal] to a new one [for 7.3]. It was agreed upon to follow the procedure as per the link "http://help.sap.com/saphelp_nw73/helpdata/en/49/101b273d9d132ee10000000a421937/frameset.htm" as all data and history has to be maintained. As per method desribed here ".. >> Choose the Change Management Service link. >> Choose the Landscape Configurator link and change the DTR URL in the track configuration of TRACK1 from SRCDTR to TGTDTR. >>To create a copy of TRACK1, choose Save As. Name the track TRK1CPY .." This "Save As" operation is throwing error as it cannot access the target DTR. Since we are performing the steps in old NWDI CMS, it should be able to access the new NWDI DTR [with separate CMS, SLD, CBS, DTR]. But cannot figure how to do it. Do we have to maintain same CMS Admin user id and paasowrd in the new NWDI as the old one??

Please help.

... -.-.

Hello Experts,
  We are migrating tracks from 7.0 to 7.31 ,
We have followed the following procedure to do the same.

1)Downloaded the SC from old NWDI and imported to the new one

2)after creating a track we added the imported SC and added 7.31 relevant dependencies(

SAP_BUILDT

EP_BUildT

ENGFACADE

FRAMEWORK

WD-RUNTIME

COMP_BUILDT

ECM-CORE

ESCONF_BUILDT

ESF

MOIN_BUILDT

ENGINEAPI)

3) Added .SCA files related to these std SC in inbox folder

4)Updated CMS

5)Check in the SC (Std and Custom) till assembly

6)Now when i go to CMS and see i find  various DC to be broken and few dirty few metadata ,used DC in Red signal.

Kindly suggest where we are going wrong.

Thanks ,

Regards,

Prajakta K

Hello Experts.

I have got a new project now:

I want to generate a JSP and deploy it on SAP NetWeaver Portal 7.3.

First of all, I installed NetWeaver Developer Studio 7.3 with JDK 1.6.0_21.

We are using a NWDI 7.01 SP 7.

My Problem:

On our SAP NetWeaver Portal 7.3 is a JDK 6 (1.6.0_21) running.....When I create a new Track in our NWDI, it has to be build by the Component Build Service also with JDK 6....

Can you tell me, how I set up the required JDK only for that new Track - but not as default for all Tracks in the NWDI.

P.S. It would be also very nice, if someone could confirm me, that the only required Software Component (SC) I need for deploying on NW Portal 7.3 is called: "SAP BUILD TOOL 7.3".

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,

I tried to install NWDW based on NetWeaver Release 7.02. I have found the following installation guide:

https://websmp107.sap-ag.de/~sapidb/011000358700000029522013E/devworkplace_lkg70x.pdf

I downloaded all software mentioned there:

- MS SQL (RDBMS MSSQLSRV 2008 R2 incl. SP1, 51044827),

- Software Provisioning Manager (70SWPM10SP02_3-20009707.sar),

- Developer Workplace (NW 7.0 EHP2 Dev. WP for SWPM, 51045450),

- SAPCAR (SAPCAR_315-20010453.EXE), and

- JSPM and software components (CRMDIC & SHRAPP) that I want to deploy later on the JEE server.

I unpacked everything in separate directories: mssql_extracted, swpm_extracted, and nwdw_extracted.

From there I installed first MS SQL.

Then I tried to install NW Developer Workplace by means of Software Provisioning Manager. But when starting sapinst.exe from directory swpm_extracted, it does not offer me developer workplace like described in the installation guide. I could not find it anywhere in the software delivery tool gui.

Any hint how I can add it there or install it?

Thanks in advance,

Br,

  Michael

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

Hi Guys,

I am trying to patch a SAP NW CE 7.2 system from SP1 to SP8.I had issues for 2 software components while trying to patch using the standard patching tool JSPM.

So I thought of patching just those 2 components using another tool - SUM- Software Update Manager.

In this tool it gives me an error - Cannot detect NWDI system role. Could not get NWDI system role from CVERS. com.sap.sl.util.cvers.api.CVersAccessException: CMSRTS, getModifiedComponents: unknown DB schema, can not write data com.sap.sl.util.cvers.api.CVersAccessException: CMSRTS, getModifiedComponents: unknown DB schema, can not write data

On the JSPM screen it says "System is not under NWDI control" which is correct.The guy who had installed this system has also included the usage type DI which was not needed in the first place.No initial configuration  NWDI  have been ever performed on this system and still while JSPM is not complaining on the NWDI role,SUM is complaining. Do I have to do some initial setup wrt NWDI component so that SUM will pick the right NWDI role.

Hello Experts,
  We are migrating tracks from 7.0 to 7.31 ,
We have followed the following procedure to do the same.

1)Downloaded the SC from old NWDI and imported to the new one

2)after creating a track we added the imported SC and added 7.31 relevant dependencies(

SAP_BUILDT

EP_BUildT

ENGFACADE

FRAMEWORK

WD-RUNTIME

COMP_BUILDT

ECM-CORE

ESCONF_BUILDT

ESF

MOIN_BUILDT

ENGINEAPI)

3) Added .SCA files related to these std SC in inbox folder

4)Updated CMS

5)Check in the SC (Std and Custom) till assembly

6)Now when i go to CMS and see i find  various DC to be broken and few dirty few metadata ,used DC in Red signal.

Kindly suggest where we are going wrong.

Thanks ,

Regards,

Prajakta K

Hello,

I read the solution for the discussion http://scn.sap.com/thread/2079515.

Now I have the same problem, but we used the SAPJVM_4 on the NWDI 7.01.

The location is JAVA_HOME=/usr/sap/<SID>/JC00/exe/sapjvm_4 on AIX server.

Do I have to install SAPJVM_6 on NWDI 7.01? Can I copy it from the SAP NetWeaver Portal 7.3?

And then set the settings describt in disc. 2079515?

Thanks for help

Christian

Hi,

We are using SAP NWDS 7.3 SP09 and according to it's help for configuring NWDS to connect to the SLD that contains NWDI landscape information, we are to:

Choose WindowPreferences Development Infrastructure LandscapeDirectory.

However after clicking on Window->Preference we have no 'Development Infrastructure' option available to us.

Can anyone shed any light on this please?

We are completely new to NWDI & NWDS so forgive us for missing something glaringly obvious !!!!

Hello SDN!

I want to build CRM ISA 5.0 application locally thru NWDS. This application uses Development Component technology. In the NWDI server track for this application has a build variant "default" with key "com.sap.jdk.home_path_key" and value for this key "JDK1.4.2_HOME".

When I try to build it locally I've got an error:

Error: com.sap.tc.buildplugin.util.BuildPluginException: No JDK_HOME_PATH defined for key 'JDK1.4.2_HOME'     at com.sap.tc.buildplugin.JavaMacroContextProvider.setupJavaCompiler(JavaMacroContextProvider.java:235)     at com.sap.tc.buildplugin.JavaMacroContextProvider.setupJavaEnvironment(JavaMacroContextProvider.java:180)     at com.sap.tc.buildplugin.JavaMacroContextProvider.execute(JavaMacroContextProvider.java:35)     at com.sap.tc.buildplugin.PrepareContextBuildStep.prepareTechnologySpecificData(PrepareContextBuildStep.java:187)     at com.sap.tc.buildplugin.PrepareContextBuildStep.setupBuildFileCreatorContext(PrepareContextBuildStep.java:95)     at com.sap.tc.buildplugin.PrepareContextBuildStep.execute(PrepareContextBuildStep.java:56)     at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:196)     at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:168)     at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)     at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)     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.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:350)     at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:99)     at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:73)     at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:59)     at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1750)     at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:6004)     at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction.buildDCsForDevConfig(BuildAction.java:307)     at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction.access$200(BuildAction.java:58)     at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction$1.run(BuildAction.java:212)     at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
Error: Build stopped due to an error: No JDK_HOME_PATH defined for key 'JDK1.4.2_HOME'

I've created system environment variables JDK_HOME_PATH, JAVA_HOME and JDK1.4.2_HOME pointed to C:\j2sdk1.4.2_17. In NWDS parameter "Installed JREs" pointed to C:\j2sdk1.4.2_17. Nothing effect.

How to build this application locally?

Regards, Lev

Hi All,

I have a portal & webdynpro application in the form of a single .sca file.

I unzipped the file using winzip and got two files - .ear and .epa.

I want to import this in NWDS to view the code and make some changes in webdynpro.

Can anybody give me the step by step procedure to do this?

Will surely award points for useful answers.

thanks

Juhi Kulshreshtha

Hi,

I've run the configuration wizard "DI Change Management Service (CMS): Create an Application Skeleton" on a BPM runtime system (NW 7.31 SP06) to create an NWDI track for my BPM project. I accordingly chose the "BPM application 7.3" configuration template to set the needed dependencies and to copy the necessary SAP SCAs to the NWDI track.

When I tried it the first time the SAP BPEM software components were empty. They didn't contain any DCs. So I imported them manually into the NWDI track.

Unfortunately this track got corrupted when checking in the first sources. So I deleted the track in the CMS, all software components and products in the SLD and all repositories in the DTR.

But when running the configuration wizard "DI Change Management Service (CMS): Create an Application Skeleton" again not only the BPEM SCs are empty but all of the SAP software components. None of them contains any DCs.

I don't want to manually add all the missing SCAs to the track as this is what the wizard is made for.

So what's the problem with this wizard? What's going wrong?

Any ideas?

Best regards,

Robert

Hi,

Last week we had several errors appearing related to CBS workspaces not being owned correctly and NWDI)(CBS) Cannot instantiate buildspace administrator.

I found a similar details on this link so followed the instructions given

https://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29%28CBS%29+Cannot+instantiate+buildspace+administrator

Now when I go back into CMS Landscape Configurator and select Save on the Track Data, the spinning icon comes up for a couple of seconds

and then an error appears at the bottom of the page :

I have traced this back to the application log file which reports :

[037ffffffa0ffffffd20020ffffffd4]#n/a##3a8a47c08a6f11e2c0b5001a648f9412#SAPEngine_Application_Thread[impl:3]_19ID\#(J2EE306565100)ID0833399350DB58f018f154848257b22f8732705a50ab4bda9dc0End.29ffa6118a6b11e29843001a648f9412##0#0#Error#1#com.sap.cms.pcs.conf.manager.CmsConfManager#Plain###com.sap.cms.util.exception.CMSUnexpectedException

at com.sap.cms.pcs.conf.manager.CmsConfManager.editTrackConfiguration(CmsConfManager.java:808)

at com.sap.cms.pcs.conf.manager.proxy.CmsConfProxyBean.editTrackConfiguration(CmsConfProxyBean.java:289)

at com.sap.cms.pcs.conf.manager.proxy.LocalCmsConfProxyLocalObjectImpl0_0.editTrackConfiguration(LocalCmsConfProxyLocalObjectImpl0_0.java:1936)

at com.sap.cms.ui.landconf.LandConfController.editTrack(LandConfController.java:2936)

at com.sap.cms.ui.landconf.wdp.InternalLandConfController.editTrack(InternalLandConfController.java:1310)

at com.sap.cms.ui.landconf.LandConfController.decideSaveOrEdit(LandConfController.java:5170)

at com.sap.cms.ui.landconf.wdp.InternalLandConfController.decideSaveOrEdit(InternalLandConfController.java:1378)

at com.sap.cms.ui.landconf.SingleTrack.saveTrack(SingleTrack.java:318)

at com.sap.cms.ui.landconf.wdp.InternalSingleTrack.saveTrack(InternalSingleTrack.java:1522)

at com.sap.cms.ui.landconf.SingleTrack.onActionSaveTrack(SingleTrack.java:696)

at com.sap.cms.ui.landconf.wdp.InternalSingleTrack.wdInvokeEventHandler(InternalSingleTrack.java:1575)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)

at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101)

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304)

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)

at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

Caused by: com.sap.cms.util.exception.CMSUnexpectedException

at com.sap.cms.pcs.conf.communicator.DTRConfCommunicator.createWorkspace(DTRConfCommunicator.java:143)

at com.sap.cms.pcs.conf.core.services.SystemManagerObject.addCompartment(SystemManagerObject.java:567)

at com.sap.cms.pcs.conf.core.plugin.DefaultTrack.newTrack(DefaultTrack.java:163)

at com.sap.cms.pcs.conf.core.TrackManager.editTrack(TrackManager.java:139)

at com.sap.cms.pcs.conf.manager.CmsConfManager.editTrackConfiguration(CmsConfManager.java:744)

... 36 more

Caused by: java.lang.NullPointerException

at com.sap.cms.pcs.conf.communicator.DTRConfCommunicator.createWorkspace(DTRConfCommunicator.java:124)

... 40 more

#

#1.5 #001A648F94120077000007CB00002B7C0004D7A95177E994#1363022123097#/Applications/CMS#sap.com/tc~wd~dispwda#com.sap.cms.ui.landconf.LandConfController#Administrator#38347##n/a##3a8a47c08a6f11e2c0b5001a648f9412#SAPEngine_Application_Thread[impl:3]_19ID\#(J2EE306565100)ID0833399350DB58f018f154848257b22f8732705a50ab4bda9dc0End.29ffa6118a6b11e29843001a648f9412##0#0#Error#1#com.sap.cms.ui.landconf.LandConfController#Plain###CMSUnexpectedExcepiton null#

The Default.Trc file doesn't get update when I generate the error, so wondering if there are anymore log files with more info.

Many thanks,

Sean Collins

Hi Guys,

I am trying to patch a SAP NW CE 7.2 system from SP1 to SP8.I had issues for 2 software components while trying to patch using the standard patching tool JSPM.

So I thought of patching just those 2 components using another tool - SUM- Software Update Manager.

In this tool it gives me an error - Cannot detect NWDI system role. Could not get NWDI system role from CVERS. com.sap.sl.util.cvers.api.CVersAccessException: CMSRTS, getModifiedComponents: unknown DB schema, can not write data com.sap.sl.util.cvers.api.CVersAccessException: CMSRTS, getModifiedComponents: unknown DB schema, can not write data

On the JSPM screen it says "System is not under NWDI control" which is correct.The guy who had installed this system has also included the usage type DI which was not needed in the first place.No initial configuration  NWDI  have been ever performed on this system and still while JSPM is not complaining on the NWDI role,SUM is complaining. Do I have to do some initial setup wrt NWDI component so that SUM will pick the right NWDI role.

Hi,

I'am new to NWDI.

I want to create a track,let me know where i can do that.

I checked few posts,where i can see that it can be done in CMS Landscape Configurator, where i can see this

Regards,

Pradeep

Hi all,

We have setup a JDI server wherein we have created track for ESS using the JDI Cookbook. Everything was working fine & we were able to modify the code and check in our activities.But lately all of our activities have started failing. Whenever we do any modification, build the DC, & try to activate the activity, a request id is generated but after some we get a error log & the activation fails.

Can anyone help me on this. Why are the activities failing.It was working fine earlier but almost 5-8 activations on diff DC's has failed with the same error messages although they are building fine in Developer Studio.

Following is the error log:

Request Log - [ 1701/RIQ_ESSTrack_D ]

SAP Component Build Server 

Build number assigned: 1718

Change request state from QUEUED to PROCESSING

ACTIVATION request in Build Space "RIQ_ESSTrack_D" at Node ID: 2,141,150

               [id: 1,701; parentID: 0; type: 4]

               [options: FORCE ACTIVATE PREDECESSORS, IGNORE COMPONENT INTERSECTION]

REQUEST PROCESSING started at 2005-12-11 22:58:11.725 GMT

===== Pre-Processing =====

List of activities to be activated:

               1 activity in compartment "sap.com_SAP_ESS_1"

                               CCT31660_ess_tra_tre_ NN_1

                                              [seq. no 12][created by ADMINISTRATOR at 2005-12-11 12:01:31.0][ID df1a1ea9554b11da88c600508bdfdc5e]

Analyse dependencies to predecessor activities... started at 2005-12-11 22:58:12.959 GMT

Analysing compartment "sap.com_SAP_ESS_1"

               No dependencies to predecessor activities found.

Analyse dependencies to predecessor activities... finished at 2005-12-11 22:58:12.975 GMT and took 16 ms

Analyse activities... started at 2005-12-11 22:58:12.975 GMT

               Synchronizing component "sap.com/ess/tra/tre" from repository... finished at 2005-12-11 22:59:11.178 GMT and took 54 s 406 ms

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

Analyse activities... finished at 2005-12-11 22:59:11.381 GMT and took 58 s 406 ms

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

               "sap.com/ess/tra/tre" variant "default"

Prepare build environment in the file system... started at 2005-12-11 22:59:12.053 GMT

               Synchronize development configuration... finished at 2005-12-11 22:59:12.085 GMT and took 16 ms

               Synchronize component definitions... finished at 2005-12-11 22:59:12.178 GMT and took 93 ms

               Synchronize sources...

               Synchronize sources... finished at 2005-12-11 23:02:15.992 GMT and took 3 m 3 s 814 ms

               Synchronize used libraries...

                               "sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/tc/col/api" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

                                              [DC 164 variant "default"][SC 170] using [DC 31 variant "default"][SC 171][is OK]

                               "sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/tc/cmi" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

                                              [DC 164 variant "default"][SC 170] using [DC 30 variant "default"][SC 171][is OK]

                               "sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/tc/ddic/ddicruntime" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

                                              [DC 164 variant "default"][SC 170] using [DC 34 variant "default"][SC 171][is OK]

                               "sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/tc/ddic/metamodel/content" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

                                              [DC 164 variant "default"][SC 170] using [DC 35 variant "default"][SC 171][is OK]

                               "sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/tc/wd/webdynpro" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

                                              [DC 164 variant "default"][SC 170] using [DC 148 variant "default"][SC 167][is OK]

                               "sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/tc/logging" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

                                              [DC 164 variant "default"][SC 170] using [DC 142 variant "default"][SC 167][is OK]

                               "sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/tc/wdp/metamodel/content" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

                                              [DC 164 variant "default"][SC 170] using [DC 38 variant "default"][SC 171][is OK]

                               "sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/com.sap.aii.proxy.framework" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

                                              [DC 164 variant "default"][SC 170] using [DC 1 variant "default"][SC 171][is OK]

                               "sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/com.sap.aii.util.misc" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

                                              [DC 164 variant "default"][SC 170] using [DC 2 variant "default"][SC 171][is OK]

                               "sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/com.sap.exception" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

                                              [DC 164 variant "default"][SC 170] using [DC 92 variant "default"][SC 167][is OK]

                               "sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/com.sap.mw.jco" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

                                              [DC 164 variant "default"][SC 170] using [DC 95 variant "default"][SC 167][is OK]

                               "sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/pcui_gp/xssfpm" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

                                              [DC 164 variant "default"][SC 170] using [DC 158 variant "default"][SC 168][is OK]

                               "sap.com/ess/tra/tre" in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/pcui_gp/xssutils" has NO VALID Component Description Archive (DCDA). The component seems to have never been built successfully.

                                              [DC 164 variant "default"][SC 170] using [DC 159 variant "default"][SC 168][is OK]

                               "sap.com/ess/tra/tre"  in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/tc/col/api" has NO PUBLIC PART with name "default". Such a public part has not yet been defined or activated.

                                              [DC 164 variant "default"][SC 170] using [PP "default" of DC 31 variant "default"][SC 171][last successfull build: 1530]

                               "sap.com/ess/tra/tre"  in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/tc/cmi" has NO PUBLIC PART with name "default". Such a public part has not yet been defined or activated.

                                              [DC 164 variant "default"][SC 170] using [PP "default" of DC 30 variant "default"][SC 171][last successfull build: 1530]

                               "sap.com/ess/tra/tre"  in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/tc/ddic/ddicruntime" has NO PUBLIC PART with name "default". Such a public part has not yet been defined or activated.

                                              [DC 164 variant "default"][SC 170] using [PP "default" of DC 34 variant "default"][SC 171][last successfull build: 1530]

                               "sap.com/ess/tra/tre"  in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/tc/ddic/metamodel/content" has NO PUBLIC PART with name "default". Such a public part has not yet been defined or activated.

                                              [DC 164 variant "default"][SC 170] using [PP "default" of DC 35 variant "default"][SC 171][last successfull build: 1530]

                               "sap.com/ess/tra/tre"  in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/tc/wd/webdynpro" has NO PUBLIC PART with name "default". Such a public part has not yet been defined or activated.

                                              [DC 164 variant "default"][SC 170] using [PP "default" of DC 148 variant "default"][SC 167][last successfull build: 1533]

                               "sap.com/ess/tra/tre"  in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/tc/logging" has NO PUBLIC PART with name "default". Such a public part has not yet been defined or activated.

                                              [DC 164 variant "default"][SC 170] using [PP "default" of DC 142 variant "default"][SC 167][last successfull build: 1533]

                               "sap.com/ess/tra/tre"  in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/tc/wdp/metamodel/content" has NO PUBLIC PART with name "default". Such a public part has not yet been defined or activated.

                                              [DC 164 variant "default"][SC 170] using [PP "default" of DC 38 variant "default"][SC 171][last successfull build: 1530]

                               "sap.com/ess/tra/tre"  in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/com.sap.aii.proxy.framework" has NO PUBLIC PART with name "default". Such a public part has not yet been defined or activated.

                                              [DC 164 variant "default"][SC 170] using [PP "default" of DC 1 variant "default"][SC 171][last successfull build: 1530]

                               "sap.com/ess/tra/tre"  in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/com.sap.aii.util.misc" has NO PUBLIC PART with name "default". Such a public part has not yet been defined or activated.

                                              [DC 164 variant "default"][SC 170] using [PP "default" of DC 2 variant "default"][SC 171][last successfull build: 1530]

                               "sap.com/ess/tra/tre"  in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/com.sap.exception" has NO PUBLIC PART with name "default". Such a public part has not yet been defined or activated.

                                              [DC 164 variant "default"][SC 170] using [PP "default" of DC 92 variant "default"][SC 167][last successfull build: 1533]

                               "sap.com/ess/tra/tre"  in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/com.sap.mw.jco" has NO PUBLIC PART with name "default". Such a public part has not yet been defined or activated.

                                              [DC 164 variant "default"][SC 170] using [PP "default" of DC 95 variant "default"][SC 167][last successfull build: 1533]

                               "sap.com/ess/tra/tre"  in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/pcui_gp/xssfpm" has NO PUBLIC PART with name "FloorplanManager". Such a public part has not yet been defined or activated.

                                              [DC 164 variant "default"][SC 170] using [PP "FloorplanManager" of DC 158 variant "default"][SC 168][last successfull build: 1529]

                               public part "FloorplanManager" of component "sap.com/pcui_gp/xssfpm" ... OK

                                              [PP "FloorplanManager" of DC 158 variant "default"][SC 168][last successfull build: 1529]

                               public part "FloorplanManager" of component "sap.com/pcui_gp/xssfpm" ... OK

                                              [PP "FloorplanManager" of DC 158 variant "default"][SC 168][last successfull build: 1529]

                               public part "FloorplanManager" of component "sap.com/pcui_gp/xssfpm" ... OK

                                              [PP "FloorplanManager" of DC 158 variant "default"][SC 168][last successfull build: 1529]

                               "sap.com/ess/tra/tre"  in compartment "sap.com_SAP_ESS_1" cannot be built. Activation will fail.

                                              Used component "sap.com/pcui_gp/xssutils" has NO PUBLIC PART with name "FPMUtils". Such a public part has not yet been defined or activated.

                                              [DC 164 variant "default"][SC 170] using [PP "FPMUtils" of DC 159 variant "default"][SC 168][last successfull build: 1529]

                               public part "FPMUtils" of component "sap.com/pcui_gp/xssutils" ... OK

                                              [PP "FPMUtils" of DC 159 variant "default"][SC 168][last successfull build: 1529]

                               public part "FPMUtils" of component "sap.com/pcui_gp/xssutils" ... OK

                                              [PP "FPMUtils" of DC 159 variant "default"][SC 168][last successfull build: 1529]

                               public part "FPMUtils" of component "sap.com/pcui_gp/xssutils" ... OK

                                              [PP "FPMUtils" of DC 159 variant "default"][SC 168][last successfull build: 1529]

                               public part "Common" of component "sap.com/ess/tra" ... OK

                                              [PP "Common" of DC 165 variant "default"][SC 170][last successfull build: 1534]

                               public part "Common" of component "sap.com/ess/tra" ... OK

                                              [PP "Common" of DC 165 variant "default"][SC 170][last successfull build: 1534]

                               public part "Common" of component "sap.com/ess/tra" ... OK

                                              [PP "Common" of DC 165 variant "default"][SC 170][last successfull build: 1534]

                               public part "Common" of component "sap.com/ess/tra" ... OK

                                              [PP "Common" of DC 165 variant "default"][SC 170][last successfull build: 1534]

                               public part "Utils" of component "sap.com/ess/tra" ... OK

                                              [PP "Utils" of DC 165 variant "default"][SC 170][last successfull build: 1534]

                               public part "Utils" of component "sap.com/ess/tra" ... OK

                                              [PP "Utils" of DC 165 variant "default"][SC 170][last successfull build: 1534]

                               public part "Utils" of component "sap.com/ess/tra" ... OK

                                              [PP "Utils" of DC 165 variant "default"][SC 170][last successfull build: 1534]

                               public part "UI" of component "sap.com/ess/tra" ... OK

                                              [PP "UI" of DC 165 variant "default"][SC 170][last successfull build: 1534]

                               public part "UI" of component "sap.com/ess/tra" ... OK

                                              [PP "UI" of DC 165 variant "default"][SC 170][last successfull build: 1534]

                               public part "UI" of component "sap.com/ess/tra" ... OK

                                              [PP "UI" of DC 165 variant "default"][SC 170][last successfull build: 1534]

               Synchronize used libraries... finished at 2005-12-11 23:02:17.367 GMT and took 1 s 375 ms

Prepare build environment in the file system... finished at 2005-12-11 23:02:17.383 GMT and took 3 m 5 s 330 ms

===== Pre-Processing =====  finished at 2005-12-11 23:02:17.383 GMT and took 4 m 5 s 611 ms

Change request state from PROCESSING to FAILED

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

ERROR! The following error occurred  during request processing:Activation failed due to component "sap.com/ess/tra/tre" variant "default". The component is BROKEN.

REQUEST PROCESSING finished at 2005-12-11 23:02:17.383 GMT and took 4 m 5 s 658 ms