Deployment Error for TS 3.5

I am trying to get the base deployment for the testStand engine and the base testStand system. In my deployment I am including the component/user directory. I have mass compiled it to LV 8.0. I am getting the following error with lots of other warning.
Error: The following file(s) could not be copied:
C:\Program Files\National Instruments\TestStand 3.5\Components\User\RuntimeServers\LabVIEW\Server.llb\TestStand Server - Not a Window Refnum
C:\Program Files\National Instruments\TestStand 3.5\Components\User\RuntimeServers\LabVIEW\Server.llb\TestStand Server - Window Refnum
Thank you,
Hiren
Hiren Patel

Howdy Hiran -
If you have not intentionally modified the LabVIEW runtime server, I would recommend copying the original server from your "NI" to your "User" directoy. Overwrite the C:\Program Files\National Instruments\TestStand 3.5\Components\User\RuntimeServers\LabVIEW folder with C:\Program Files\National Instruments\TestStand 3.5\Components\NI\RuntimeServers\LabVIEW.
Let me know if you still see the error after overwritting the runtime server with the original.
Andrew W || Applications Engineer
National Instruments

Similar Messages

EJB deployment error for Weblogic server 9.2 mp4

Hi,
While trying to deploy a small EJB jar file which uses EJB 2.1 CMP beans with relationships, getting the following error from Weblogic server 9.2 MP4:
=================================================================================================
<Error> <EJB> <VinodThinkPad> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320143988333> <BEA-012036> <Compiling generated EJB classes produced the following Java compiler error message:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
>
####<Nov 1, 2011 4:09:48 PM IST> <Error> <Deployer> <VinodThinkPad> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320143988380> <BEA-149265> <Failure occured in the execution of deployment request with ID '1320143984947' for task '1'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(EJBTest)
Unable to deploy EJB: EJBTest.jar from EJBTest.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
     at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
     at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
     at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:432)
     at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
     at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
weblogic.application.ModuleException: Exception preparing module: EJBModule(EJBTest)
Unable to deploy EJB: EJBTest.jar from EJBTest.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
     at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
     at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
     at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:432)
     at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
     at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:382)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.io.IOException: Compiler failed executable.exec:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
     at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
     at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
     at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:432)
     at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
     at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
=================================================================================================
While I'm able to deploy without the CMP 1-1 relationship, the moment I introduce the 1-1 relationship, I get this error. Database used is Oracle 10g XE.
I have been battling this error for more than a day now. Kindly help me fix this.
Thanks in advance!
Regards,
Vinod

Hi,
I was able to figure out the root cause. I was using the primitive data type "int" for primary key and foreign key for one of the beans in the relationship. After I changed it to "Integer" wrapper type, the issue got resolved.
-Vinod

Deploy Error for Web Dynpro

