Error when deploy the Planning SampAp application view

When deploying, the job console shows:
Started Time : 2008年3月4日 13:23:49
Submitted Time : 2008年3月4日 13:23:49
Last Updated Time : 2008年3月4日 13:23:52
User Name : admin
Process Name :
Thread : 0
Server : DimServer
Detail : Initiating Product Action...
Inspecting Deployment History...
Generating Headers and Callback Information...
Generating Application Data...
Preparing Product Request...
Posting Product Request...
Product Response:200...
Waiting For Status Updates...
and it was stocked at 9%. After a while, the job console showed:
Started Time : 2008年3月4日 11:41:34
Submitted Time : 2008年3月4日 11:41:34
Last Updated Time : 2008年3月4日 11:46:45
User Name : admin
Process Name :
Thread : 0
Server : DimServer
Detail : App Creation failed with Exceptioncom.hyperion.planning.HspRuntimeException: Unable to locate dimension information to load. Dimension: Currency at com.hyperion.planning.HspDimensionLoader.parseModelForPlanningDimen(Unknown Source) at com.hyperion.planning.HspDimensionLoader.parseModelForPlanningDimen(Unknown Source) at com.hyperion.planning.HspDimensionLoader.parse(Unknown Source) at com.hyperion.planning.HspDimensionLoader.load(Unknown Source) at com.hyperion.planning.HspDimensionLoader.load(Unknown Source) at com.hyperion.planning.utils.HspApplicationCreator.loadOutline(Unknown Source) at com.hyperion.planning.utils.HspApplicationCreator.load(Unknown Source) at com.hyperion.planning.utils.HspApplicationCreator.createApplication(Unknown Source) at com.hyperion.planning.appdeploy.HspAppDefinition.deployAppFromXML(Unknown Source) at com.hyperion.planning.appdeploy.HspAppDefinition.access$000(Unknown Source) at com.hyperion.planning.appdeploy.HspAppDefinition$1.run(Unknown Source)
I've created a new datasource for this app, but still faced the same problem.
PS: I also found some error when validate the SampAp application view, so I've changed it a little. I don't know if the application view design may cause this problem. Thanks for your reply.

Hi,
From another post which I think relates to same sort of issue the solution was :-
On your server > Change your "Standards and formats" into English(United States) in "Regional and Language Options".
This was due to the currency format being in chinese.
Cheers
John

Similar Messages

When deploying the webdynpro java application , showing error message

Hi Masters,
when deploying the webdynpro java application , showing error message. Please reply why this problem showing and what is the solution
But Iogin to sdm tool ( remote gui .sh) with same password, which password i am using for deploy the webdynpro java application.here in sdm tool i am able to login. and i restart the sdm , and again trying to deploy the same problem it showing.
URL to deploy : file:/C:/DOCUME1/ppuser/LOCALS1/Temp/temp30925rupa.com~sales.ear
Result
=> deployment aborted : file:/C:/DOCUME1/ppuser/LOCALS1/Temp/temp30925rupa.com~sales.ear
Aborted: development component 'sales'/'rupa.com'/'LOKAL'/'0.2010.02.13.14.32.39':Caught exception during application deployment from SAP J2EE Engine's deploy API:com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [devsap] with user name: [J2EE_ADMIN] Check your login information. Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: No login module succeeded.] (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC)
Deployment exception : The deployment of at least one item aborted
Edited by: sujana mullapudi on Feb 13, 2010 2:52 PM

Hi Sujana,
For deploying Web Dynpro for Java application, J2EE_admin correct password must be stored in the scured area of config tool.
Your error show that J2EE_admin information is not correct.
So, Please ask your basis team to update new J2EE_ADMIN password or you can do it in scured area of config tool.
Hope this will helps you.
Thanks
Arun Jaiswal

Getting Error when deploying the WD application

hi all,
Anybody have idea about , what is the reason for the following error. Till now it is working properly. suddenly it is giving the following error when deploying the application.
2.4.2007 13:17:36 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[004]Deployment aborted
Settings
SDM host : eimkopdvs4
SDM port : 50118
URL to deploy : file:/C:/WINDOWS/TEMP/temp2898TestWebDynproProj.ear
Result
=> deployment aborted : file:/C:/WINDOWS/TEMP/temp2898TestWebDynproProj.ear
Aborted: development component 'TestWebDynproProj'/'local'/'LOKAL'/'0.2007.04.02.13.17.28'/'0':
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [EIMKOPDVS4] with user name: [Administrator]                     Check your login information.                     Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
     at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:494)
     at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:363)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
     at javax.naming.InitialContext.init(InitialContext.java:219)
     at javax.naming.InitialContext.<init>(InitialContext.java:195)
     at com.sap.engine.deploy.manager.DeployManagerImpl.checkCredentials(DeployManagerImpl.java:2983)
     at com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthMethodInvoker.invokeCheckCredentialsInternal(DeployManagerAuthMethodInvoker.java:51)
     at com.sap.sdm.serverext.servertype.inqmy.extern.ExternalMethodInvoker.invokeCheckCredentials(ExternalMethodInvoker.java:45)
     at com.sap.sdm.serverext.servertype.inqmy.extern.ExternalMethodInvoker.invokeCheckCredentials(ExternalMethodInvoker.java:32)
     at com.sap.sdm.serverext.servertype.inqmy.extern.EngineOnlineDeployerImpl.checkLoginCredentials(EngineOnlineDeployerImpl.java:173)
     at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:167)
     at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
     at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
     at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
     at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
     at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:48)
     at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
     at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
     at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
     at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
     at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
     at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:120)
     at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:89)
     at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)
     at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)
     at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84)
     at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
     at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
     at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)
     at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
     at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
     at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
     at java.lang.Thread.run(Thread.java:534)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
     at com.sap.engine.services.security.remote.login.RemoteLoginContextExt.<init>(RemoteLoginContextExt.java:34)
     at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:81)
     at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:355)
     ... 37 more
Caused by: java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/10.4.71.36,port=50104,localport=3057]
     at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:420)
     ... 1 more
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
Deployment exception : The deployment of at least one item aborted

Hi,
Check if the server is running. If so, try restarting it and then retry.

Error When Deploying a planning application

I've prepared a planning application in hyperion 9.3;
Validation is successful but when deploying the application deployment fails with the message "Action aborted. Please check the Job Status for results."
Job status shows:
===============================================================================
Started Time : Sunday, March 08, 2009 6:39:27 PM
Submitted Time : Sunday, March 08, 2009 6:39:27 PM
Last Updated Time : Sunday, March 08, 2009 6:39:29 PM
User Name : amjad
Process Name :
Thread : 0
Server : DimServer
Detail : Initiating Product Action...
Inspecting Deployment History...
Generating Headers and Callback Information...
Generating Application Data...
Preparing Product Request...
Posting Product Request...
Product Response:550...
Action aborted.
================================================================================
any suggestion?

