Error duing SDm deplyment of DICMS16P_3-10003499.SCA

[Former Member]

Hi,

I am getting the above error while deploying DICMS16P_3-10003499.SCA in Pi 7.0 system OS:HP Unix.. Here is the sdm logfile info

Sep 28, 2010 12:07:49... Info:

Sep 28, 2010 12:07:49... Info: ============================================

Sep 28, 2010 12:07:49... Info: = Starting to execute command 'server' =

Sep 28, 2010 12:07:49... Info: ============================================

Sep 28, 2010 12:07:49... Info: Starting SDM - Software Deployment Manager...

Sep 28, 2010 12:07:50... Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0016.2008042316153

6.0000

Sep 28, 2010 12:07:52... Info: SDM operation mode successfully set to: Integrate

d

Sep 28, 2010 12:07:53... Info: JStartupFramework is requesting to start the SDM

Server.

Sep 28, 2010 12:07:53... Info: Start the SDM Server integrated in the JStartupFr

amework.

Sep 28, 2010 12:07:53... Info: Initializing Network Manager (50117)

Sep 28, 2010 12:07:53... Info: Starting SDM Server listening on port 50118

"sdmlog20100928.log" [Read only] 7159 lines, 720023 characters

at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.traver

sThrough(PackageBuilder.java:289)

at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.traver

sThrough(PackageBuilder.java:289)

at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.traver

sThrough(PackageBuilder.java:289)

at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.traver

sThrough(PackageBuilder.java:289)

at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.traver

sThrough(PackageBuilder.java:274)

at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.compil

at java.security.AccessController.doPrivileged(Native Me

thod)

at com.sap.engine.core.thread.impl3.SingleThread.execute

(SingleThread.java:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(Sin

gleThread.java:172)

Caused by: com.sap.engine.interfaces.webservices.server.dep

loy.WSDeploymentException: Webservices common deployment exception! The reason i

s: Error occurred generating ws client proxy files. Package error. . Additional

info: at com.sap.engine.services.webservices.server.deploy.wsc lient.WSClientProxyGenerator.generateAndPackageProxyFiles(WSClientProxyGenerator .java:61) at com.sap.engine.services.webservices.server.deploy.wsc lient.WSClientsDeployGenerator.generateSingleWSClientDeployFiles(WSClientsDeploy Generator.java:188) ... 25 more Caused by: com.sap.engine.interfaces.webservices.server.dep loy.WSDeploymentException: Webservices common deployment exception! The reason i s: Error occurred trying to compile ws client proxy files. Compilation error. . Additional info:

at com.sap.engine.services.webservices.server.deploy.wsc

lient.WSClientProxyGenerator.compileWSClientProxyFile(WSClientProxyGenerator.jav

a:256)

at com.sap.engine.services.webservices.server.deploy.wsc

Oct 19, 2010 2:24:33 PM Info: No action: Selected development component 'tc/SL/

CMS/cleanuptool'/'sap.com'/'MAIN_APL70VAL_C'/'1552404'/'4' will not update curre

ntly deployed development component 'tc/SL/CMS/cleanuptool'/'sap.com'/'MAIN_APL7

0VAL_C'/'1552404'/'3'.

Oct 19, 2010 2:27:58 PM Info: Saved current Engine state.

Oct 19, 2010 2:27:59 PM Info: Starting: Initial deployment: Selected developmen

t component 'tc/SL/CMS/cvers/proxy'/'sap.com'/'MAIN_APL70VAL_C'/'1496430'/'4' wi

ll be deployed.

Oct 19, 2010 2:27:59 PM Info: SDA to be deployed: /usr/sap/QX1/DVEBMGS01/SDM/ro

ot/origin/sap.com/tc/SL/CMS/cvers/proxy/MAIN_APL70VAL_C/4/1496430/tc_SLCMS~cver

s~proxy.sda

Oct 19, 2010 2:27:59 PM Info: Software type of SDA: J2EE

Oct 19, 2010 2:27:59 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE A

pplication) *****

Oct 19, 2010 2:28:01 PM Info: Begin of log messages of the target system:

10/10/19 14:27:59 - ***********************************************************

10/10/19 14:28:00 - Start updating EAR file...

10/10/19 14:28:00 - start-up mode is lazy

10/10/19 14:28:00 - EAR file updated successfully for 16ms.

10/10/19 14:28:00 - Start deploying ...

10/10/19 14:28:00 - EAR file uploaded to server for 279ms.

10/10/19 14:28:01 - ERROR: Not deployed. Deploy Service returned ERROR:

10/10/19 14:28:00 - EAR file updated successfully for 16ms.

10/10/19 14:28:00 - Start deploying ...

10/10/19 14:28:00 - EAR file uploaded to server for 279ms.

10/10/19 14:28:01 - ERROR: Not deployed. Deploy Service returned ERROR:

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

