cancel
Showing results for 
Search instead for 
Did you mean: 

Problems to deploy ADSSAP SPS14

Former Member
0 Kudos

Hi,

try to deploy on NW7.0 SPS10 the new stack SPS14.

I have difficulties to deploy the ADSSAP (Adobe Document Service) Component.

The following error is shown in the sdm log file

Caught exception during deployment from SAP J2EE Engine's offline deploy API:
com.sap.engine.tools.offlinedeploy.rdb.ODeploymentException: ERROR: Can't deploy component with sda D:\usr\sap\J02\JC01\SDM\root\origin\com.adobe\PDFManipulation\Adobe Systems\1\800.20070626144044.156488\adobe-PDFManipulation.sda
com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: ,
	at com.sap.engine.core.configuration.impl.persistence.rdbms.UpdateProcessor.flush(UpdateProcessor.java:342)
	at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.commitConfigurationHandler(ConfigurationCache.java:1184)
	at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.commit(ConfigurationHandlerImpl.java:914)
	at com.sap.engine.tools.offlinedeploy.rdb.OfflineComponentDeployImpl.deployComponent0(OfflineComponentDeployImpl.java:410)
	at com.sap.engine.tools.offlinedeploy.rdb.OfflineComponentDeployImpl.deployComponent(OfflineComponentDeployImpl.java:266)
	at com.sap.sdm.serverext.servertype.inqmy.extern.EngineOfflineDeployerImpl.performDeployment(EngineOfflineDeployerImpl.java:209)
	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:128)
	at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:97)
	at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:68)
	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.nwmss.jdbc.base.BaseBatchUpdateException: [SAP_NWmss][SQLServer JDBC Driver]The DBMS returned an unspecified error.  The command code was 0.
	at com.sap.nwmss.jdbc.sqlserver.SQLServerImplStatement.getBatchRowsAffectedCount(Unknown Source)
	at com.sap.nwmss.jdbc.base.BasePreparedStatement.executeBatch(Unknown Source)
	at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeBatch(BasicPreparedStatement.java:263)
	at com.sap.sql.jdbc.mss.MssInetPreparedStatement.executeBatch(MssInetPreparedStatement.java:188)
	at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1129)
	at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1091)
	at com.sap.engine.core.configuration.impl.persistence.rdbms.DBAccessDefault.execUpdateFileBatch(DBAccessDefault.java:1223)
	at com.sap.engine.core.configuration.impl.persistence.rdbms.UpdateProcessor.flush(UpdateProcessor.java:322)
	... 33 more

In the SQL Server Log I saw the following message:

WARNING:  Failed to reserve contiguous memory of Size= 36765696.
 Insufficient memory available..

I detected the following sap note:

795991

but it does not help.

Any other hints or suggestions.

Regards Karin

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

The problem is solved now. The server was low on memory (a reboot of the server solved the problem).

Former Member
0 Kudos

Check if you have enough free diskspace, especially under ...\trans\EPS\in

Have you set the JVM parameters as per Note 723909 - Java VM settings for J2EE 6.40/7.0