Deployment finished with warning when I deploy projects!

Dear All,
I got the error message when I deploy 2 related projects to J2EE, what is the reason? Thanks.
2011-5-27 15:37:57 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] WARNING:
[003]Deployment finished with warning
Settings
SDM host : IBM205928
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/ADMINI1/LOCALS1/Temp/temp3258717415907093402cateomp~asc.ear
Result
=> deployment not executed : file:/C:/DOCUME1/ADMINI1/LOCALS1/Temp/temp3258717415907093402cateomp~asc.ear
Unresolved dependencies found for the following SDAs:
1.: development component 'eomp/asc'/'cat'/'CNP_CRMASCTR_D'/'20110527151357'/'0'
dependency:
name: 'eomp/survyapp'
vendor: 'cat'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
Deployment will be aborted.
Deployment exception : Got problems during deployment

Hello
I tried to deploy all components that I can find, but it is still wrong.
Do you know how to check these components which need be deployed? Thanks ...

Similar Messages

Check DB finished with warning

Dear all,
Check DB finished with warning from DB13,
kindly check the detail log .
BR0969I Checking database administration...
BR0970W Database administration alert - level: WARNING, type: CRITICAL_TABLESPACE, object: PSAPSR3, value: (max_extn of 5 files on disk 3342337) 34959360 KB (> 28188060 KB)
BR0970W Database administration alert - level: WARNING, type: CRITICAL_TABLESPACE, object: PSAPSR3, value: (max_extn of 5 files on disk 3342338) 32747520 KB (> 26471824 KB)
BR0970W Database administration alert - level: WARNING, type: CRITICAL_TABLESPACE, object: PSAPSR3, value: (max_extn of 5 files on disk 3342339) 33157120 KB (> 17786284 KB)
BR0970W Database administration alert - level: WARNING, type: CRITICAL_TABLESPACE, object: PSAPSR3, value: (max_extn of 5 files on disk 3342340) 34304000 KB (> 24094204 KB)
BR0970W Database administration alert - level: WARNING, type: CRITICAL_TABLESPACE, object: PSAPSR3700, value: (max_extn of 4 files on disk 3342339) 24125440 KB (> 17786284 KB)
BR0970W Database administration alert - level: WARNING, type: CRITICAL_TABLESPACE, object: PSAPSR3700, value: (max_extn of 5 files on disk 3342340) 29286400 KB (> 24094204 KB)
BR0970W Database administration alert - level: ERROR, type: MISSING_INDEX, object: (table) SAPSR3.ZBIMIS
BR0970W Database administration alert - level: ERROR, type: MISSING_STATISTICS, object: (table) SAPSR3.ZHDFCLOG
BR0970W Database administration alert - level: ERROR, type: MISSING_STATISTICS, object: (table) SAPSR3.ZHDFCLOG1
BR0970W Database administration alert - level: ERROR, type: MISSING_STATISTICS, object: (table) SAPSR3.ZHDFCMAP
BR0970W Database administration alert - level: ERROR, type: MISSING_STATISTICS, object: (index) SAPSR3.ZHDFCLOG~0
BR0970W Database administration alert - level: ERROR, type: MISSING_STATISTICS, object: (index) SAPSR3.ZHDFCLOG1~0
BR0970W Database administration alert - level: ERROR, type: MISSING_STATISTICS, object: (index) SAPSR3.ZHDFCMAP~0
BR0280I BRCONNECT time stamp: 2010-03-12 01.04.29
BR0972I Checking database operations...
BR0280I BRCONNECT time stamp: 2010-03-12 01.04.29
BR0974I Checking database messages in /oracle/IRP/saptrace/background/alert_IRP.log ...
BR0280I BRCONNECT time stamp: 2010-03-12 01.04.31
BR0977I Checking database profile...
BR0978W Database profile alert - level: WARNING, parameter: LOG_BUFFER, value: 14251008 (>< 4096,512 KB)
BR0978W Database profile alert - level: WARNING, parameter: OPTIMIZER_FEATURES_ENABLE, value: 10.2.0.1 (set in parameter file)
BR0978W Database profile alert - level: WARNING, parameter: PARALLEL_EXECUTION_MESSAGE_SIZE, value: 2152 (>< 16384,4096)
BR0978W Database profile alert - level: ERROR, parameter: QUERY_REWRITE_ENABLED, value: TRUE (<> FALSE)
BR0978W Database profile alert - level: ERROR, parameter: REPLICATION_DEPENDENCY_TRACKING, value: TRUE (<> FALSE)
BR0978W Database profile alert - level: WARNING, parameter: STAR_TRANSFORMATION_ENABLED, value: FALSE (<> TRUE)
BR0978W Database profile alert - level: WARNING, parameter: STATISTICS_LEVEL, value: TYPICAL (set in parameter file)
BR0280I BRCONNECT time stamp: 2010-03-12 01.04.31
BR0980I Number of changed database profile parameters: 0
BR0280I BRCONNECT time stamp: 2010-03-12 01.04.32
Kindly suggest
Regards