Hi,
If you are going to be using EPMA the first thing to do is to make sure you have installed all the patches for EPMA and Planning.
They are available from [metalink3|https://metalink3.oracle.com/od/faces/index.jspx] , planning is at patch 9.3.1.1.10 and EPMA has around 5 patches.
Cheers
John
http://john-goodwin.blogspot.com/

Error while deploying the Web Dynpro application

HI All,
I have developed a Web dynpro application. Now when I am deploying the application I am getting an error.
Description
Jan 8, 2008 2:14:12 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[002]Deployment aborted
Deployment exception : Cannot determine sdm host (is empty). Please configure your engine/sdm correctly !
Can any one please help me regarding this.
Regards
Neha

Hi Neha,
It seems that there is problem with your SDM server. It seems that during J2EE engine configuration SDM server is not configured. Actually this configuration is done by Basis Team.
By the way try out your Server setting:
Go To:: Windows -> Preferences -> SAP J2EE Engine
[Mention the required details over there]
And Check whether you are getting Active SDM Server under J2EE Engine.
Regards,
Nittin Garg

Error while deploying the ADF Mobile application to the Android Emulator.

Hi,
I'm getting an error when trying to deploying a basic helloworld ADF mobile application to my Android sdk emulator which is already running as below.
I'm not able to make anything from this limited log. Can anyone have a look and help me with what could be wrong.
Any kind of suggestions are most welcome.
[06:09:30 PM] Print the version of this tool (1.7).
[06:09:30 PM] dx --help
[06:09:30 PM] Print this message.
[06:09:30 PM] Command-line execution failed (Return code: 1)
[06:09:30 PM] Command-line executed: "D:\1_DevCore\android_sdk\adt-bundle-windows-x86_64-20130219\sdk\platform-tools\dx.bat" dex debug keep-classes output="D:\jdevuserhome\111230\ADFMobile\MyMobileApps\ MyMobileApp01\ MyMobileApp01\deploy\ANDROID_MOBILE_NATIVE_archive1\classes.dex" D:\jdevuserhome\111230\ADFMobile\MyMobileApps\ MyMobileApp01\ MyMobileApp01\deploy\ANDROID_MOBILE_NATIVE_archive1\classes D:\jdevuserhome\111230\ADFMobile\MyMobileApps\ MyMobileApp01\ MyMobileApp01\deploy\ANDROID_MOBILE_NATIVE_archive1\framework\build\jar\AND_ksoap.jar D:\jdevuserhome\111230\ADFMobile\MyMobileApps\ MyMobileApp01\ MyMobileApp01\deploy\ANDROID_MOBILE_NATIVE_archive1\framework\build\jar\Container.jar D:\jdevuserhome\111230\ADFMobile\MyMobileApps\ MyMobileApp01\ MyMobileApp01\deploy\ANDROID_MOBILE_NATIVE_archive1\framework\build\jar\IDMMobileSDK.jar D:\jdevuserhome\111230\ADFMobile\MyMobileApps\ MyMobileApp01\ MyMobileApp01\deploy\ANDROID_MOBILE_NATIVE_archive1\framework\build\jar\logging_dalvik_release.jar D:\jdevuserhome\111230\ADFMobile\MyMobileApps\ MyMobileApp01\ MyMobileApp01\deploy\ANDROID_MOBILE_NATIVE_archive1\framework\build\jar\phonegap.jar D:\jdevuserhome\111230\ADFMobile\MyMobileApps\ MyMobileApp01\ MyMobileApp01\deploy\ANDROID_MOBILE_NATIVE_archive1\framework\build\jar\vmchannel_dalvik_release.jar
[06:09:30 PM] Shutting down Android Debug Bridge server...
[06:09:30 PM] Deployment cancelled.
[06:09:30 PM] ---- Deployment incomplete ----.
[06:09:30 PM] Deployment failed due to one or more errors returned by 'D:\1_DevCore\android_sdk\adt-bundle-windows-x86_64-20130219\sdk\platform-tools\dx.bat'. The following is a summary of the returned error(s):
Command-line execution failed (Return code: 1)
Thanks,
Bhasker

I'm not able to make anything from this limited log.
For Android emulator logs run the following command.
adb logcat
logcat | Android Developers

Error while deploying the Eclipse Link Application into Server

Hi guys,
i tried to deploy the application using Eclipselink into the server. but i got the following exception:
Error processing persitence unit EJBModel of module WLEclipseLinkDemo-ejb.jar: Error instantiating the Persistence Provider class org.eclipse.persistence.jpa.PersistenceProvider of the PersistenceUnit EJBModel: java.lang.ClassNotFoundException: org.eclipse.persistence.jpa.PersistenceProvider
Full StackTrace:
Failure occurred in the execution of deployment request with ID '1243622816661' for task '1'. Error is: 'weblogic.application.ModuleException: ' weblogic.application.ModuleException: at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:387) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) weblogic.deployment.EnvironmentException: Error processing persitence unit EJBModel of module WLEclipseLinkDemo-ejb.jar: Error instantiating the Persistence Provider class org.eclipse.persistence.jpa.PersistenceProvider of the PersistenceUnit EJBModel: java.lang.ClassNotFoundException: org.eclipse.persistence.jpa.PersistenceProvider at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:322) at weblogic.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:123) at weblogic.deployment.AbstractPersistenceUnitRegistry.storeDescriptors(AbstractPersistenceUnitRegistry.java:331) at weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDescriptor(AbstractPersistenceUnitRegistry.java:245) at weblogic.deployment.ModulePersistenceUnitRegistry.<init>(ModulePersistenceUnitRegistry.java:63) at weblogic.ejb.container.deployer.EJBModule.setupPersistenceUnitRegistry(EJBModule.java:209) at weblogic.ejb.container.deployer.EJBModule$1.execute(EJBModule.java:310) at weblogic.deployment.PersistenceUnitRegistryInitializer.setupPersistenceUnitRegistries(PersistenceUnitRegistryInitializer.java:62) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:381) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
but one thing, same EAR file is working in one server, but in another server it is giving the above exception.
i copied all the jars to server as same as working server. still i am getting the same error.
can anyone help me.
Rajesh

