Unable to Deploy MI SCA Files from Stack 22 (JSPM and SDM)

[former_member241142]

Hi,

I have been trying to deploy the following SCA Files which were part of Stack 22 (updating from Stack 19) and have consistantly been getting the below errors:

<br><br>

- SCA Packages<br>

<br>

NWMADMIN22_0-10003498 (Installed OK)<br>

<br>

Failed to Install:<br>

<br>

NWMCLIENT22_0-20000910.SCA<br>

NWMDRIVERS22_0-10003496.SCA<br>

NWMWDLAP22_0-10003497.SCA<br>

<br><br>

JDK Version: C:\j2sdk1.4.2_28-x64 (have also tried C:\j2sdk1.4.2_20-x64)

<br><br>

Log Entries:

<br><br>

0/11/15 15:04:33 - ***********************************************************<br>

10/11/15 15:04:33 - Start updating EAR file...<br>

10/11/15 15:04:33 - start-up mode is lazy<br>

10/11/15 15:04:34 - EAR file updated successfully for 470ms.<br>

10/11/15 15:04:34 - Start deploying ...<br>

10/11/15 15:04:34 - EAR file uploaded to server for 60ms.<br>

10/11/15 15:04:35 - ERROR: Not deployed. Deploy Service returned ERROR:

java.rmi.RemoteException: Cannot deploy application sap.com/tc_mobileconnector_ppc03_xsc_crm_1_1_2..

Reason: null; nested exception is:

com.sap.engine.services.deploy.container.DeploymentException

at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:569)

at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)

at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)

at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)

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:104)

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

Caused by: com.sap.engine.services.deploy.container.DeploymentException

at com.sap.ip.me.core.deployment.core.MobileArchiveContainerImpl.deploy(MobileArchiveContainerImpl.java:175)

at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:608)

at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:323)

at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:309)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)

at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3190)

at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:554)

... 10 more

For detailed information see the log file of the Deploy Service.

10/11/15 15:04:35 - ***********************************************************

Nov 15, 2010 3:04:35 PM Info: End of log messages of the target system.

Nov 15, 2010 3:04:35 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****

Nov 15, 2010 3:04:35 PM Error: Aborted: development component 'tc/mobile/connector_ppc03_xsc_crm_1_1_2'/'sap.com'/'SAP AG'/'7.0019.20090401143814.0000'/'0', grouped by software component 'NWMDRIVERS'/'sap.com'/'SAP AG'/'1000.7.00.22.0.20100607135315''/'0':

Caught exception during application deployment from SAP J2EE Engine's deploy service:

java.rmi.RemoteException: Cannot deploy application sap.com/tc_mobileconnector_ppc03_xsc_crm_1_1_2..

Reason: null; nested exception is:

com.sap.engine.services.deploy.container.DeploymentException

(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)

Nov 15, 2010 3:04:35 PM Info: Starting to save the repository

Nov 15, 2010 3:04:35 PM Info: Finished saving the repository for 370 ms.

Nov 15, 2010 3:04:36 PM Info: Starting: Initial deployment: Selected software component 'NWMDRIVERS'/'sap.com'/'SAP AG'/'1000.7.00.22.0.20100607135315''/'0' will be deployed.

Nov 15, 2010 3:04:36 PM Error: Aborted: software component 'NWMDRIVERS'/'sap.com'/'SAP AG'/'1000.7.00.22.0.20100607135315''/'0':

Failed deployment of SDAs:

development component 'tc/mobile/connector_ppc03_xsc_crm_1_1_2'/'sap.com'/'SAP AG'/'7.0019.20090401143814.0000'/'0' : aborted

Please, look at error logs above for more information!

Nov 15, 2010 3:04:36 PM Info: Starting to save the repository

Nov 15, 2010 3:04:43 PM Info: Finished saving the repository for 6569 ms.

Nov 15, 2010 3:04:43 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.

Nov 15, 2010 3:04:43 PM Error: -

---

At least one of the Deployments failed -

---

Nov 15, 2010 3:05:09 PM Info: Summarizing the deployment results:

Nov 15, 2010 3:05:09 PM Error: Aborted: E:\usr\sap\trans\EPS\in\NWMDRIVERS22_0-10003496.SCA

Nov 15, 2010 3:05:09 PM Error: Processing error. Return code: 4

<br><br>

The errror is similar regardless of which SCA file I try to deploy... I have also tried via the Mobile Administrator, however that appears to just call SDM sosame end result. I have also tried the following:<br><br>

sdm jstartup "mode=standalone"<br>

sdm systemcomponentstate "mode=sync"<br>

sdm jstartup "mode=integrated"<br><br>

With no success, as you can see in the log there is little detail on the error, anyone have any suggestions? Thanks in Advance.<br><br>

Edited by: Davey G on Nov 15, 2010 9:05 AM - Edit Due to Bad Formatting

<BR><BR>

-

---

<BR>

<BR><BR>