/tc_SLCMS_cversproxy..

Reason: Webservices common deployment exception! The reason

is: Error occured, trying to generate deployment files for ws client com.sap.cm

s.tcs.cvers.proxy.CMSRTS, application sap.com/tc_SLCMS_cversproxy. . Additiona

l info: none; nested exception is:

java.lang.Exception: com.sap.engine.interfaces.webservic

es.server.deploy.WSDeploymentException: Webservices common deployment exception!

The reason is: Error occured, trying to generate deployment files for ws client

com.sap.cms.tcs.cvers.proxy.CMSRTS, application sap.com/tc_SLCMS_cversproxy.

. Additional info: none

at com.sap.engine.services.webservices.server.deploy.wsc

lient.WSClientsDeployGenerator.generateSingleWSClientDeployFiles(WSClientsDeploy

10/10/19 14:28:00 - start-up mode is lazy

10/10/19 14:28:00 - EAR file updated successfully for 16ms.

10/10/19 14:28:00 - Start deploying ...

10/10/19 14:28:00 - EAR file uploaded to server for 279ms.

10/10/19 14:28:01 - ERROR: Not deployed. Deploy Service returned ERROR:

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

/tc_SLCMS_cversproxy..

Reason: Webservices common deployment exception! The reason

is: Error occured, trying to generate deployment files for ws client com.sap.cm

s.tcs.cvers.proxy.CMSRTS, application sap.com/tc_SLCMS_cversproxy. . Additiona

l info: none; nested exception is:

java.lang.Exception: com.sap.engine.interfaces.webservic

es.server.deploy.WSDeploymentException: Webservices common deployment exception!

The reason is: Error occured, trying to generate deployment files for ws client

com.sap.cms.tcs.cvers.proxy.CMSRTS, application sap.com/tc_SLCMS_cversproxy.

. Additional info: none

at com.sap.engine.services.webservices.server.deploy.wsc

lient.WSClientsDeployGenerator.generateSingleWSClientDeployFiles(WSClientsDeploy

Generator.java:194)

at com.sap.engine.services.webservices.server.deploy.wsc

lient.WSClientsDeployGenerator.generateSingleWSClientDeployFiles(WSClientsDeploy

Generator.java:167)

at com.sap.engine.services.webservices.server.deploy.wsc

lient.WSClientsDeployGenerator.generateWSClientsDeployFiles0(WSClientsDeployGene

rator.java:155)

at com.sap.engine.services.webservices.server.deploy.wsc

lient.WSClientsDeployGenerator.generateWSClientsDeployFiles(WSClientsDeployGener

ator.java:139)

at com.sap.engine.services.webservices.server.deploy.wsc

lient.WSClientsDeployGenerator.generateWSClientsDeployFiles0(WSClientsDeployGene

rator.java:129)

at com.sap.engine.services.webservices.server.deploy.wsc

lient.WSClientsDeployGenerator.generateWSClientsDeployFiles(WSClientsDeployGener

ator.java:91)

at com.sap.engine.services.webservices.server.deploy.wsc

lient.WSClientsDeployGenerator.generateDeployFiles(WSClientsDeployGenerator.java

:46)

at com.sap.engine.services.webservices.server.deploy.wsc

lient.WSClientsDeployManager.deploy(WSClientsDeployManager.java:56)

at com.sap.engine.services.webservices.server.deploy.WSD

eployer.deploy(WSDeployer.java:158)

at com.sap.engine.services.deploy.server.application.Dep

loymentTransaction.makeComponents(DeploymentTransaction.java:606)

at com.sap.engine.services.deploy.server.application.Dep

loyUtilTransaction.commonBegin(DeployUtilTransaction.java:321)

at com.sap.engine.services.deploy.server.application.Dep

loymentTransaction.begin(DeploymentTransaction.java:307)

at com.sap.engine.services.deploy.server.application.App

licationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)

at com.sap.engine.services.deploy.server.application.App

licationTransaction.makeAllPhases(ApplicationTransaction.java:326)

at com.sap.engine.services.deploy.server.DeployServiceIm

pl.makeGlobalTransaction(DeployServiceImpl.java:3186)

at com.sap.engine.services.deploy.server.DeployServiceIm

pl.deploy(DeployServiceImpl.java:554)

at com.sap.engine.services.deploy.server.DeployServiceIm

plp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInter

nal(DispatchImpl.java:319)

at com.sap.engine.services.rmi_p4.DispatchImpl._run(Disp

atchImpl.java:200)

at com.sap.engine.services.rmi_p4.server.P4SessionProces

sor.request(P4SessionProcessor.java:136)

at com.sap.engine.core.service630.context.cluster.sessio

n.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.ja

va:33)

Edited by: Jag on Oct 19, 2010 9:29 PM