For WLS 10.3, I think that Kodo is the default JPA provider unless you apply a patch for EclipseLink/TopLink. Perhaps the WLS environments have installed different patches?
See the comment in this blog: http://msikora.typepad.com/michael_sikora_on_java_ee/2008/10/converting-to-weblogic-103---part-2.html
I think that it is a public patch when you run Smart Update.
There's also a detailed explanation here of the classpath options:
http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial
You may also get some help in the JPA forum:
TopLink/JPA

Error when deploy the web dynpro

Hi, i'm a newbie of SAP NWDS.
I have installed the NWDS 7.2 and Java JDK 1.6, the AS java is SAP J2EE Engine/7.01.
When i go to deploy the Welcome application i recive this errors:
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
       name:     'tc/bl/logging/api'
     vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
       name:     'tc/wd/api'
     vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
       name:     'tc/ddic/runtime/facade'
     vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
       name:     'tc/aii/base/offline/facade'
     vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
I think that my version of NWDS it's too new for the AS.
Have i to install an older version of NWDS and Java JDK?
What do you think?
Thanks.

Hi,
This is clearly a version imcompatibility issue ,
check below link :
/message/9597673#9597673 [original link is broken]
Please do some search on sdn before posting the questions. as the answer is already available.
Regards
Deepak

Error in Deploy the webdynpro java application.

Hi Friends,
while i deploy the allpication i am getting this error. what is this error.It is very urgent to me
Failed to process request. Please contact your system administrator.
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
   java.lang.NullPointerException
    at com.itc.espb.WeborderView.wdDoInit(WeborderView.java:145)
    at com.itc.espb.wdp.InternalWeborderView.wdDoInit(InternalWeborderView.java:392)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
    at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
    ... 32 more
Thanks & Regards,
Murali

HI Murali,
Clearly it is stating that Null Pointer exception is wdDoInit() method of WeborderView at line number 145. Check what logic you have written there and try to rectify it. Still if you are not able to do so, copy the logic here. I will try to help you.
Note: Inorder to enable line numbers, go to Window-> Preferences->Workbench->Editors->Text Editor->Show line numbers
Regards,
Jithin

Error when debugging the Web DynPro application-Flight Example

Hi all,
I am trying to execute the Flight Application example.
In the Search View I have entered City from and to and getting only one record in the table control as output in Result View irrespective of any cities.
I checked with SAPR/3 but it is showing more records.
For finding the error I tried to DEBUG the application.starting the DEBUG immediately I am getting the error REMOTE VM NOT CONNECTED.I am trying to solve this error to Starting the DEBUG.
If any tips to solve this error in DEBUG mode and what is the reson the other records are not showing in the output Result view.
Thanks in Advance.
Regards,
Ram