HI
Go to DB20 , Enter the table name ( which are coming in warning) , Press "Refresh" button . You will see
"Old number" and "New Number" are different for those table. Simply click on "Create Statistics" button.
Once you create stats for all the tables shown in warning, run your DB Check job once again.
You have lots of other warning...do some google...you will get most of the information for those warning. Some good links are below
http://download.oracle.com/docs/cd/B12037_01/server.101/b10755/initparams143.htm
http://skywheel.sarang.net/docs/Oracle/10g/server.101/b10755/initparams168.htm
http://youngcow.net/doc/oracle10g/server.102/b14237/initparams209.htm
Regards
Anindya
Edited by: Anindya Bose on Mar 12, 2010 12:35 PM

Exporting application finished with error (when deploying)

When deploying HFM application from EPMA, I get this error from job "Exporting Application ...":
Process Name : dimension_server
Thread : 10
Server : HYPSRV
Detail : An error was encountered while executing the Application Export: Object reference not set to an instance of an object.
In Event Viewer, there are two errors from HyS9BPMA_DimensionServer:
1. [ApplicationExportJob] ERROR Object reference not set to an instance of an object.Exception: System.NullReferenceException
Message: Object reference not set to an instance of an object.
Source: dimension_server
2. There are no results available for job Exporting application htcapp. because an error was encountered while processing the job. See the Job Console or the Event Viewer for more information.Exception:
Because of that, deployment still finish with status "Aborted".
Does anybody know, why is that?
Thanks,
Vlado

See BPMA log for more details.

Oracle Apps.XML reports ending with warning when the report output contains

Hi I have XML reports. When we run these reports as concurrent program through Oracle Apps. window and if the report output contains special characters(like Chineese data) in between of English, then the concurrent program is ending with warning. If we remove special characters then it is working fine or when we run the report query directly from backend it is working fine.
We are importing this data from legacy system into oracle apps. and we can't control these characters or decode them with some other charactes.
Can any one guide me how to get the XML report output with special characters.
Thanks in advance.
Chandra Babu Lankipalli.

Hi Hussein,
The concurrent program is ending with Warning. It is unable to publish output file.
For the same when we remove special characters and run the program it is completing and generating the
output. The log fine is as follows when the data file contains special characters.
Custom Application: Version : UNKNOWN
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
XXFA_AR_WIN_EXCEPTION module: XXFA AR Wintrack Customer Interface Exception Report
Current system time is 23-MAR-2009 05:33:19
+-----------------------------
| Starting concurrent program execution...
+-----------------------------
Arguments
P_CUST_ERRORED='3'
P_CUST_SUCCESS='0'
P_CUST_TOTAL='3'
P_REQUEST_ID='4661283'
P_USER_NAME='SYSADMIN'
APPLLCSP Environment Variable set to :
XML_REPORTS_XENVIRONMENT is :
/d01/oracle/fadevora/8.0.6/guicommon6/tk60/admin/Tk2Motif_UTF8.rgb
XENVIRONMENT is set to /d01/oracle/fadevora/8.0.6/guicommon6/tk60/admin/Tk2Motif_UTF8.rgb
Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
American_America.UTF8
Report Builder: Release 6.0.8.25.0 - Production on Mon Mar 23 05:33:19 2009
(c) Copyright 1999 Oracle Corporation. All rights reserved.
Enter Username:
Start of log messages from FND_FILE
End of log messages from FND_FILE
Executing request completion options...
------------- 1) PUBLISH -------------
Beginning post-processing of request 4661284 on node FAHQSNA01SFTD03 at 23-MAR-2009 05:33:20.
Post-processing of request 4661284 failed at 23-MAR-2009 05:33:21 with the error message:
One or more post-processing actions failed. Consult the OPP service log for details.
------------- 2) PRINT -------------
Not printing the output of this request because post-processing failed.
Finished executing request completion options.
Concurrent request completed
Current system time is 23-MAR-2009 05:33:21
Thanks in advance.
Chandra