I have got the error message on Deploying the project of web dynpro, they are:
Deployment aborted
2006年7月6日 上午10:21:13 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[002]Deployment aborted
Settings
SDM host : fly-2012
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/Family/LOCALS1/Temp/temp25891TutWD_FlightList_Init.ear
Result
=> deployment aborted : file:/C:/DOCUME1/Family/LOCALS1/Temp/temp25891TutWD_FlightList_Init.ear
Aborted: development component 'TutWD_FlightList_Init'/'local'/'LOKAL'/'0.2006.07.06.10.17.59':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
Additional log information about the deployment
2006年7月6日 上午10:21:13 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
[002]Additional log information about the deployment
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7186 - 630]/>
<!NAME[C:\usr\sap\J2E\JC00\SDM\program\log\sdmcl20060706022108.log]/>
<!PATTERN[sdmcl20060706022108.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[MS950]/>
<!LOGHEADER[END]/>
Jul 6, 2006 10:21:08 AM Info: -
Starting deployment -
Jul 6, 2006 10:21:08 AM Info: Error handling strategy: OnErrorStop
Jul 6, 2006 10:21:08 AM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Jul 6, 2006 10:21:08 AM Info: Update strategy: UpdateAllVersions
Jul 6, 2006 10:21:08 AM Info: Starting deployment prerequisites:
Jul 6, 2006 10:21:08 AM Info: Loading selected archives...
Jul 6, 2006 10:21:08 AM Info: Loading archive 'C:\usr\sap\J2E\JC00\SDM\program\temp\temp25891TutWD_FlightList_Init.ear'
Jul 6, 2006 10:21:09 AM Info: Selected archives successfully loaded.
Jul 6, 2006 10:21:09 AM Info: Actions per selected component:
Jul 6, 2006 10:21:09 AM Info: Initial deployment: Selected development component 'TutWD_FlightList_Init'/'local'/'LOKAL'/'0.2006.07.06.10.17.59' will be deployed.
Jul 6, 2006 10:21:10 AM Info: Ending deployment prerequisites. All items are correct.
Jul 6, 2006 10:21:10 AM Info: Saved current Engine state.
Jul 6, 2006 10:21:10 AM Info: Starting: Initial deployment: Selected development component 'TutWD_FlightList_Init'/'local'/'LOKAL'/'0.2006.07.06.10.17.59' will be deployed.
Jul 6, 2006 10:21:10 AM Info: SDA to be deployed: C:\usr\sap\J2E\JC00\SDM\root\origin\local\TutWD_FlightList_Init\LOKAL\0.2006.07.06.10.17.59\temp25891TutWD_FlightList_Init.ear
Jul 6, 2006 10:21:10 AM Info: Software type of SDA: J2EE
Jul 6, 2006 10:21:10 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 6, 2006 10:21:12 AM Info: Begin of log messages of the target system:
06/07/06 10:21:10 - ***********************************************************
06/07/06 10:21:11 - Start updating EAR file...
06/07/06 10:21:11 - start-up mode is lazy
06/07/06 10:21:11 - EAR file updated successfully for 811ms.
06/07/06 10:21:11 - Start deploying ...
06/07/06 10:21:12 - EAR file uploaded to server for 120ms.
06/07/06 10:21:12 - ERROR: Not deployed. Deploy Service returned ERROR:
                     java.rmi.RemoteException: Only Administrators have the right to perform this operation.
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:526)
                          at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java: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)
                     For detailed information see the log file of the Deploy Service.
06/07/06 10:21:12 - ***********************************************************
Jul 6, 2006 10:21:12 AM Info: End of log messages of the target system.
Jul 6, 2006 10:21:12 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 6, 2006 10:21:12 AM Error: Aborted: development component 'TutWD_FlightList_Init'/'local'/'LOKAL'/'0.2006.07.06.10.17.59':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Jul 6, 2006 10:21:13 AM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Jul 6, 2006 10:21:13 AM Error: -
At least one of the Deployments failed -

The tools I using to Deploy is
SAP NetWeaver Developer Studio. and I'm follow the tutorial from it, I have enter the sdm password and operate the delopyment, but when it create the ear file, then the error have occur and catch the error about:
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
I have try to login as j2eadm to operate the deployment, but the error message is same.
as you say, the user "SDM" or "J2EE_ADMIN" user account I haven't find in my windows XP.
and one more question, does the project need to deploy success then the web page "Web Dynpro Content Administrator" could find the project?
lastly, I have try to login to SDM by using the SAP given program C:\usr\sap\J2E\JC00\SDM\program\RemoteGui for testing, It was success. and does the default SDM account could change the permission by different password?

Deployment error for Web Dynpro application

Hello, I have developed a new Web Dynpro Welcome application in my local system, which is my laptop. I have both the NW Dev Studio and the app server on my laptop.
When I try to deploy and run the application I get the below error. As far I am concerned I have logged in as j2eadm user and trying to deploy.
Appreciate your help to resolve the error
Sep 23, 2007 6:26:57 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[002]Deployment aborted
Settings
SDM host : Natasha
SDM port : 50018
URL to deploy : file:/C:/WINDOWS/TEMP/temp6475Welcome.ear
Result
=> deployment aborted : file:/C:/WINDOWS/TEMP/temp6475Welcome.ear
Aborted: development component 'Welcome'/'local'/'LOKAL'/'0.2007.09.23.18.26.49':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted

As per the procedure given in 3rd point I have changed the j2eadm password but it gives me the below error when I try to redeploy and run
Result
=> deployment aborted : file:/C:/WINDOWS/TEMP/temp26493Welcome.ear
Aborted: development component 'Welcome'/'local'/'LOKAL'/'0.2007.09.25.22.11.45':
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: [Natasha] with user name: [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: Authentication did not succeed.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
Deployment exception : The deployment of at least one item aborted

NWDS deploy error for service interface

Hi Friends,
I am deploying simple process instance via NWDS.
The process instance contains "intermediate message event" , which is waiting for cXML - order request message.
The service interface -wsdl in SAP PI ,which is configured for above "intermediate message event" is having below line :
<xsd:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/>
I am getting below error while deploying above instance:
Description:
1. JAR entry META-INF/wsdl/mtsapcom2Forderreq2Freceiverespmsg/http://www.w3.org/2001/xml.xsd not found in D:\usr\sap\DI3\J00\j2ee\cluster\server1\temp\deploy\mt.sap.com~orderreq.sda1403025008814\mt.sap.com~orderreq.wsar
How to resolve this reference in service interface?
Also, external defination having cXML.xsd is also having some of the field types are red, like xml:lang.
Please suggest your views on the same.
--Divyesh

Did you solved this issue?
Thanks in advance.

Web service deployment error - CE 7.2(CAF)

I am getting deployment error for CE 7.2 CAF application.
it was working fine. Suddenly with out any changes in the code or the web service, I am not able deploy the application.
if I remove the modeled service , it is successfully deployed. But modeled service is required to expose the service for other applications.
any one have suggestions? does this is a problem from J2EE engine? any authentication problems??
its a nested error:
com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
Reason: ASJ.dpl_dc.001085 An error occurred while deploying the deployment item [<projectname>~ear].
; nested exception is:
            com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [<projectname>~ear]
sdu file path: [/usr/sap/CED/J00/j2ee/cluster/server0/temp/tc~bl~deploy_controller/archives/582/<projectname>ear.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it.
            at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:891)
            at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
            at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:104)
            at com.sap.ide.tools.services.dc.EngineDcDeployService.deployFiles(EngineDcDeployService.java:178)
            at com.sap.ide.tools.services.dc.EngineDcDeployService.deploy(EngineDcDeployService.java:92)
            at com.sap.ide.dii05.ui.internal.actions.dc.DcDeployAction$3.run(DcDeployAction.java:236)
            at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Resolved myself : delete the project in webAS using deployment perspective and delete the project in NWDS and recreate the same project and deploy with WSDL.

Web service deployment error -

Hi all,
Only recently I've been encountering deployment error for my EAR that contains a webservice. I deployed the EAR file via SAP Netweaver IDE. Prior to that, there wasn't any issue while performing deployment but lately the error below is persistent and I had to repackage my webservice to a different EAR file. But after a few days, the same error occurs with the newly deployed EAR file.
Result
=> deployment aborted : file:/C:/DOCUME~1/KOK~1.CHA/LOCALS~1/Temp/temp48934WellsPortalRptEar.ear
Aborted: development component 'WellsPortalRptEar'/'sap.com'/'localhost'/'2005.11.14.16.41.46':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Already started operation with application sap.com/WellsPortalRptEar in the cluster. No other operation with this application is allowed at the moment.. Reason: Cannot lock [2005111121371371500000amsdc2-s-1250................1085450, DEPLOY_LOCK_AREA, sap.com/WellsPortalRptEar, X]; it is in use by the same owner.; nested exception is: com.sap.engine.frame.core.locking.LockException: Cannot lock [2005111121371371500000amsdc2-s-1250................1085450, DEPLOY_LOCK_AREA, sap.com/WellsPortalRptEar, X]; it is in use by the same owner.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
I've restarted the J2EE Engine but the error will not go away. I've also tried to undeploy the EAR file manually via SDM but the same error occured. Is there any way I can redeploy my webservice without hitting this error?
Your insights are greatly appreciated.
Thanks, regards.

Hi Kok
Check this link, it will solve your problem
http://help.sap.com/saphelp_nw04/helpdata/de/24/3733418bb16e24e10000000a155106/content.htm
please award points and close the thread.
Sameer

Error while deploying ECO for Java

Hi
I got this error while deploying ECO for JAVA
I chose manual deplyoment
I specified the location of the jar file, app name, display name
and left the rest of the options unticked
after i clicked on the apply button
OAS returns me this error message:
Error!: 1
which is not very helpful
thanks
null

HI..
Did you check with the note that has been mentioned in the log file??
Thanks
Gopal
Message was edited by:
Gopalakrishnan

Error at the time of deploying App for SP 2013

When I try to deploy any App created using VS 2012, giving error below. Please provide some help to resolve it.
Build started: Project: FleetManagementApp, Configuration: Debug Any CPU ------
------ Deploy started: Project: FleetManagementApp, Configuration: Debug Any CPU ------
Active Deployment Configuration: Deploy App for SharePoint
Skipping deployment step because a pre-deployment command is not specified.
Skipping the uninstall step because the app for SharePoint is not installed on the server.
Install app for SharePoint:
Uploading the app for SharePoint...
Error occurred in deployment step 'Install app for SharePoint': We're sorry, we weren't able to complete the operation, please try again in a few minutes.
If you see this message repeatedly, contact your administrator.
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========