Hi,
This is clearly a version imcompatibility issue ,
check below link :
/message/9597673#9597673 [original link is broken]
Please do some search on sdn before posting the questions. as the answer is already available.
Regards
Deepak

Error When generating the plan layout

Dear All,
When i try to generate the file description for COPA planning through KP34ER, i get the following error..
I have checked all four points that they have mentioned. Any idea why this coud be?
No data has been entered yet.
Message no. KG845
Diagnosis
The planning layout you are using (COPAGI) only contains selection criteria for which no data has yet been entered. As a result, the system cannot display any plan data.
In this layout it is not possible to add characteristic values. This could be due to the following:
1. Manual planning is not allowed for the specified record type. Only record types A, F, G, E, and your user-defined record types can be planned manually.
2. The planning layout was only defined to contain actual data. The plan/actual indicator "1" is nowhere specified.
3. The selected plan version cannot be planned.
4. The lead column was defined so that only the texts of the characteristic values are displayed. As a result, no new characteristic values can be added in planning.
Procedure
Proceed as follows, depending on what the cause was:
1. Use a record type that can be planned manually.
2. None
3. Choose another plan version that can be planned.
4. Change the planning layout so that the key of the characteristic values is displayed in the lead column.
Thank you
Gayani

Hi,
Another possible reason could be, that in the general data selection of the layout is used the characteristic which is not restricted in the plannig package to the single value:
Example:
Let say the char. Country is used in the general data selection and is not restricted in the pl. package. Since the value for the
general data selection characteristic is not possible to enter in the layout, it is not possible to enter any data, because the user
could not enter for Country and the system doesn't know for what Country the planning is done. If you restrict the Country in the pl. package to single value (e.g. JP) then it will work, since the system knows now, that the data which will be entered belongs to the Country = JP.
So please make sure, that all general data characteristics are restricted to the single value in the planning package. Then it will work.
When we specify single value the planlayout can be displayed with "0" because of there is in this case already created (together with values of other characteristics) a concrete profitability segment that exists certainly. That means system can find and display this profitability segment.
But when we put interval 0000 - ZZZZ for a characteristic system doesn't know which values from this interval are the valid values that are able to be displayed for planning. For example the value 1010 can exist but 2020 does not exist and it would make no sence to offer these invalid values for display of planning data.
In general, message KG845 in case of selection defined by interval is raised also due performance reasons. Selection
defined by interval(s) could lead to big number of possible combinations, which should be displayed regardless of fact that no data are already posted in database.
The idea is following- if there is selection defined by single values, then we don't care about performance and we display data (empty) values as it's fast(regardless of fact that no data are posted in database). In case of selection by interval, performance is an issue because we have to display all combinations of data, which can be generated. This could lead to thousands of possible combinations and long system response. This is not intended and it makes no real sense. Basic idea
here is that we use different approach in case that selection is defined by interval and different approach, when selection is defined by single value.
I hope this helps.
regards
Waman

Getting Error when convert the plan order into production order

Hi Experts,
When i converting the planorder into production order i am getting this error
could you please suggest me hoew can i resolve this issue.
Message no. CK466
Diagnosis
The system could not calculate a price for the internal activity with activity type 20000 of cost
center 110TUP002 because none of the valuation strategies in valuation variant 006 was successful.
System Response
If the system issues a warning message or an information message, the costing item will be
used in costing with a value of zero.
If the system issues an error message, it sets the status "KF" (costed with errors).
If the system issues a termination message, the cost estimate cannot be processed.
Procedure
1. Check the master data for activity type 20000 of cost center 110TUP002.
2. If you have authorization for Customizing, check the valuation strategy for internal activities
in valuation variant 006.
Thanks&regards.
Sateesh.C