SAP database check finished with warning

Hello All,
In sapcheck folder latest .chk file finished with following warnings
BR0280I BRCONNECT time stamp: 2009-04-01 10.30.50
BR0972I Checking database operations...
BR0973W Database operation alert - level: WARNING, operation: cdzsjafp.log, time: 2009-01-17 05.13.45, condition: Last 'log' operation failed with rc = 3
Kindly help me resolve the issue.
Regards
Mohsin

>
mohsin m wrote:
> Hello All,
>
> In sapcheck folder latest .chk file finished with following warnings
>
> BR0280I BRCONNECT time stamp: 2009-04-01 10.30.50
> BR0972I Checking database operations...
> BR0973W Database operation alert - level: WARNING, operation: cdzsjafp.log, time: 2009-01-17 05.13.45, condition: Last 'log' operation failed with rc = 3
>
> Kindly help me resolve the issue.
>
> Regards
> Mohsin
Hello,
The warning occurs because the database check looks for the logs of all old operations that ended with an error. The text "Last 'log' operation" means: an operation log with the extension ".log"was found for an action that ended with the (error) status RC = 3.
Since the log referred to is old (January 17), you can get rid of it by running:
brconnect -u / -c force -f cleanup -m 60
(60 is the minimum age of the logs to clean up; adapt this value to your requirements)
Also, it is a good idea to schedule the action "Cleanup logs" periodically via DB13.
Regards,
Mark

XML PrintSelectedInvoices completes with warning when run as child request

Hi Friends,
I have converted the print selected invoices to xml and it runs fine when run by itself through SRS but it fails when it is submitted as a child request ( when it gets run as a child request when Invoice import and print program is run). Here is the problem:
1)When request is submitted, through SRS it passes fine and while submitting I find the template name,template language in theoptions button: Upon completion �Window:(UNDER LAYOUT section)
2)BUT When request is submitted as child request it fails and while submitting this; Ifind that there is no information in the layout section in the options: Uponcompletion �Window:(UNDER LAYOUT SECTION).You will see that there is notemplate name,template language etc. and details picked in the Upon Completionwindow under OPTIONS buton in SRS.
Also the error in the log file is as follows:
Printing output file.
Request ID : 41921527
Number of copies : 1
Printer : 11111
Error: May not be a PDF file (continuing anyway)
Error (0): PDF file is damaged - attempting to reconstruct xref table...
Error: Couldn't find trailer dictionary
Error: Couldn't read xref table
Pasta: Error: Preprocess failed. Command=/usr/testinstance/temp/pasta13459_0.tmp /n00/common/testinstance/temp/pasta13459_1.tmp
Pasta: Error: Preprocess or Print command failed!!!
APP-FND-00500: AFPPRN received a return code of failure from routine FDUPRN. Program exited with status 1
Cause: AFPPRN received a return code of failure from the OSD routine FDUPRN. Program exited with status 1.
Regards
Ray

Register the template before using it.
Once it is registered, you can call that report as a child request.
Regards
Ray

Shipping Exceptions Report Ends with Warning When Submitted as Part of Doc.

Hi all
My version 11.5.9
OS RHEL 4.6
lpr: error - unable to print file: client-error-not-found
APP-FND-00500: AFPPRN received a return code of failure from routine FDUPRN. Program exited with status 1
Cause: AFPPRN received a return code of failure from the OSD routine FDUPRN. Program exited with status 1.
When i tried with no of copies'0' it worked fine for some doc.
For others am getting same error.

Duplicate post.
APP-FND-00500
APP-FND-00500

Assembly finished with errors

