Deployment Exception: Could not instantiate network ...

[Former Member]

Hey,

I'm having a problem deploying my process. I never had this error before, it's a big process with subprocesses etc. I just recreated my process (new DC name) and I'm still getting this error. I'm not sure where to look for possible mistakes!

Any help would be appreciated!

description: []
]. Cannot update it.
	at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:715)
	at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:226)
	at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:112)
	at com.sap.ide.tools.services.dc.EngineDcDeployService.deployFiles(EngineDcDeployService.java:160)
	at com.sap.ide.tools.services.dc.EngineDcDeployService.deploy(EngineDcDeployService.java:84)
	at com.sap.ide.dii05.ui.internal.actions.dc.DcDeployAction$3.run(DcDeployAction.java:224)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] 
An error occurred while deploying the deployment item [delaware.be_poc_complaint].

Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] 
An error occurred during deployment of [sdu id: [delaware.be_poc_complaint]
Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: [ERROR CODE DPL.DS.6193] 
Error while ;
Caused by: com.sap.engine.services.deploy.container.DeploymentException: Deploy Exception

Caused by: com.sap.glx.repository.exceptions.RuntimeRepositoryException: 
com.sap.glx.repository.exceptions.RuntimeRepositoryException: 
The runtime repository handler "Flow Handler" reported an exception while trying to add new versions for component poc_complaint

	at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy (RuntimeRepositoryDeployManager.java:263)
	at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive (ContentArchiveDeployContainer.java:1103)
	... 21 more

[Former Member · Accepted solution]

Forget rest of exception:

Caused by: com.sap.glx.repository.exceptions.HandlerException: com.sap.glx.deploy.api.DeployException: 
java.io.IOException: Could not instantiate network 2aa8a4d085e6639c0e493254e699ae08/delaware.be/poc_complaint/Approve.
The given network does exceed the maximum revision number. The given network has revision number 1.2 
(Galaxy BPMN to trigger network compiler as of NetWeaver CE EhP1. Give yourself to the dark side.) 
but maximum possible revision number is 1.1.

	at com.sap.glx.core.resource.impl.j2ee.rrdeploy.KernelHandlerImpl.addVersion(KernelHandlerImpl.java:84)
	at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deployArchive(RuntimeRepositoryDeployManager.java:1180)
	... 23 more

Caused by: com.sap.glx.deploy.api.DeployException: java.io.IOException: 
Could not instantiate network 2aa8a4d085e6639c0e493254e699ae08/delaware.be/poc_complaint/Approve.
The given network does exceed the maximum revision number. The given network has revision number 1.2 
(Galaxy BPMN to trigger network compiler as of NetWeaver CE EhP1. Give yourself to the dark side.) 
but maximum possible revision number is 1.1.

	at com.sap.glx.deploy.impl.DeployControllerImpl$InternalActuator.deploy(DeployControllerImpl.java:447)
	at com.sap.glx.core.resource.impl.j2ee.rrdeploy.KernelHandlerImpl.addVersion(KernelHandlerImpl.java:78)
	... 24 more

Caused by: java.io.IOException: Could not instantiate network 2aa8a4d085e6639c0e493254e699ae08/poc_complaint/Approve.
The given network does exceed the maximum revision number. The given network has revision number 1.2 
(Galaxy BPMN to trigger network compiler as of NetWeaver CE EhP1. Give yourself to the dark side.) 
but maximum possible revision number is 1.1.

	at com.sap.glx.core.kernel.trigger.config.CSVNetBuilder.parse(CSVNetBuilder.java:1020)
	at com.sap.glx.core.kernel.trigger.config.CSVNetBuilder.parse(CSVNetBuilder.java:274)
	at com.sap.glx.deploy.impl.DeployControllerImpl$InternalActuator.deploy(DeployControllerImpl.java:429)
	... 25 more

[OliverGoetz · Accepted solution]

Hi Lynne,

the network revision numbers you see here are version numbers of the internal format for the BPM deployments.

It was necessary to change something in this format between Support Package 3 and 4, and therefore the minor revision counter was incremented.

Because a higher revision usually means that something new was introduced in the format, the rule is that the revision number of the deploy unit must be equal or less than that of the AS Java installation - otherwise the runtime components in the server would not know how to deal with it!

The error message you see suggests that you have updated your NWDS or your NWDI content already to SP4, but the server is still on SP3 or earlier. To resolve this problem you need to update the server to SP4 (or, if you don't wish to do that for some reason, use an SP3 version of the NWDS or model your process in an NWDI track which is still on SP3).

For SAP NetWeaver CE 7.1 EhP1, the major revision number will always stay on 1.

For SAP NetWeaver CE 7.2, the major revision number will be increased to 2.

Best regards,

Oliver

[Former Member · Accepted solution]

Thanks !

[Former Member · Accepted solution]

Hi,

last week I got the same error and I could find the error by assitance thru SAP.

For everybody, like me, who did not know how to check the version number just have a look at this:

In NWDS:

1. Help > Support Information (Save to Desktop) > Unzip file and open "installinfo.xml"

2. In second line you see the IDE version is "...NW711_03.." --> This means 7.1.1 SP3

In Composition Environment:

1. Open [http://hostname:portnumber/sap/monitoring/ComponentInfo|http://hostname:portnumber/sap/monitoring/ComponentInfo]

2. Check the version of the BPEM* SCAs

Compore both version numbers. They must be on the same level

Regards

[Former Member]

We're facing a similar problem. Is there an expiration date or automatic update on the CE? Being this close to the 7.2 ramp-up?