Hi,
For the orders for which you get the error, note the dates, then check in KSBT, whether there is price maintained for that period.
Eg: If the order has a start - 2nd Aug, 2010 & end 10th Aug, 2010, then check if price exists for period - 08, year - 2010
Regards,
Vivek
Added
If the values are maintained, then check the costing variants specified for the order type in OPL8 for plant - order type combination in cost accounting tab. Then in OPL1, check the details specified for the variants. If you're not sure on this, take help from your FI-Co colleague.

Getting Unknown Source Error While Deploying the Planning Application

Hi,
Getting following error while trying to Deploy Planning Application from BPMA
Started Time : Tuesday, January 08, 2008 5:43:40 PM
Submitted Time : Tuesday, January 08, 2008 5:43:40 PM
Last Updated Time : Tuesday, January 08, 2008 5:44:32 PM
User Name : hpadmin
Process Name :
Thread : 0
Server : DimServer
Detail : App Creation failed with Exceptionjava.lang.RuntimeException: Exception occurred while creating the application. Check log for details at com.hyperion.planning.appdeploy.HspAppDefinition.deployAppFromXML(Unknown Source) at com.hyperion.planning.appdeploy.HspAppDefinition.access$000(Unknown Source) at com.hyperion.planning.appdeploy.HspAppDefinition$1.run(Unknown Source)

Hi,
I am getting the same error:-
Started Time : Tuesday, February 26, 2008 4:14:31 PM
Submitted Time : Tuesday, February 26, 2008 4:14:31 PM
Last Updated Time : Tuesday, February 26, 2008 4:15:39 PM
User Name : hpadmin
Process Name :
Thread : 0
Server : DimServer
Detail : App Creation failed with Exceptionjava.lang.RuntimeException: Exception occurred while creating the application. Check log for details at com.hyperion.planning.appdeploy.HspAppDefinition.deployAppFromXML(Unknown Source) at com.hyperion.planning.appdeploy.HspAppDefinition.access$000(Unknown Source) at com.hyperion.planning.appdeploy.HspAppDefinition$1.run(Unknown Source)
1---Have created new user for new App as well datasource
2-Bounced the EPMA as well planning server but no avail.
how I can I get detail log ? or if is it possible to tell me which directory to look into
thanks in advance
Sanjay

Error when deploying new version of application on ALBPM 6.0.4