Hello ,
Assembly finished with errors , when I check the logs found the logs from repostory-export as below. please provide me inputs to resolve this issue
20090313124906 Info :Starting Step Repository-export at 2009-03-13 12:49:06.0432 +1:00
20090313124906 Info :Start export of sources
20090313124906 Info :Component: sap.com/SAP_ESS Version :D66_ESSMODI_C.20090313114905 is processed now.
20090313124906 Info :1. PR is of type TCSSoftwareComponent
20090313124906 Info :Start reading sources of SC sap.com,SAP_ESS from DTR http://sapd66.deutsche-boerse.de:50000/dtr
20090313124906 Detail :Start creating PropagationList 'CMS_sap.com_SAP_ESS_5_5268ee8bf6a811dd805a00145ed1abbe'.
20090313124908 Fatal :VcmFailure received
20090313124908 Fatal :caused by Exception:com.tssap.dtr.client.lib.deltavlib.VcmFailure: The transaction failed with [INTERNAL SERVER ERROR].:The transaction failed with [INTERNAL SERVER ERROR].
com.tssap.dtr.client.lib.deltavlib.VcmFailure: The transaction failed with [INTERNAL SERVER ERROR].
 at com.sap.cms.tcs.client.DTRCommunicator.createPropagationList(DTRCommunicator.java:939)
 at com.sap.cms.tcs.client.DTRCommunicator.getExport(DTRCommunicator.java:314)
 at com.sap.cms.tcs.core.RepositoryExportTask.processRepositoryExport(RepositoryExportTask.java:158)
 at com.sap.cms.tcs.core.RepositoryExportTask.process(RepositoryExportTask.java:333)
 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.assemblePropagationRequests(TCSManager.java:739)
 at com.sap.cms.pcs.assembly.manager.AssemblyManager.assemble(AssemblyManager.java:1068)
 at com.sap.cms.pcs.assembly.manager.AssemblyManager.startLevelAssembly(AssemblyManager.java:468)
 at com.sap.cms.pcs.assembly.manager.AssemblyManager.startQueueAssembly(AssemblyManager.java:350)
 at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startAssembly(CmsTransportProxyBean.java:1096)
 at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startAssembly(LocalCmsTransportProxyLocalObjectImpl0_0.java:2302)
 at com.sap.cms.ui.wl.Custom1.startComponetAssembly(Custom1.java:16703)
 at com.sap.cms.ui.wl.Custom1.assembleQueue(Custom1.java:4845)
 at com.sap.cms.ui.wl.wdp.InternalCustom1.assembleQueue(InternalCustom1.java:2901)
 at com.sap.cms.ui.wl.Worklist.handleAssemblyOptionsEvent(Worklist.java:1625)
 at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2991)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
 at com.sap.tc.webdynpro.progmodel.controller.Component.fireEvent(Component.java:284)
 at com.sap.cms.ui.wl.wdp.InternalWorklists.wdFireEventAssemblyOptionsEvent(InternalWorklists.java:470)
 at com.sap.cms.ui.wl.Worklists.fireAssemblyOptionsEvent(Worklists.java:247)
 at com.sap.cms.ui.wl.wdp.InternalWorklists.fireAssemblyOptionsEvent(InternalWorklists.java:402)
 at com.sap.cms.ui.wl.AssemblyOptionsPopup.startAssembly(AssemblyOptionsPopup.java:1360)
 at com.sap.cms.ui.wl.AssemblyOptionsPopup.onActionStartAssemblyAndAttachToCTS(AssemblyOptionsPopup.java:715)
 at com.sap.cms.ui.wl.wdp.InternalAssemblyOptionsPopup.wdInvokeEventHandler(InternalAssemblyOptionsPopup.java:660)
 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.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
 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(AccessController.java:219)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
20090313124908 Fatal :caused by Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: The transaction failed with [INTERNAL SERVER ERROR].:communication error: VcmFailure received: The transaction failed with [INTERNAL SERVER ERROR].
com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: The transaction failed with [INTERNAL SERVER ERROR].
 at com.sap.cms.tcs.client.DTRCommunicator.getExport(DTRCommunicator.java:350)
 at com.sap.cms.tcs.core.RepositoryExportTask.processRepositoryExport(RepositoryExportTask.java:158)
 at com.sap.cms.tcs.core.RepositoryExportTask.process(RepositoryExportTask.java:333)
 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.assemblePropagationRequests(TCSManager.java:739)
 at com.sap.cms.pcs.assembly.manager.AssemblyManager.assemble(AssemblyManager.java:1068)
 at com.sap.cms.pcs.assembly.manager.AssemblyManager.startLevelAssembly(AssemblyManager.java:468)
 at com.sap.cms.pcs.assembly.manager.AssemblyManager.startQueueAssembly(AssemblyManager.java:350)
 at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startAssembly(CmsTransportProxyBean.java:1096)
 at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startAssembly(LocalCmsTransportProxyLocalObjectImpl0_0.java:2302)
 at com.sap.cms.ui.wl.Custom1.startComponetAssembly(Custom1.java:16703)
 at com.sap.cms.ui.wl.Custom1.assembleQueue(Custom1.java:4845)
 at com.sap.cms.ui.wl.wdp.InternalCustom1.assembleQueue(InternalCustom1.java:2901)
 at com.sap.cms.ui.wl.Worklist.handleAssemblyOptionsEvent(Worklist.java:1625)
 at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2991)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
 at com.sap.tc.webdynpro.progmodel.controller.Component.fireEvent(Component.java:284)
 at com.sap.cms.ui.wl.wdp.InternalWorklists.wdFireEventAssemblyOptionsEvent(InternalWorklists.java:470)
 at com.sap.cms.ui.wl.Worklists.fireAssemblyOptionsEvent(Worklists.java:247)
 at com.sap.cms.ui.wl.wdp.InternalWorklists.fireAssemblyOptionsEvent(InternalWorklists.java:402)
 at com.sap.cms.ui.wl.AssemblyOptionsPopup.startAssembly(AssemblyOptionsPopup.java:1360)
 at com.sap.cms.ui.wl.AssemblyOptionsPopup.onActionStartAssemblyAndAttachToCTS(AssemblyOptionsPopup.java:715)
 at com.sap.cms.ui.wl.wdp.InternalAssemblyOptionsPopup.wdInvokeEventHandler(InternalAssemblyOptionsPopup.java:660)
 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.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
 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(AccessController.java:219)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
20090313124908 Info :Remove software component SAP_ESS from further processing.
20090313124908 Info :Step Repository-export ended with result 'error' at 2009-03-13 12:49:08.0279 +1:00
Koti Reddy

Hi,
According to my previous experience, error points that NWDI is configured incorectly.
"20090313124908 Fatal :VcmFailure received
20090313124908 Fatal :caused by Exception:com.tssap.dtr.client.lib.deltavlib.VcmFailure: The transaction failed with INTERNAL SERVER ERROR.:The transaction failed with INTERNAL SERVER ERROR."
What you can do it to run comfiguration wizzard on NWDI for CBS; CMS & DTR:
NWDI Server:
http://<servername>:<port number>/nwa
Deploy & Change --> Select DI_CBS & click start: This will walk you through wizard and once completed successfuly run for DI_CMS & DI_DTR.
Furthermore, please start the Visual Admin of the Engine and check that
the following values are set:
Dispatcher-> Services->HTTP Provider -> Properties TAB
KeepAliveTimeout = 300 (seconds)
MaxRequestContentLength = 1048576 (kB)
Server->Services-> HTTP Provider -> Properties TAB
ServletsLongDataTransferTimeout = 600000 (milli seconds)
Also just to have clean system(no hanged up resources), restart your NWDI system bufore you start assemble.
Bhavin

Warning when patching EP SP 11

Dear SDN,
I deployed patch number SP11 for ep 6. During the installation sapinst gave the message that "a component deployed with errors and additional steps may need to be manually done after the patch.
This is the error in th callSDMviaSAPinst log
F:\sapdown\SP11\ep6sp11\SAPINST-CD\PORTAL\JAVA-LIB\com.sapportals.dqe.service.sda
Mar 30, 2005 7:02:22 PM Error: Executed, but finished with warning(s). Return code: 102
What can I do about this?
Thanks
Jeremy

On the first screen of SDM, on the bottom right corner of the screen, you will see a block style arrow. Click on that and it will expand a part of the screen that controls the behavior you are looking for.

ESS/MSS business packages "Deployed with Warning"

Hello All,
 We are on NW04s SP10 on MS SQL server and Windows server. The Database and portal installations or on different machines. I installed the business packages ESS 1.0, MSS 1.0 and the XSS components - 600 using the JSPM.
After I deploy, I get the message "Deployed with Warning"
When I opened the log files and checked for errors, I found errors in deployment on these SDAs
sap.com/essfiaddr - WEBDYNPRO
sap.com/essinaddr - WEBDYNPRO
sap.com/essinpdata - WEBDYNPRO
sap.com/mssexpdyn - WEBDYNPRO
sap.com/mssexpssa - WEBDYNPRO
sap.com/mssoprogeneraldescription - WEBDYNPRO
And I get the following exceptions for all the SDAs above.
07/01/11 09:54:10 - sap.com/essfiaddr - WEBDYNPRO
07/01/11 09:54:10 - ***********************************************************
Jan 11, 2007 9:54:11 AM Info: End of log messages of the target system.
Jan 11, 2007 9:54:11 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jan 11, 2007 9:54:11 AM Warning: Finished with warnings: development component 'ess/fi/addr'/'sap.com'/'MAIN_ERP05PAT_C'/'795293':
Caught exception during application startup from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while starting application sap.com/ess/fi/addr and wait.
Reason: Clusterwide exception: server ID 11376250:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''sap.com/essfiaddr'' for startup. Reason=
Clusterwide exception: Failed to start application ''sap.com/essfiaddr'': The referenced application ''sap.com/ess~per'' can''t be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?
 at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1490)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:231)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:317)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:111)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:227)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4684)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4589)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4562)
 at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
 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:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Now, after this, when I log into the portal and see the MSS role, the links are all missing. I see only Overview and its worksets and pages and Reports and its worksets. Everything else is missing. The warning that I see is "Linked object is unavailable"
