Issue in NWDS 7.0.18
Hello,
I am working on NWDS 7.0.18 Tool.
Unfotunately, my System got hanged. And after that, the Tool is not getting maximised. It is showing the icon of NWDS in the Task bar below side of the window. But when I try to click on it, its not maximizing the window.
When I try to right click on the icon, its showing only the option of close window.
I tried to open it through the Task Manager. Its showing the task as Running in the Task manager. When I right clicked on it, and selected bring to front option. It gave no response.
In Task Manager itself, When I right clicked on it, and selected the End Task option, two pop-up windows got opened. And one is for Exit Confirmation and other is the Error Window. Giving the below mentioned error.
'The System cannot end this program, because it is waiting for a response from you. To return to Windows and check the status of the Program, click cancel. If you choose to close program immidiately, you will lose any unsaved data. To end the Program now, click end now.'
Kindly help me out to resolve the issue. As, I am having 10 open Activities which contains huge amount of code. And I cant afford to loose those it.
Thanking you!
Tried it already. Still getting the issue.
Similar Messages
-
RAWSTRING issue in NWDS 7.3 - B cannot be resolved to a type
Dear Experts,
I'm facing an issue while importing a structure in RFC which has RAWSTRING in NWDS 7.3 SP09. This worked well in NWDS 7.0 but having issues in NWDS 7.3
In the inbuilt Java files I'm having error in the method ( B cannot be resolved to a type )
public [B getBinary1() {
return ([B)super.getAttributeValue("Binary1");
Appreciate your suggestions if you faced similar issues.
Thankshi mohamed ,
as already specified in the thread ,http://scn.sap.com/thread/3286933 you can use the deprecated rfc , as even we were not able to solve that issue even though we deleted and reimported several times , you can use deprecated rfc . we tried changing the type of the attribute from xtring to other compatible types at abap side but it didnt work , so we used deprecated rfc.
Regards
Govardan -
Hi
We have upgraded from CE 7.2 to Netweaver 7.3.
When I installed NWDS 7.3 and tried to import the SC I am facing an issue. it throws an error "Some infrastructure servers cannot be contacted". It is the build server that is not getting connected.
I am able to ping sld also the build server path can be opened via browser.The same is also connected when I try using NWDS 7.2.
I have tried changing the network setting in the preferences without much help.
Can you please let me know what is missing?
Regards
KGMHi
Thanks for the reply.
I am using direct connect to the internet option in both 7.2 and 7.3 .
Is there any thing in particular to be done?
Issue resolved after adding the hostname.
Edited by: KGMuku on Feb 16, 2012 7:40 AM -
Deployment issue in NWDS while deploying BPM
Hi Experts,
I m getting following deployment error in NWDS (SAP Enhancement Package 1 for SAP NetWeaver Developer Studio 7.3 SP11 PAT0002) while deploying BPM.
can u plz revert back if you have encountered similar issue.
com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
Reason: ASJ.dpl_dc.001085 Operation [deploy] of [DC-I205] failed
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:862)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:105)
at com.sap.ide.tools.services.dc.EngineDcDeployService.deployFiles(EngineDcDeployService.java:257)
at com.sap.ide.tools.services.dc.EngineDcDeployService.deploy(EngineDcDeployService.java:135)
at com.sap.ide.dii05.ui.internal.actions.dc.DcDeployAction$5$1.run(DcDeployAction.java:282)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 Operation [deploy] of [DC-I205] failed
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:246)
at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:67)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100)
at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
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)
Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] Operation [deploy] of [DC-I205] failed
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:167)
at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:138)
at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213)
... 8 more
Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: ASJ.dpl_ds.006193 Operation [deploy] of [/usr/sap/A6D/J00/j2ee/cluster/server0/temp/tc~bl~deploy_controller/archives/1418/DC-I205.sda] failed
at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:3370)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:315)
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:139)
... 11 more
Caused by: com.sap.engine.services.deploy.container.DeploymentException: TxException
at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1280)
at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deploy(ContentArchiveDeployContainer.java:137)
at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:310)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:519)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:183)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:203)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:421)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:473)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1836)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:360)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:313)
... 12 more
Caused by: java.lang.Exception: com.sap.engine.services.ts.transaction.TxRollbackException: Current transaction is marked for rollback
at com.sap.engine.services.ts.transaction.TxManagerImpl.commitLevel(TxManagerImpl.java:621)
at com.sap.transaction.TxManager.commitLevel(TxManager.java:237)
at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1277)
at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deploy(ContentArchiveDeployContainer.java:137)
at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:310)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:519)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:183)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:203)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:421)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:473)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1836)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:360)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:313)
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:139)
at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:138)
at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213)
at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:67)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100)
at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
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)
Caused by: java.lang.IllegalStateException: Galaxy commit failed (for a possible cause, refer to the nested exception(s)
at com.sap.glx.core.kernel.execution.TransitionManagerImpl$BoundPrimaryTransaction.beforeCompletion(TransitionManagerImpl.java:117)
at com.sap.engine.services.ts.jta.impl.SynchronizationWrapper.beforeCompletion(SynchronizationWrapper.java:36)
at com.sap.engine.services.ts.jta.impl2.TXR_TransactionImpl.beforePrepare(TXR_TransactionImpl.java:589)
at com.sap.engine.services.ts.jta.impl2.TXR_TransactionImpl.commit(TXR_TransactionImpl.java:1120)
at com.sap.engine.services.ts.jta.impl2.TXR_TransactionManagerImpl.commit(TXR_TransactionManagerImpl.java:333)
at com.sap.engine.services.ts.transaction.TxManagerImpl.commitLevel(TxManagerImpl.java:610)
... 24 more
Caused by: com.sap.glx.core.kernel.api.TransitionRollbackException: Transaction locked for rollback; Commit refused.
at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.rollback(AbstractTransactionBase.java:701)
at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_precommit(AbstractTransaction.java:186)
at com.sap.glx.core.kernel.mmtx.AbstractTransaction.commit(AbstractTransaction.java:75)
at com.sap.glx.core.kernel.execution.TransitionManagerImpl$BoundPrimaryTransaction.beforeCompletion(TransitionManagerImpl.java:115)
... 29 more
Caused by: com.sap.glx.core.dock.api.DockException: Adapter com.sap.glx.adapter.internal.Transformer didn't comply with configuration
at com.sap.glx.core.dock.impl.DockingPortal.configure(DockingPortal.java:693)
at com.sap.glx.core.dock.impl.DockingPortal.configureCallback(DockingPortal.java:495)
at com.sap.glx.core.dock.impl.DockingPortal.runConfigureCallback(DockingPortal.java:998)
at com.sap.glx.deploy.impl.DeployControllerImpl$DeployProcessor.runProcessorWork(DeployControllerImpl.java:801)
at com.sap.glx.deploy.impl.DeployControllerImpl$Processor.run(DeployControllerImpl.java:624)
at com.sap.glx.deploy.impl.DeployControllerImpl$Processor.access$1300(DeployControllerImpl.java:585)
at com.sap.glx.deploy.impl.DeployControllerImpl$ProcessorList.run(DeployControllerImpl.java:549)
at com.sap.glx.deploy.impl.DeployControllerImpl$ProcessorList.run(DeployControllerImpl.java:543)
at com.sap.glx.core.kernel.DefaultRuntimeManager.requestRuntimeMode(DefaultRuntimeManager.java:1110)
at com.sap.glx.deploy.impl.DeployControllerImpl$InternalActuator.executeDeployWork(DeployControllerImpl.java:1177)
at com.sap.glx.core.resource.impl.j2ee.rrdeploy.CoreServiceRRHandler$DeployActuatorCallback.executeDeployActuatorCallbackWork(CoreServiceRRHandler.java:138)
at com.sap.glx.core.resource.impl.j2ee.rrdeploy.CoreServiceRRHandler$DeployActuatorCallback.access$400(CoreServiceRRHandler.java:50)
at com.sap.glx.core.resource.impl.j2ee.rrdeploy.CoreServiceRRHandler.callCoreServiceHandlers(CoreServiceRRHandler.java:314)
at com.sap.glx.core.resource.impl.j2ee.rrdeploy.CoreServiceRRHandler.addVersion(CoreServiceRRHandler.java:337)
at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.handlerDistributionForDeployment(RuntimeRepositoryDeployManager.java:2565)
at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deployArchive(RuntimeRepositoryDeployManager.java:1535)
at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:339)
at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:261)
at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:251)
at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1265)
... 22 more
Caused by: com.sap.glx.adapter.api.AdapterException: Adapter com.sap.glx.adapter.internal.Transformer has refused deploy unit 7b9afc88c8f151c20d38cef0d370f416 using configuration mode DEPLOYMENT
at com.sap.glx.core.dock.impl.DockingPortal.configure(DockingPortal.java:669)
... 41 more
Caused by: java.lang.RuntimeException: Transformer could not get lock within 60 seconds
at com.sap.glx.core.internaladapter.Transformer$Share.acquireWrite(Transformer.java:875)
at com.sap.glx.core.internaladapter.Transformer$TransformerTemplateAccessor$GeneratorTemplate$GeneratorConfigurationAccessor$GeneratorLocalProvider$ImplementedGeneratorLocal.acquireWrite(Transformer.java:2317)
at com.sap.glx.core.internaladapter.Transformer$TransformerTemplateAccessor$GeneratorTemplate$GeneratorConfigurationAccessor.insertRule(Transformer.java:2775)
at com.sap.glx.core.internaladapter.Transformer$TransformerTemplateAccessor$GeneratorTemplate$GeneratorConfigurationHandler.configure(Transformer.java:2930)
at com.sap.glx.core.internaladapter.Transformer$TransformerTemplateAccessor$GeneratorTemplateHandler.configure(Transformer.java:3472)
at com.sap.glx.core.internaladapter.Transformer.configure(Transformer.java:3675)
at com.sap.glx.core.dock.impl.DockingPortal.configure(DockingPortal.java:666)
... 41 more
at com.sap.engine.services.ts.transaction.TxRollbackException.writeReplace(TxRollbackException.java:163)
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 java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:1040)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1116)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:423)
at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:1033)
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 java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:953)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1482)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:423)
at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:1033)
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 java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:953)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1482)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:331)
at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:139)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:488)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:81)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:72)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:43)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:999)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:59)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
... 3 moreHi,
i have not done any changes to any process. I have created new DC and created new process.
new DC is not getting deployed with error "Adapter com.sap.glx.adapter.internal.Transformer didn't comply with configuration". If you will check error log above then you will find it their. -
Look and Feel Issues from NWDS 7.0.9 on Windows 7
Dear Experts,
I have successfully installed a new NWDS 7.0.9 on my 18' inch laptop:
Windows 7 (64Bit)
JDK 1.4.18 (32Bit)
The NWDS starts without any problems however, i am begining to experience some erratic behavior from the projects i have created.
For instance, when i attempt to Edit the Application Properties for a WDJ project, the neccessary fields (and tabs) are not displayed hence i am unable to edit properties like the 'ExpirationTime' or create new one for that matter.
In some cases,i am unable to embed a View into a Window because the neccessary fields to aid my selection of the view i want to embed are not visible for interaction.
The same challenge occurs with EAR project; i am unable to edit 'application-j2ee-engine.xml' fields because they are not visible.
After some troubleshooting,i discovered that the screen resolution may be affecting the 'Look and Feel' of the NWDS itself,
If i reduced the resolution from 1024*768 to a value much more lower, some of these controls are displayed but with the desktop completely messed up.
Does anybody have a solution to my problem because this challenge is affecting my productivity?
Could my issue be as a result of my laptop screen size (i am using an 18'inch laptop)?
Best regards,
Bakau Onafuwa
Oceanic Bank Int'l PLCHi Vishal,
first go to the download section in SMP.
Roughly follow this path (translated from german ;-):
SAP Software Distribution Center -> Download -> Further Download-Infos -> SAP Support Package Stacks -> SP Stack Download
From list select SP Stack SAP NetWeaver 2004s
A new window will pop up:
1. Select your stack
2. Usage Selection: Application Server Java
3. Next Step
4. Under SAP Kernel xx bit select your DB and OS
5. Next Step
6. You get a list of all components of you selected items.
Here you'll find NWDS with a filename like JIDE09P_1-10003480.SAR
You know the rest, right?
Regards,
ok -
Dear All,
I am using NWDS 7 for web dynpro development.
I created a development component for customer master in web dynpro and it is perfectly integrated with R/3 and saving the data in R/3.
Now I exported this component using File->Export->File System->Development Component ,
Then I created a new development component and imported the same exported DC in this component.
It imported the DC successfully but when I tried to deploy it after rebuild it is showing error--
Jun 28, 2008 1:49:30 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
[006]Additional log information about the deployment
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[D:\usr\sap\DEP\JC02\SDM\program\log\sdmcl20080628081927.log]/>
<!PATTERN[sdmcl20080628081927.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Jun 28, 2008 1:49:27 PM Info: -
Starting deployment -
Jun 28, 2008 1:49:27 PM Info: Error handling strategy: OnErrorStop
Jun 28, 2008 1:49:27 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Jun 28, 2008 1:49:27 PM Info: Update strategy: UpdateAllVersions
Jun 28, 2008 1:49:27 PM Info: Starting deployment prerequisites:
Jun 28, 2008 1:49:28 PM Info: Loading selected archives...
Jun 28, 2008 1:49:28 PM Info: Loading archive 'D:\usr\sap\DEP\JC02\SDM\program\temp\temp6581dep.com~t1.ear'
Jun 28, 2008 1:49:28 PM Info: Selected archives successfully loaded.
Jun 28, 2008 1:49:28 PM Info: Actions per selected component:
Jun 28, 2008 1:49:28 PM Info: Initial deployment: Selected development component 't1'/'dep.com'/'LOKAL'/'0.2008.06.28.13.49.17'/'0' will be deployed.
Jun 28, 2008 1:49:28 PM Info: Ending deployment prerequisites. All items are correct.
Jun 28, 2008 1:49:30 PM Error: Unable to compare host[idedep] and host[WEBSERVER] Throwable: java.net.UnknownHostException Throwable message: WEBSERVER: WEBSERVER
Jun 28, 2008 1:49:30 PM Info: Saved current Engine state.
Jun 28, 2008 1:49:30 PM Info: Starting: Initial deployment: Selected development component 't1'/'dep.com'/'LOKAL'/'0.2008.06.28.13.49.17'/'0' will be deployed.
Jun 28, 2008 1:49:30 PM Info: SDA to be deployed: D:\usr\sap\DEP\JC02\SDM\root\origin\dep.com\t1\LOKAL\0\0.2008.06.28.13.49.17\temp6581dep.com~t1.ear
Jun 28, 2008 1:49:30 PM Info: Software type of SDA: J2EE
Jun 28, 2008 1:49:30 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jun 28, 2008 1:49:30 PM Error: Unable to compare host[idedep] and host[WEBSERVER] Throwable: java.net.UnknownHostException Throwable message: WEBSERVER
Jun 28, 2008 1:49:31 PM Info: Begin of log messages of the target system:
08/06/28 13:49:30 - ***********************************************************
08/06/28 13:49:31 - Start updating EAR file...
08/06/28 13:49:31 - start-up mode is lazy
08/06/28 13:49:31 - EAR file updated successfully for 31ms.
08/06/28 13:49:31 - Start deploying ...
08/06/28 13:49:31 - EAR file uploaded to server for 15ms.
08/06/28 13:49:31 - ERROR: Not deployed. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy application dep.com/t1..
Reason: Clusterwide exception: Failed to deploy application dep.com/t1. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application dep.com/t1. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:569)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
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.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application dep.com/t1. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1050)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3186)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:554)
... 10 more
For detailed information see the log file of the Deploy Service.
08/06/28 13:49:31 - ***********************************************************
Jun 28, 2008 1:49:31 PM Info: End of log messages of the target system.
Jun 28, 2008 1:49:31 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jun 28, 2008 1:49:31 PM Error: Aborted: development component 't1'/'dep.com'/'LOKAL'/'0.2008.06.28.13.49.17'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application dep.com/t1..
Reason: Clusterwide exception: Failed to deploy application dep.com/t1. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application dep.com/t1. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Jun 28, 2008 1:49:31 PM Info: Starting to save the repository
Jun 28, 2008 1:49:32 PM Info: Finished saving the repository
Jun 28, 2008 1:49:32 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Jun 28, 2008 1:49:32 PM Error: -
At least one of the Deployments failed -
what could be the problem... Please suggest..
Thanks in AdvanceHi alternatively try this
1. Create a new Web Dynpro DC Project.
This creates an empty container for a Web Dynpro DC that does not have yet have any functions. The new DC should include all relevant development objects in the local project.
Do not check the newly created DC into the DTR yet.
2. In the Web Dynpro perspective, switch to the Navigator view.
3. Select the local Web Dynpro project that you want to migrate and expand the project structure.
4. Select the source folder src and the Model Folder, then choose Copy in the context menu (right mouse click).
5. Now choose the DC project that you have just created and expand the project structure in the Navigator view down to the source folder.
6. Select the Packages node and choose Paste.
7. Choose OK to confirm your selection.
8. Assign a DTR activity either by creating a new activity or choosing an existing one.
9. Switch to Web Dynpro Explorer.
10. Choose the project node for the DC project and choose the Reload function.
11. A dialog box appears. Choose Reload again.
12. Execute a local rebuild for the entire DC project. Choose the Rebuild project function.
13. If there are no errors in the task view, execute a DC-based build by choosing Development Component Build.
This build is identical to the central build tool; it is needed to cater for mutual dependencies of DCs during the build. -
hai ALL,
I have installed EP and nwds on my PC . when i try to configure the J2EE engine in the 'preferences' window it is not accepting or taking any changes done by me . Please help me with complete docs on NWDS
Thanks,
Raghavendra AchHi Phani
I think first step applies to you
After deleting metadata folder , restart again.
1) If the j2EE installed on your localmachine then
preferences->SAP J2EE Engine ->select the second radiobutton -> select browse and select the instance (after clicking browse , it will show you local j2e instance) select and save.
2) If the J2EE is installed on remote machine
you can get the details from SystemInformation.
Connect to http://<hostName>:<port>
Click on systeminformation link and you can see the messageserverport info .
Type the messageserverport in your j2EE settings preferneces.
Koti Reddy -
Reg. files missing in NWDS
Hi all,
I am having an issue regarding NWDS i.e. when I took backup of the applications for reinstallation of NWDS, .classpath,.metamodel,.project,.tssapinfo etc files are missing from my applications. Now I am unable to open these applications in NWDS ,its giving an error that .project is missing .I reguest kindly to give your valuable suggestions for getting these file back in my applications so that i can proceed further in developing my application.I am inneed of it.
thanking you
AravindHi Aravind
When you create an "empty project you will get those missing files e g .project, .classpath. Then you just import your backuped files that contains your views, component(s), windows etc.
Of course you probably need to modify your buildpath if you have dependencies in your project that is not standard.
Maybe I'm not understanding you correctly?
Regards
Göran
Edited by: Göran Westin on Feb 20, 2008 10:07 AM
Edited by: Göran Westin on Feb 20, 2008 10:17 AM -
NWDS Active/Inactive DC shows offline after loging to NWDI
Hi experts,
I am Facing a weird issue using NWDS.
When I log to NWDI through NWDS, the active/inactive DC perspective still shows as Offline.
I tried closing and reopening NWDS couple of times but still the issue persists.
I faced same issue couple of days back and closing and reopening NWDS resolved the issue.
I am searching for a permanent solution for this problem.
Thanks,
AshutoshHi,
Did you try to reimport the track and see?
We had same issue issue closing and opening NWDS didn't solve then we have removed the Track from Development Configuration Perspective and imported the track again and it helped.
After deleting the Track in NWDS, navigate to Window - Preferences - Expand Java Development Infrastructure - Development Configuration Pool and look for the Location for Development Configuration.
And Delete the .dtc folder from that location and close the NWDS and reopen and import the new track.
This should solve the issue.
Hope this helps.
Cheers-
Pramod -
Hello,
With NWDS CE 7.1 Is it possible to develop mobile Infrastructure application.........
in Windows ->Preferences -> i cannot find MDK/MI Development
should i need to install another version....
Please can anyone help meDear Manish,
Please follow the link Akhil gave for installing the Mobile Plugins. Please note that your CE IDE's version (for example SP 07) should match with your MI / NetWeaver Mobile Plugins for proper functioning. If you have a need to update your NWDS to the latest SP and you are stuck somewhere, please refer the following thread in which I have helped out in solving NWDS CE 7.1 - generic - updating issues.
NWDS CE: SAP Plugins missing
Regards,
Veera -
NWDS 7.3 Slow Navigation
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,
VeyHi Vey,
What sort of DC's are you working with? In the past, I've experienced slows downs like this working with BPM and BRM DC's, where NWDS is continuously building and compiling local content, which in turn slows everything down to the point it is unworkable.
From memory, I'm sure there were some OSS interactions that applied fixes to the underlying NWDI to try to avoid this.
Also, what sort of machine spec' are you running NWDS on, as it is a very resource hungry piece of software!
I've not working with NWDS in anger for a long time now unfortunately, however I'm sure there was a view you could open that showed all of the current processes running within NWDS, like the task manager for Windows. It may be useful to see what is running on your installation to see if that helps track down the issue. I think "Progress View" or similar might be the one I'm thinking about.
For sure though, you aren't the only one who has suffered with NWDS performance!
Cheers,
G. -
"LayoutTagLibrary" tag error in JSP file .
Dear All,
I am trying to implement Custom Framework Page in SAP NW Portal 7.3 with the help of the [DOCUMENT|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/001bfa1a-958e-2e10-c2be-d914f673e21e?QuickLink=index&overridelayout=true]
I am getting an error in the FrameworkPageLayout.jsp file, Can not find the tag library descriptor for "LayoutTagLibrary
I added the SharingReference - com.sap.portal.pagebuilder Under Application tag
and LayoutTagLibrary - /SERVICE/com.sap.portal.pagebuilder/taglib/layout.tld Under Component Profile tag.
But still, I am getting this error. How to resolve this?
Regards
Eben Joyson.Hi Detlev,
I modified my jsp page. but still I get the same error. Can not find the tag library descriptor for "prt:taglib:LayoutTagLibrary"
Should I need to add any jar file under the lib folder of the project? Help me to solve this issue. Only in NWDS 7.3 i am facing this issue. with NWDS 7.0, its working.
My JSP Code :
<%@ taglib uri="prt:taglib:LayoutTagLibrary" prefix="lyt"%>
<lyt:template eliminatemessagebar="true">
<lyt:container id="container" wrappingMethod="none">
</lyt:container>
</lyt:template>
My Portalapp.xml
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<application alias="affs">
<application-config>
<property name="Vendor" value="sap.com"/>
<property name="SecurityArea" value="NetWeaver.Portal"/>
<property name="SharingReference" value="SAPJ2EE::library:com.sap.portal.themes.lafservice, com.sapportals.htmlb, com.sap.portal.navigation.api_service, com.sap.portal.pagebuilder, com.sap.portal.useragent, com.sap.portal.navigation.helperservice, com.sap.portal.navigation.afp.helperservice"/>
</application-config>
<components>
<component name="layout">
<component-config>
<property name="ClassName" value="com.sapportals.portal.pb.layout.PageLayout"/>
<property name="ResourceBundleName" value="pagebuilder_nls"/>
<property name="SafetyLevel" value="no_safety"/>
</component-config>
<component-profile>
<property name="ComponentType" value="com.sapportals.portal.layout"/>
<property name="com.sap.portal.pcm.Category" value="platform">
<property name="inheritance" value="final"/>
</property>
<property name="LayoutTagLibrary" value="/SERVICE/com.sap.portal.pagebuilder/taglib/layout.tld"/>
<property name="com.sap.portal.reserved.layout.TemplateFile" value="FrameworkPageLayout.jsp"/>
<property name="com.sap.portal.reserved.layout.Cont1" value="container">
<property name="title" value="Content"/>
<property name="orientation" value="vertical"/>
</property>
<property name="com.sap.portal.page.builder.optimization.level" value="2"/>
<property name="AuthScheme" value="anonymous"/>
<property name="Title" value="AFP Layout"/>
<property name="EPCFLevel" value="1"/>
<property name="SupportedUserAgents" value="(*,*,*)">
<property name="validvalues" value="7/(*,*,*)"/>
</property>
</component-profile>
</component>
<component name="iview">
<component-config>
<property name="ClassName" value="com.customer.afp.fromscratch.FrameworkPageComponent"/>
<property name="SafetyLevel" value="no_safety"/>
</component-config>
<component-profile>
<property name="com.sap.portal.iview.ShowTray" value="false"/>
<property name="AuthScheme" value="anonymous"/>
<property name="EPCFLevel" value="1"/>
<property name="SupportedUserAgents" value="(*,*,*)">
<property name="validvalues" value="7/(*,*,*)"/>
</property>
</component-profile>
</component>
</components>
<services/>
</application> -
EJB Project couldnu00B4t be created
Hello,
I updated my NW Developer Studio to 2.0.15, Build id: 200511290548. Now the problem occurs that I cannot create a new EJB Project. Following error is shown up: New project couln´t be created.
In the log the error starts with following message:
!ENTRY com.sap.ide.metamodel.core 1 1 Jul 31, 2006 14:38:19.281
!MESSAGE Updating metamodel archives from classpath for project MailAdapterModule
!ENTRY com.tssap.util 4 0 Jul 31, 2006 14:38:20.804
!MESSAGE Jul 31, 2006 2:38:20 PM com.tssap.j2ee.ui.creation.internal.AbstractJ2eeProjectCr... [Thread[main,5,main]] Error: method: createNewProject -> problems with runnable for j2ee-project
!STACK 0
java.lang.reflect.InvocationTargetException
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:313)
Any ideas?
Regards
MichaelHi Michael,
I have heard of (and experienced) a number of different issues with NWDS SP15. Rather than trying to fight it, you could try installing SP16 or SP17 and see if that solves the problem.
Regards,
Thorsten -
Netweaver Developer Studio 7.0 performance problem
Hi everyone:
I have a situation in which I am unable to perform any operations upon opening a particular Edit Model Binding window. The number of nodes (25) & attributes (on average, 25 per node, several up to 100 per node) to be managed is so huge, that for any context mappings between the applicable model context and any of its 4 dependent contexts, NWDS 7.0 suffers from a 30-60 second delay when I try any kind of scrolling, opening and collapsing of nodes (sometimes even longer), even bringing up the window itself. The javaw.exe memory footprint from NWDS 7.0 becomes unmanageably large (500+ MB), paralyzing my whole computer even with 2GB RAM. From your own experiences, how did you manage doing any kind of Java Webdynpro context binding for such heavily populated Model contexts?
Any tips for resolving this issue in NWDS 7.0? Would upgrading to NWDS 7.1 help? Anybody conduct an informal performance comparison, memory requirements, and other benchmarks between the two IDEs? How would I maintain any outstanding activity requests from NWDS 7.0 I have not checked-in yet?
Please advise,
JonHello Jon,
I agree, but 2 GB RAM is sufficient to run the NWDS efficiently, consider the following points to increase its performance.
1. Tweak your eclipse.ini : This will increase the memory usage of Eclipse, but will give you the best startup and working performance. If you think eclipse is using up too much memory, lower the Xms, Xmx and PermSize values.
-startupplugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar--launcher.XXMaxPermSize256m-vmargs -Xms256m -Xmx512m -XX:PermSize=256m -XX:MaxPermSize=256m -XX:+AggressiveOpts-XX:+StringCache-XX:+UseFastAccessorMethods-XX:+UseLargePages-XX:LargePageSizeInBytes=4m-XX:AllocatePrefetchLines=1-XX:AllocatePrefetchStyle=1-Dide.gc=true
2. Disable the un-necessary startup plugins
It loads up certain (un-necessary) plugins at startup. We can tweak this a bit to improve the startup performance.
Go to Window > Preferences
Expand General and select Startup and Shutdown
On the right side, uncheck the plugins you don't want to start. Usually, you can uncheck all of them. Don't worry, it just makes the startup minimal. Once you need to access the module in the IDE, it will start it up.
Click OK and restart IDE.
BR
Satish Kumar -
Invalid Class -Java Bean not available for import
hai friends,
i have declared the bean but unable to import into webdynpro application
i am geting the error invalid Class-java bean Not available for improt
i am try for this since more than 10 days , i get the same error
even i thought there may be issues with nwds , i have installed thrice.
there is application download from the sdn tu_bonus calculation it is working
plz help me neede very urgentlyHi,
Go thro' these solved threads dealing with similar type of problem,
Import JavaBean Error : Invalid Class
invalid class - ..as Model Class already exist
Hope it helps to fix the error !
Regards
Srinivasan T
Maybe you are looking for
-
Plan cost line items for cost centers report
Hello, I am displaying the report: Plan cost line items for cost centers and when I display the details of a line item it appears a document number, where could I display this document? I have tried to display it in FB03 transaction but it seems not
-
IPhone 4 could not capture remote Wi-Fi but can capture the network from close range to Ataatjos meter
-
How can I find a device by its name on iCloud?
I need some help! I'm trying to find my wife's iPad using iCloud. Neither of our accounts are signed in to it right now, so how can I search for it by device name?
-
Problem with Process 2012 in Bridge CS5
I can't use Process 2012 in CS5 Bridge. It always makes me go back to 2010. I think I have the latest ACR, and use this in LR4. Anyone else experience this? Thanks, Dave
-
Analytic Workspace Manager Release date
Does anyone know that release date for the analytic workspace manager?