[thunder_feng]

Hello

firstly please help to check which JDK is being used? is it 1.4 or 1.5.

For PI 7.0, it must be 1.4.

Regards,

Thunder

[Former Member]

Thanks Thunder for your reply.here is the java vesion in my system

java -version

java version "1.4.2.23"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2.23-091005-06:23)

Java HotSpot(TM) Server VM (build 1.4.2 1.4.2.23-091005-04:04-IA64N IA64, mixed

mode)

I am also getting the below error , not sure this is the exact prob

Oct 19, 2010 11:15:35... Error: Aborted: development component 'tc/SL/CMS/TCSEar

'/'sap.com'/'MAIN_APL70VAL_C'/'1530540'/'6', grouped by software component 'DI_C

MS'/'sap.com'/'MAIN_APL70P16_C'/'1000.7.00.16.3.20091008145524''/'6':

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

vice:

java.rmi.RemoteException: Cannot deploy application sap.com/tc_SLCMS~TCSEar..

Reason: Errors while compiling:

/usr/lib/dld.sl: Bad magic number for shared library: /usr/lib/pa20_64/libc.2

/usr/lib/dld.sl: Exec format error

[HP ARIES32]: Core file for 32-bit PA-RISC application

[HP ARIES32]: /opt/java1.4/bin/javac saved to /usr/sap/QX1/DVEBMGS01/j2ee/clus

ter/server2/core.javac.

; nested exception is:

com.sap.engine.services.ejb.exceptions.deployment.EJBFileGenerationExcep

tion: Errors while compiling:

/usr/lib/dld.sl: Bad magic number for shared library: /usr/lib/pa20_64/libc.2

/usr/lib/dld.sl: Exec format error

[HP ARIES32]: Core file for 32-bit PA-RISC application

[Former Member]

Hi Ja,

Please refer to following SAP Notes for the above error:

335515 Bad magic number for shared library

And 639715; that describes similar error. Can you please

check for such inconsistancies?

Best Regards

Sajjan Kumar

[Former Member]

I checked the OSS note and i dont any inconsistencies in my system

Thanks

Ja

[Former Member]

"Error occurred generating ws client proxy files. Package error"

Looks like a package error,Download it again from market place and give a try.Also make sure that the .SCA file has 777 permission.

[thunder_feng]

Hello Ja

Apologize for the delay response, there is a known issue in SAP that if a higher JDK is used by the engine, then it will fail due to a compilation problem, with the following error as you are seeing:

Caused by: com.sap.engine.interfaces.webservices.server.dep loy.WSDeploymentException:

Webservices common deployment exception!

The reason is: Error occurred generating ws client proxy files.

Package error. .

Additional info: at com.sap.engine.services.webservices.server.deploy.wsc lient.WSClientProxyGenerator.generateAndPackageProxyFiles(WSClientProxyGenerator .java:61) at com.sap.engine.services.webservices.server.deploy.wsc lient.WSClientsDeployGenerator.generateSingleWSClientDeployFiles(WSClientsDeploy Generator.java:188) ... 25 more

Caused by: com.sap.engine.interfaces.webservices.server.dep loy.WSDeploymentException:

Webservices common deployment exception! The reason is: Error occurred trying to compile ws client proxy files. Compilation error. .

I understand the java 1.4 is being installed on this system, but is there any other JDK installed also?

could you please paste the content of this file from your system - sdm_jstartup.properties? which will shows us exactly whcih JDK is being used by the deploy tool.

Meanwhile could you please check note 1360910 as per the version you are using?

Thanks and best reagrds,

Thunder

[Former Member]

Here is the content of sdm_jstartup.properties . I used the same file to deploy in my DEV system and i was able to deply successfully in my DEV system. I checked the note and i have chhosen the correct file.

sdm.Name=SDM

sdm.Type=sdm

sdm.JavaPath=/opt/java1.4

sdm.MaxHeapSize=256

sdm.ClassPath=/usr/sap/QX1/DVEBMGS01/SDM/program/bin/SDM.jar

sdm.JavaParameters=-XdoCloseWithReadPending -XdoCloseWithReadPending -XdoCloseWi

thReadPending

sdm.MainClass=SDMInternal

sdm.ShutDownClassName=com.sap.sdm.jstartup.shutdown.InternalShutDown

sdm.Parameters=server sdmhome=/usr/sap/QX1/DVEBMGS01/SDM/program

sdm.rootPath=/usr/sap/QX1/DVEBMGS01/SDM/program

sdm.Debbugable=yes

thanks

Ja

[thunder_feng]

Hi Ja,

The sdm properties file show everything is fine.

Unfortunately I have no further idea neither, probaly you can report a customer message to sap under component

BC-CTS-CMS, and as the version is quite new, there is a possibility that this was just caused by an unknown bug.

Best Regards,

Thunder