Could anyone please suggest me what could be wrong?
Thanks,
Sunitha

Hi Sunitha,
First of all I was not able to find if your backend is ERP 2004 or ERP 2005. It should be ERP 2005 if you want to user ESS 1.0 and MSS 1.0 BP
Please check in Content Administrator if you can locate these applications and test the same. If yes then you can ignore this warning. If No, in that case you have to redeploy XSS, ESS and MSS using SDM again.
The links in portal comes from your backend Area Page Customizing. To verify if the problem is with your Portal Business Package or with your backend customizing run your ESS applications using
http://<portal>:<port>/webdynpro/dispatcher/sap.com/pcui_gp~xssutils/XssMenuArea?sap.xss.menuhdr=SAPDEFAULT&sap.xss.menuargrp=SAPDEFAULTESS
and MSS using
http://<portal>:<port>/webdynpro/dispatcher/sap.com/pcui_gp~xssutils/XssMenuArea?sap.xss.menuhdr=SAPDEFAULT&sap.xss.menuargrp=SAPDEFAULTMSS
If you can see all the links correctly here, your backend customization is fine and there is a problem with your BP of ESS and MSS. So you will have to import the same again in the portal. However if you are not able to view the links in the page, then there is a problem with you Area Page Customization. You will need to check your config with the Client 000 configuration to find out the missing config.
Hope this helps.
Regards,
Shubham

Deploy with warning

Hi.All.
when i deployed WD application , it end with warning ,could someone tell me how to do.
--- Deploying file(s):
     E:\Documents and Settings\MrBryant\workspace_rt.jdi\LocalDevelopment\DCs\demo.sap.com\tutorial_pagenavigation\_comp\gen\default\deploy\demo.sap.com~tutorial_pagenavigation.ear
--- Status:
     Deploy finished with warnings.
--- Description:
            S U M M A R Y
~~~~~~~~~~~~~~~~~~~
Successfully deployed:           0
Deployed with warnings:           1
Failed deployments:                0
~~~~~~~~~~~~~~~~~~~
1. File:E:\Documents and Settings\MrBryant\workspace_rt.jdi\LocalDevelopment\DCs\demo.sap.com\tutorial_pagenavigation\_comp\gen\default\deploy\demo.sap.com~tutorial_pagenavigation.ear
     Name:tutorial_pagenavigation
     Vendor:demo.sap.com
     Location:localDevelopment
     Version:20090421170011
     Deploy status:Warning
     Version:HIGHER
     Description:
          1. Exception has been returned while the [demo.sap.com/tutorial_pagenavigation] was starting. Warning/Exception :[
][[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: [server ID 48033250:can't instantiate default ORB implementation com.sun.enterprise.iiop.POAEJBORB
           -> com.sun.enterprise.iiop.POAEJBORB
------------------------- Loader Info -------------------------
ClassLoader name: [service:deploy]
Living status: alive
Direct parent loaders:
   [system:Frame]
   [library:core_lib]
   [library:tc~bl~txmanager~plb]
   [service:iiop]
   [service:file]
   [library:tc~je~jlinee~lib]
Resources:
   /usr/sap/C04/J04/j2ee/cluster/bin/services/deploy/lib/private/sap.com~tc~je~deploy~impl.jar
server ID 48033250:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application [demo.sap.com/tutorial_pagenavigation] cannot be started. Reason: it has hard reference to resource [tc~wd~api] with type [application], which is not active on the server.
Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?
     at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:871)
     at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:848)
     at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:575)
     at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:489)
     at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:169)
     at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:134)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:467)
     at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:560)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:197)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:358)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3432)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3418)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3308)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3280)
     at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:105)
     at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:78)
     at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
     at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:91)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:61)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:862)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:810)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:640)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:359)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:248)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:897)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:355)
     at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:67)
     at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:41)
     at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:977)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:57)
     at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application [sap.com/tc~wd~api] cannot be started. Reason: it has hard reference to resource [tc~wd~dispwda] with type [application], which is not active on the server.
Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?
     at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:871)
     at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:848)
     at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:575)
     at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:489)
     at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:169)
     at com.sap.engine.services.deploy.server.application.StartTransaction.beginLocal(StartTransaction.java:142)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:582)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:202)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:367)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.regularStartApplicationLocalAndWait(DeployServiceImpl.java:3229)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:3221)
     at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:863)
     ... 35 more