Hi,
Please check the link below, it about the simialr issue.
https://social.msdn.microsoft.com/Forums/vstudio/en-US/c8eb6c92-e1b2-45a9-840e-c782bdc933ec/error-occurred-in-deployment-step-install-app-for-sharepoint-were-sorry-we-werent-able-to?forum=sharepointdevelopment
Best Regards
Dennis Guo
TechNet Community Support

Deployment error in 9.0.3 for app with local interface

While attempting to port an EJB-application from jboss to oracle, I have encountered a deployment error in 9.0.3 9iASR2 which I cannot decipher. The same ear-file is successfully deployed on the 9.0.3. OC4J standalone version (both on a machine running winXP)
I get a "syntax error in source" when I attempt the deployment and all my local-interface class-files end up on the j2ee_home root, i.e. <oracle-home>/j2ee/home/.
Am I too early using local interface on version 9.0.3, is my packaging messed up or should I look for my bugs in some missed logfile?
BTW: where do I find deployment stack traces for this version of 9iAS?
Dag

Hi,
you can find deployment stack traces in the following location \ORACLE\806\opmn\logs. i think this might help u.
I am also facing a problem like com.evermind.compiler.CompilationException: Syntax error in source,did u know cause for this.
Thanks and Regards,
Bala

Deployment error: null. See ide log for details

When i succesfully compiled an application which has a conver in it, the Deployment progress monitor gives the error:
Deployment error: null. See ide log for details
And doesn't display my app.
Does anyone knows what this means?

The ide log file (C:\Documents and Settings\<username>\.Creator\EA\system\ide.log) is located here: "Help" menu -> "Java Studio Creator Log file"
Don't hesitate pasting it into this forum topic.
-Alexis

WD app Deployment Error - Where can we find J2ee log file for linux install