I keep getting this error on our dev box when trying to deploy a new version of the application: <May 21, 2010 12:25:41 PM CDT> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: javax.management.remote.rmi.RMIConnectionImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;Ljava.rmi.MarshalledObject;[Ljava.lang.String;Ljavax.security.auth.Subject;)
The system is ALBPM 6.0.4/WL 9.2/solaris
BEA AquaLogic(TM) BPM Enterprise for Application Server
Version: 6.0.4
Build: #98853
I have posted the full stack trace below, can anyone offer any assistance?
-Dan
Error Message info
RuntimeException thrown in operation replaceProcessDefinition
Caused by: cannot assign instance of fuego.resources.Msg to field fuego.lang.DefaultException.msg of type fuego.resources.Msg in instance of fuego.lang.DefaultRuntimeException$MyDefaultException
javax.management.RuntimeMBeanException: RuntimeException thrown in operation replaceProcessDefinition
     at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:195)
     at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:224)
     at javax.management.remote.rmi.RMIConnectionImpl_922_WLStub.invoke(Unknown Source)
     at weblogic.management.remote.common.RMIConnectionWrapper$15.run(ClientProviderBase.java:606)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.security.Security.runAs(Security.java:61)
     at weblogic.management.remote.common.RMIConnectionWrapper.invoke(ClientProviderBase.java:604)
     at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:972)
     at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:201)
     at $Proxy25.replaceProcessDefinition(Unknown Source)
     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:592)
     at fuego.mami.engine.jmx.EngineManagementJmxAdaptor$JmxEngineManagementProxy.invoke(EngineManagementJmxAdaptor.java:264)
     at $Proxy25.replaceProcessDefinition(Unknown Source)
     at fuego.mami.engine.jmx.EngineManagementJmxAdaptor.replaceProcessDefinition(EngineManagementJmxAdaptor.java:201)
     at fuego.mami.ProjectManager.notifyEngine(ProjectManager.java:1341)
     at fuego.mami.ProjectManager.notifyEngines(ProjectManager.java:642)
     at fuego.mami.DeploymentTopology.notifyEngines(DeploymentTopology.java:958)
     at fuego.webconsole.model.JSFDeploymentTopology.deployAction(JSFDeploymentTopology.java:766)
     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:592)
     at com.sun.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:126)
     at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:72)
     at javax.faces.component.UICommand.broadcast(UICommand.java:312)
     at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:267)
     at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:381)
     at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:75)
     at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
     at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:90)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:197)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
     at fuego.web.filter.CharsetFilter.doFilter(CharsetFilter.java:48)
     at fuego.web.filter.BaseFilter.doFilter(BaseFilter.java:63)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
     at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667)
     at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
     at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.ClassCastException: cannot assign instance of fuego.resources.Msg to field fuego.lang.DefaultException.msg of type fuego.resources.Msg in instance of fuego.lang.DefaultRuntimeException$MyDefaultException
     at java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(ObjectStreamClass.java:2004)
     at java.io.ObjectStreamClass.setObjFieldValues(ObjectStreamClass.java:1184)
     at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1914)
     at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
     at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
     at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
     at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
     at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
     at weblogic.rmi.extensions.server.CBVInputStream.readObjectInternal(CBVInputStream.java:71)
     at weblogic.rmi.extensions.server.CBVInputStream.readObject(CBVInputStream.java:65)
     at weblogic.rmi.internal.ServerRequest.unmarshalThrowable(ServerRequest.java:352)
     at weblogic.rmi.internal.ServerRequest.getThrowable(ServerRequest.java:62)
     at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:203)
     at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
     at javax.management.remote.rmi.RMIConnectionImpl_922_WLStub.invoke(Unknown Source)
     at weblogic.management.remote.common.RMIConnectionWrapper$15.run(ClientProviderBase.java:606)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.security.Security.runAs(Security.java:61)
     at weblogic.management.remote.common.RMIConnectionWrapper.invoke(ClientProviderBase.java:604)
     at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:972)
     at fuego.server.jmx.mami.ClusterAwareEngineManagement.invokeMethod(ClusterAwareEngineManagement.java:389)
     at fuego.server.jmx.mami.ClusterAwareEngineManagement.distributeVoidMethod(ClusterAwareEngineManagement.java:345)
     at fuego.server.jmx.mami.ClusterAwareEngineManagement.distributeVoidMethodWithStringParameter(ClusterAwareEngineManagement.java:276)
     at fuego.server.jmx.mami.ClusterAwareEngineManagement.replaceProcessDefinition(ClusterAwareEngineManagement.java:143)
     at fuego.server.jmx.mami.JmxEngineManagement.replaceProcessDefinition(JmxEngineManagement.java:200)
     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:585)
     at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:414)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
     at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:149)
     at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:149)
     at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:426)
     at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor$10.run(AuthenticatedSubjectInterceptor.java:377)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor.invoke(AuthenticatedSubjectInterceptor.java:375)
     at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:310)
     at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1410)
     at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
     at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1247)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1350)
     at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:784)
     at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:550)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:440)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:436)
     at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:58)
     at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:975)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Edited by: drkduncan on May 21, 2010 12:02 PM

Lightroom 2.7 cannot use RAW photos from a Canon 5D Mark III. You need at least Lightroom 4.1
Search for 0xc000007b here at the Adobe forums to find the answer.

Error when deploying war file into application server