Caused by: com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Error in starting application [sap.com/tc~wd~dispwda].
     at com.sap.engine.services.servlets_jsp.server.deploy.StartAction.prepareStart(StartAction.java:246)
     at com.sap.engine.services.servlets_jsp.server.deploy.WebContainer.prepareStart(WebContainer.java:420)
     at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:228)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:194)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:591)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:202)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:367)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.regularStartApplicationLocalAndWait(DeployServiceImpl.java:3229)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:3221)
     at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:863)
     ... 46 more
Caused by: org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementation com.sun.enterprise.iiop.POAEJBORB vmcid: 0x0 minor code: 0 completed: No
     at org.omg.CORBA.ORB.create_impl(ORB.java:297)
     at org.omg.CORBA.ORB.init(ORB.java:336)
     at com.sap.engine.services.servlets_jsp.server.application.NamingResources.bindNamingResources(NamingResources.java:147)
     at com.sap.engine.services.servlets_jsp.server.application.ApplicationContext.init(ApplicationContext.java:937)
     at com.sap.engine.services.servlets_jsp.server.deploy.StartAction.createContext(StartAction.java:305)
     at com.sap.engine.services.servlets_jsp.server.deploy.StartAction.prepareStart(StartAction.java:141)
     ... 56 more
Caused by: java.lang.ClassNotFoundException: com.sun.enterprise.iiop.POAEJBORB
------------------------- Loader Info -------------------------
ClassLoader name: [service:deploy]
Living status: alive
Direct parent loaders:
   [system:Frame]
   [library:core_lib]
   [library:tc~bl~txmanager~plb]
   [service:iiop]
   [service:file]
   [library:tc~je~jlinee~lib]
Resources:
   /usr/sap/C04/J04/j2ee/cluster/bin/services/deploy/lib/private/sap.com~tc~je~deploy~impl.jar
     at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:274)
     at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:243)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:363)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:242)
     at org.omg.CORBA.ORB.create_impl(ORB.java:295)
     ... 61 more
Result
Status:Warning
Edited by: zhenhua peng on Apr 21, 2009 11:24 AM

Hi,
From the logs it is clear that your application is dependent on [tcwdapi] which is either not deployed on the target server or failed to start. This is called as class loader exception. To overcome this issue, you have to either deploy the reference application or see to that it is in "Started" status in the target server. If you have trouble in starting the application, then it might be necessary to restart the java server and then do the deployment.
Regards,
Pranav

Problems with navigation when deploy application on WebLogic 10.3

Hi! I have problems with navigation when I deploy my application on Weblogic server 10.3. In my application I have two pages. One page where I can see the records. In this page I have button Create with action to secound jspx page. When I press this button then the first form (where I could see all records) is empty - the create operation worked, but navigation to second page not. Navigation rules is in adf task flow. In default server all works correct. Where is the problem?
Maybe when I deploy my application I need specialy deploy adf task flow or somewhere write something? If so, then can you explain me where? Any suggestions what to do.
Best regards!