Hi,
I have a problem with deploying a web dynpro application. There are no errors before deployment but when I deploy the application, I get a deployment error with the following description.
I tried to view the trace or log file but we have SAP installed on a linux OS and I do not know where can we see the log or trace file. Please help.
Version:
SAP NW 2004s SP15
NWDS 7.0
xRPM 4.5
Error Description:
May 14, 2008 12:49:50 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager)
[Thread[Deploy Thread,5,main]] ERROR:
[008]Deployment aborted
Settings
SDM host : BS307
SDM port : 50718
URL to deploy : file:/C:/DOCUME1/SMULLA1/LOCALS~1/Temp/2/temp20045SempraDemo4.5.ear
Result
=> deployment aborted : file:/C:/DOCUME1/SMULLA1/LOCALS~1/Temp/2/temp20045SempraDemo4.5.ear
Aborted: development component 'SempraDemo4.5'/'local'/'LOKAL'/'0.2008.05.14.00.49.36'/'0':Caught exception during application deployment from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Cannot deploy application local/SempraDemo4.5.. Reason: Clusterwide exception: Failed to deploy application local/SempraDemo4.5. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application local/SempraDemo4.5. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine? (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
Edited by: Subramanya Srinivas Mullapudi on May 14, 2008 8:34 AM

Hi Reza,
Hope you are doing good.
You can set the trace level in the SAP/Java Gui dynamically :
Call transaction SMICM
Choose the menu Goto → Trace Level → Set
In the pop-up window, set the desired level (0,1,2,3)
To switch on an /nSMICM or ICM HTTP trace via command line you should go to
usr\sap\<SID>\<instance_number>\exe directory and run the icmon program with the following command:
icmon◦◦pf=\usr\sap\<SID>\SYS\profile\<SID>_<instance_name>_<HOST>
where you fill in the SID, instance name and host corresponding to your system.
The icmon program is interactive and to increase trace level you must write
"+" and pres enter.To quit you must write "q" and press enter.
The trace will be written◦to the following file: usr\sap\<SID>\<instance_number>\work\dev_icm
Thank you!
Kind Regards,
Hemanth
SAP AGS

OMB05602: An unknown Deployment error has occured for Object Type Deploymen

I was deploying a process_flow package here in named "PF_LOAD", then the following error occured.
OMB05602: An unknown Deployment error has occured for Object Type DeploymentContextImpl.generate WBGeneratedObject[] is null or length 0 for PF_LOAD.
Does anyone know what this error means or what possibly caused it?
So

Hi David
OWB version 10.2.0.3.0
This is what I cought from the log when tried to deploy the process flow via OMB+
OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN_PROCESS_FLOWS'
Action plan DEPLOY_PLAN_PROCESS_FLOWS created.
OMBALTER DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN_PROCESS_FLOWS' ADD ACTION 'PF_LOAD_PROCESS_FLOW_PACKAGE_DEPLOY' SET PROPERTIES (OPERATION) VALUES ('REPLACE') SET REFERENCE PROCESS_FLOW_PACKAGE 'PF_LOAD'
Action plan DEPLOY_PLAN_PROCESS_FLOWS altered.
OMBDEPLOY DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN_PROCESS_FLOWS'
OMB05602: An unknown Deployment error has occured for Object Type DeploymentContextImpl.generate WBGeneratedObject[] is null or length 0 for PF_LOAD.
When I viewed via the control center jobs detail window, it is not even logged there.
Cheers
So

MYSQL Plug-in for Oracle grid deployment errors

hello,
having problems deploying the mysql plug-in. see error below....any ideas?
this is the error in the emom.log
2009-06-05 14:36:25,975 [EMUI_14_36_25_/console/emx/deploy] ERROR em.emx exists.743 - XXXXXX sql = select mmp.target_type, mmp.mp_version, mmp.functional_description, mmp.requirements_description, mmp.hwm_status from mgmt_management_plugins mmp WHERE (mmp.target_type = ? AND mmp.mp_version = ?) AND mmp.hwm_status != ?
2009-06-05 14:36:25,980 [EMUI_14_36_25_/console/emx/deploy] ERROR em.emx exists.744 - XXXXXX name = mysql
2009-06-05 14:36:25,983 [EMUI_14_36_25_/console/emx/deploy] ERROR em.emx exists.745 - XXXXXX version = 1.1
2009-06-05 14:36:49,580 [Thread-278] ERROR em.emx exists.743 - XXXXXX sql = select mmp.target_type, mmp.mp_version, mmp.functional_description, mmp.requirements_description, mmp.hwm_status from mgmt_management_plugins mmp WHERE (mmp.target_type = ? AND mmp.mp_version = ?) AND mmp.hwm_status != ?
2009-06-05 14:36:49,590 [Thread-278] ERROR em.emx exists.744 - XXXXXX name = mysql
2009-06-05 14:36:49,592 [Thread-278] ERROR em.emx exists.745 - XXXXXX version = 1.1
2009-06-05 14:36:49,677 [ManagementPluginWorker(mysql:1.1,speck.lhsc.on.ca:3872)] ERROR em.emx exists.743 - XXXXXX sql = select mmp.target_type, mmp.mp_version, mmp.functional_description, mmp.requirements_description, mmp.hwm_status from mgmt_management_plugins mmp WHERE (mmp.target_type = ? AND mmp.mp_version = ?) AND mmp.hwm_status != ?
2009-06-05 14:36:49,680 [ManagementPluginWorker(mysql:1.1,speck.lhsc.on.ca:3872)] ERROR em.emx exists.744 - XXXXXX name = mysql
2009-06-05 14:36:49,681 [ManagementPluginWorker(mysql:1.1,speck.lhsc.on.ca:3872)] ERROR em.emx exists.745 - XXXXXX version = 1.1
2009-06-05 14:36:51,636 [ManagementPluginWorker(mysql:1.1,speck.lhsc.on.ca:3872)] ERROR em.emx runOperation.319 - RemoteOperationException: ERROR: NMO not setuid-root (Unix-only)
java.io.IOException: RemoteOperationException: ERROR: NMO not setuid-root (Unix-only)
at oracle.sysman.emSDK.emd.comm.RemoteOperationInputStream.read(RemoteOperationInputStream.java:172)
at oracle.sysman.emx.Util.pipe(Util.java:535)
at oracle.sysman.emx.Util.pipeAndClose(Util.java:451)
at oracle.sysman.emx.Util.pipeAndClose(Util.java:423)
at oracle.sysman.emx.AgentFileHandler.runRemoteCommand(AgentFileHandler.java:563)
at oracle.sysman.emx.AgentFileHandler.undeployFiles(AgentFileHandler.java:459)
at oracle.sysman.emx.AgentFileHandler.runOperation(AgentFileHandler.java:256)
at oracle.sysman.emx.AgentFileHandler.undeploy(AgentFileHandler.java:123)
at oracle.sysman.emx.MPHandler.runOperation(MPHandler.java:165)
at oracle.sysman.emx.MPHandler.undeploy(MPHandler.java:118)
at oracle.sysman.emx.AgentDeployWorker.deployToAgent(AgentDeployWorker.java:121)
at oracle.sysman.emx.AgentDeployWorker.run(AgentDeployWorker.java:78)
at oracle.sysman.util.threadPoolManager.WorkerThread.run(Worker.java:260)
2009-06-05 14:36:51,639 [ManagementPluginWorker(mysql:1.1,speck.lhsc.on.ca:3872)] ERROR em.emx exists.743 - XXXXXX sql = select mmp.target_type, mmp.mp_version, mmp.functional_description, mmp.requirements_description, mmp.hwm_status from mgmt_management_plugins mmp WHERE (mmp.target_type = ? AND mmp.mp_version = ?) AND mmp.hwm_status != ?
2009-06-05 14:36:51,641 [ManagementPluginWorker(mysql:1.1,speck.lhsc.on.ca:3872)] ERROR em.emx exists.744 - XXXXXX name = mysql
2009-06-05 14:36:51,643 [ManagementPluginWorker(mysql:1.1,speck.lhsc.on.ca:3872)] ERROR em.emx exists.745 - XXXXXX version = 1.1
2009-06-05 14:36:51,667 [ManagementPluginWorker(mysql:1.1,speck.lhsc.on.ca:3872)] ERROR threadPoolManager.WorkerThread run.281 - Exception message: null
java.lang.Error
at oracle.sysman.emx.AgentDeployWorker.run(AgentDeployWorker.java:82)
at oracle.sysman.util.threadPoolManager.WorkerThread.run(Worker.java:260)
2009-06-05 14:36:51,669 [Thread-279] ERROR em.emx workerDied.250 - java.lang.Error
java.lang.Error
at oracle.sysman.emx.AgentDeployWorker.run(AgentDeployWorker.java:82)
at oracle.sysman.util.threadPoolManager.WorkerThread.run(Worker.java:260)

See if this helps.
After Installing DB Control, Getting RemoteOperationException.
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=824947.1

500 Internal Server error for WD applications

Dear All
I have a very strange situation and I don´t have any idea of what to do.
Basis took the backend R/3 system down for some reasons and made it up again after some time. But now they have locked all users in our backend R/3 system as Basis is performing some task on the server.
This has resulted in all web dynpro applications that are using RFC's throwing 500 Internal server error.
All other web dynpro applications that are not dependent on R3 system are working fine.
We also have restarted the EP server as we deployed one WD application.
I'm not sure how the situation was before the restart of EP server.
In NWA i can see many error for ACCESS.ERROR: Authorization check for caller assignment to J2EE security role service.jms.default.authorization : administrators referencing J2EE security role .
Also
application Processing HTTP request to servlet finished with error. The error is: com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type is.eimskip.keywordsearchmodel.types.Zotkey could not be loaded: com.sap.dictionary.runtime.DdException: failed to create provider: User is locked. Please notify the person responsible
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:449)
at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:387)
at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:416)
at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:83)
at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:125)
at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:121)
at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:215)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:449)
at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:387)
at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:416)
at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:83)
at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:125)
at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:121)
at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:215)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:748)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:283)
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.doGet(DispatcherServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
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:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.dictionary.runtime.DdException: failed to create provider: User is locked. Please notify the person responsible
at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:254)
at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
... 61 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedConstructorAccessor525.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:229)
... 68 more
Caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: User is locked. Please notify the person responsible
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:455)
at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1015)
at com.sap.mw.jco.JCO$Client.connect(JCO.java:3255)
at com.sap.dictionary.runtime.mdi.DataProvider.(DataProvider.java:123)
... 72 more
I believe that error will get resolved once the users are unlocked in R/3 system.
But the stituation is, we will get the system back on monday morning and I'll have no time to do anything as the business will be back in 1 hr when we get the system back.
Can you please help me to identify the tasks that I can perform and be sure that all will be normal on Monday (and I'll still be in job.)
Request your help and support.
Thanks
Vineet
Edited by: vineet vikram on Apr 19, 2008 12:41 PM

Hi vineet,
Check the following things:
(1) Specify the user names in Capital letters and try. This will help you. (this could be the problem)
(2) Test the RFC destination using the tCode SM59 and try to remote login from there.
(3) If the user is locked, you can unlock using the tCode SU01.
Regards
Vinod V

Deployment Error for TS 3.5

Similar Messages

Maybe you are looking for