sap.com LM-PORTAL 7.00 SP22 (1000.7.00.22.0.20100614103116) SAP AG MAIN_APL70P22_D 20101107082551 <BR>

sap.com LM-TOOLS 7.00 SP22 (1000.7.00.22.0.20100614113124) SAP AG MAIN_APL70P22_D 20101107072744 <BR>

sap.com NET-PDK 7.00 SP22 (1000.7.00.22.0.20100604045100) SAP AG SAP AG 20101107080850 <BR>

sap.com NWMADMIN 7.00 SP22 (1000.7.00.22.0.20100614104706) SAP AG MAIN_APL70P22_D 20101108144654 <BR>

sap.com RTC 7.00 SP22 (1000.7.00.22.0.20100604113900) SAP AG SAP AG 20101107080913 <BR>

sap.com RTC-STREAM 7.00 SP22 (1000.7.00.22.0.20100604113900) SAP AG SAP AG 20101108140407 <BR>

sap.com SAP-EU 7.00 SP22 (1000.7.00.22.0.20100614103401) SAP AG MAIN_APL70P22_D 20101108113243 <BR><BR>

Just a subset, but you can see NWADMIN updated fine... as did all the other .SCA packages.<BR>

<BR>

Kernel Info:<BR><BR>

Kernel release 700<BR>

Compilation NT 5.2 3790 Servic<BR>

Sup.Pkg lvl. 267<BR>

ABAP Load 1563<BR>

CUA load 30<BR>

Mode opt<BR>

Rsyn file<BR><BR>

DB info:<BR><BR>

DB client lib. SQL_Server_8.00<BR>

DB releases MSSQL 7.00.699 or<BR>

DBSL version 700.08<BR>

DBSL Patch Level 267<BR>

<BR>

Edited by: Davey G on Nov 15, 2010 9:08 AM - Added Kernel Info

[Former Member · Accepted solution]

Hi Davey,

Can you check if your file system has enough space? Following is a note you may want to take a look:

[ Note 891895 - JSPM: required disk space|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=891895]

I assume you have tried JSPM as well as SDM both, in that case, also see if you have any antivirus software runtime scan active in parallel, if so you can disable it and try again.

Best Regards,

Shival

[Former Member · Accepted solution]

i've similar error, did you manage to find a solution ?

[former_member241142]

As per my last comments.

[former_member215291]

Hi Davey,

I'm also having the same problem.How did u resolve it? Please help.

Thanking You,

Sumeesh

Edited by: Sumeesh Chandran on Jan 3, 2011 11:33 AM

[former_member241142]

Unfortunately still a work in progress... it's on my 'low priority' list as its not business critical functionality but I may get back to it again in the next couple of days. If you have any luck, please let me know.

[Former Member]

Hey Guys,

Did you ever found the solution for that error. Please update the forum to help others like me.

Thank you,

[former_member241142]

I still have an open issue with SAP about this, it's not high priority... the last bit of advise i received from them was this:

<br><br>

1. Open Visual Admin( by executing GO.bat file).<br>

2. Expand server node > expand service node.<br>

3. Select Configuration Adaptor.<br>

4. Select Mobile folder from RHS pane.<br>

5. Expand folder Mobile.<br>

6. Select Addon's folder.<br>

7. In toolbar, there will be a change button, select the same.<br>

8. Right click on Addon's and say delete.<br>

9. Now deploy the same SCA file.<br>

<br><br>

This is what mine looked like after removing the above (notice the remaining entries):<br>

<br>

http://img257.imageshack.us/img257/6276/vaconfigadapterscreensh.jpg

<br><br>

Which didn't help and my OSS issue has been reassigned to their upgrades area, when I hear more and/or get a resolution I will post it, I did notice some other folders in the same area as above and was tempted to delete, but was awaiting confirmation from SAP.

Edited by: Davey G on Jan 19, 2011 7:37 AM

Edited by: Davey G on Jan 19, 2011 7:38 AM - Added screenshot

[former_member241142]

Just an update... this is still ongoing through OSS and SAP Support... it's currently going through a 'file may be corrupt' stage, but I suspect thati s highly unlikely given I've tried multiple versions of NWCLient, etc... and my file sizes match what is on the SAP marketplace exactly.

I think I'll just have a crack at removing some of the other mobility entries and report back later...

[former_member241142]

Righto, the latest is this sap note:

Note 1548353 - Depoyment of the component NWMCLIENT fails during upgrade

Its a relatively new addition, I am yet to try it, but Liam who's been helping me via OSS has put me on to it, so maybe a resolution in sight, yay.

[former_member241142]

The note above does indeed resolve my issue, I ended up undeploying NWADMIN23 and redeploying NWADMIN22 Patch level2 at the request of SAP, all the other MI components then deployed as expected. It seems the patch for NWADMIN23 isn't yet ready.

Anyway, glad to close this one, thanks for all the suggestions to date.

[desiree_matas]

Hello Davey,

Is any error in the deploy log? Check it and paste here the errors you find.

Regards,

Désiré