I have in log:
2009.26.3 20:12:52 oracle.adfinternal.controller.faces.lifecycle.JSFLifecycleImp
l setLifecycleContextBuilder
WARNING: ADFc: Replacing the ADF Page Lifecycle implementation with 'oracle.adfi
nternal.controller.application.model.JSFDataBindingLifecycleContextBuilder'.
2009.26.3 20:12:52 oracle.adfinternal.controller.util.model.AdfmInterface initia
lize
INFO: ADFc: BindingContext is present, using ADFm APIs for DataControlFrames.
2009.26.3 20:12:52 oracle.adfinternal.controller.metadata.provider.MdsMetadataRe
sourceProvider <init>
INFO: ADFc: Controller caching of MDS metadata resources ENABLED.
2009.26.3 20:12:52 oracle.adf.controller.internal.metadata.MetadataService$Boots
trap add
INFO: ADFc: Loading bootstrap metadata from '/WEB-INF/adfc-config.xml'.
2009.26.3 20:12:54 oracle.adf.share.security.providers.jps.CSFCredentialStore fe
tchCredential
WARNING: Unable to locate the credential for key AUGI in D:\bea\user_projects\do
mains\base_domain\config\oracle.
2009.26.3 20:12:54 oracle.adf.share.jndi.ReferenceStoreHelper throwPartialResult
Exception
WARNING: Incomplete connection information
Edited by: Debuger on Mar 26, 2009 11:18 AM

EJB3.0 App deployed with warning:Object not found in lookup of JPA_DEFAULT

Hi All ,
 I am working on NWCE7.1. I am deploying Enterprise Application DC wich is having
1 . 3 EJB3.0 session DCs
2. 1 JPA DC
I am getting following warning in deployment. I have checked persistence.xml for jta-data-source , it is added. Still not working. I am getting this error after importing configuration(Track) for these DCs in my NWDS. Earlier build n deployment was working in other NWDS on other PC.
--- Deploying file(s):
 D:\NWDS7.1\workspace.jdi\4\DCs\asianpaints.com\erecapp\_comp\gen\default\deploy\asianpaints.com~erecapp.ear
--- Status:
 Deploy finished with warnings.
--- Description:
 S U M M A R Y
~~~~~~~~~~~~~~~~~~~
Successfully deployed: 0
Deployed with warnings: 1
Failed deployments: 0
~~~~~~~~~~~~~~~~~~~
1. File:D:\NWDS7.1\workspace.jdi\4\DCs\asianpaints.com\erecapp\_comp\gen\default\deploy\asianpaints.com~erecapp.ear
 Name:erecapp
 Vendor:asianpaints.com
 Location:J2N_ERECTT_D
 Version:20090217100038
 Deploy status:Warning
 Version:HIGHER
 Description:
 1. Exception has been returned while the 'asianpaints.com/erecapp' was starting. Warning/Exception :
[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
 com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 6358450:com.sap.engine.services.orpersistence.container.deploy.ActionException: [ERROR CODE DPL.DS.5030] Clusterwide exception: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of JPA_DEFAULT.
 at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:584)
 at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:343)
 at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:637)
 at javax.naming.InitialContext.lookup(InitialContext.java:351)
 at javax.naming.InitialContext.lookup(InitialContext.java:351)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:344)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:230)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:154)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:84)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
 at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
 at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
 at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
 at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
 at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
 at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
 at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
 at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
 at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:360)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:230)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:154)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:84)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
 at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
 at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
 at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
 at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
 at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
 at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
 at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
 at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
 at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Result
Status:Warning

You have to give an explicit data source in your persistence.xml to solve this error normaly.
<persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
 <persistence-unit name="YOUR_UNIT">
 <jta-data-source>DSNAME</jta-data-source>
Frank

My project is finish with final cut 4 when i export on quick time a window open and says (error 34 ) is anyone knows what is the problem tanks DENIS

my project is finish with final cut 4 when i export via quick time a window open and says (error 34 ) what is the problem .
i've made many transfers before and every time it was excellent thanks denis

Is the external formatted tmac OS Extended?
It should be.
Al

Deployment projects with other installers inside?

Hello,
I'm developing application with Kinect and I want to create an installer to distribute it. Also, I need to install .NET Framework 4.0 if it is not installed. I'm working with VS 2012, so I had to install InstallShield LE but does not seem to have the option
to add an external installer. Do you know how can I do it? Maybe with WiX projects or Nullsoft?
Thank you!

Hello,
Thank you for your post.
I am afraid that the issue is out of support range of VS General Question forum which mainly discusses the usage of Visual Studio IDE such as
WPF & SL designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System
and Visual Studio Editor.
I did some search and find an article which may help you:
http://www.microsoft.com/en-us/kinectforwindows/faq.aspx
About deploying projects with Kinect, please reference ‘Can you provide some examples of recent Kinect for Windows
deployments?’ section on that article above. For detailed information and more support, please consult on Kinect for Windows SDK forum:
http://social.msdn.microsoft.com/Forums/en-US/home?category=kinectsdk
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Deployment finished with warning when I deploy projects!

Similar Messages

Maybe you are looking for