I wrote a web service in java using RAD and managed to check it using a web service client with no errors.
However, after creating a war file and tried to deploy this into the Sun application server, the following can be seen at the application server console:
Deploying application in domain failed; Error while running ejbc -- Fatal Error from EJB Compiler -- jaxrpc compilation exception ; requested operation cannot be completed Error while running ejbc -- Fatal Error from EJB Compiler -- jaxrpc compilation exception
In the server.log file, the following appears:
loyment|_ThreadID=13;|DPL5035:Error while running ejbc
com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- j axrpc compilation exception
at com.sun.enterprise.webservice.codegen.JaxRpcRICodegen.accept(JaxRpcRICodegen.java:206 )
at com.sun.enterprise.deployment.WebBundleDescriptor.visit(WebBundleDescriptor.java:1101 )
at com.sun.enterprise.deployment.Application.visit(Application.java:1346)
at com.sun.enterprise.webservice.codegen.JaxRpcRICodegen.run(JaxRpcRICodegen.java:103)
at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:785)
at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:563)
at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployModule(EJBCompiler.java:42 7)
at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:213)
at com.sun.enterprise.deployment.backend.ModuleDeployer.runEJBC(ModuleDeployer.java:967)
at com.sun.enterprise.deployment.backend.WebModuleDeployer.deploy(WebModuleDeployer.java :193)
at com.sun.enterprise.deployment.backend.ModuleDeployer.doRequestFinish(ModuleDeployer.j ava:140)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:146)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.ja va:71)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentS ervice.java:633)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService. java:188)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService. java:520)
at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:143)
at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:172)
|#]
[#|2007-11-14T11:21:10.083+0930|INFO|sun-appserver-ee8.1_02|javax.enterprise.system.tools.deploy ment|_ThreadID=13;|Total Deployment Time: 14145 msec, Total EJB Compiler Module Time: 0 msec, Po rtion spent EJB Compiling: 0%|#]
[#|2007-11-14T11:21:10.116+0930|SEVERE|sun-appserver-ee8.1_02|javax.enterprise.system.tools.depl oyment|_ThreadID=13;|Exception occured in J2EEC Phase
com.sun.enterprise.deployment.backend.IASDeploymentException: Error while running ejbc -- Fatal Error from EJB Compiler -- jaxrpc compilation exception
at com.sun.enterprise.webservice.codegen.JaxRpcRICodegen.accept(JaxRpcRICodegen.java:206 )
at com.sun.enterprise.deployment.WebBundleDescriptor.visit(WebBundleDescriptor.java:1101 )
at com.sun.enterprise.deployment.Application.visit(Application.java:1346)
at com.sun.enterprise.webservice.codegen.JaxRpcRICodegen.run(JaxRpcRICodegen.java:103)
at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:785)
at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:563)
at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployModule(EJBCompiler.java:42 7)
at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:213)
at com.sun.enterprise.deployment.backend.ModuleDeployer.runEJBC(ModuleDeployer.java:967)
at com.sun.enterprise.deployment.backend.WebModuleDeployer.deploy(WebModuleDeployer.java :193)
at com.sun.enterprise.deployment.backend.ModuleDeployer.doRequestFinish(ModuleDeployer.j ava:140)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:146)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.ja va:71)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentS ervice.java:633)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService. java:188)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService. java:520)
at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:143)
at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:172)
|#]

I got a similar error deploying to Weblogic with JBuilder 6 and it proved to be
the Manifest.mf file inside war, which is very sensitive to CLASSPATH entry. Finally
I used the file generated by JBuilder and it worked ...
Stefan
Frank Sun <[email protected]> wrote:
Hi, this is Frank.
I have a war file and want to deploy it. but somehow I got java.lang.StringIndexOutOfBoundsException:
String index out of range: -1
error
Would anyone please help me?
This war file is able to be deplyed using Tomcat 4.0.3.
Please help.

Error when deploy the Planning SampAp application view

Similar Messages

Maybe you are looking for