Provisioning Issues (SOAP) Between SBC 740m1 And SDM 7.5
(Doc ID 2336210.1)
Last updated on JANUARY 03, 2024
Applies to:
Oracle Communications Session Delivery Manager - Version 7.5 and laterInformation in this document applies to any platform.
Symptoms
Customer is having issues while trying to create session agents and save the configuration via SOAP.
They are using a 7.5 SDM and SBC with the version 740m1.
Below are the errors observed:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>Error in addConfigElement. AcmeConfigException thrown. Reason : Cardinality Constraint Violation. Reason: Found 0 occurrences; the minimum number of occurrences allowed=1[]</faultstring>
<detail>
<ns1:AcmeConfigWSFault xmlns:ns1="http://configmgmt.service.ws.ems.acmepacket.com/">
<validation xmlns:ns2="http://configmgmt.service.ws.ems.acmepacket.com/">Error in addConfigElement. AcmeConfigException thrown. Reason : Cardinality Constraint Violation. Reason: Found 0 occurrences; the minimum number of occurrences allowed=1[]</validation>
</ns1:AcmeConfigWSFault>
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>
//////////////////////////////////////////////////
<isIntegrityCheckSuccess>
FAILED
</isIntegrityCheckSuccess>
<overallFailMessage>
com.acmepacket.ems.common.error.DeviceManagerEMSException: Validation Error. Integration count of toplevel elements in EMS database is not matching the toplevel elements in device.
</overallFailMessage>
<overallStatus>
FAILED
</overallStatus>
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |