4 Appendix

4.1 List of Error Codes

Provisioning Gateway uses a numeric strings as error code. There are the following ranges with
their meaning:
· 3000 – 3499 and 4000 - 4999
These ranges contain error messages, which directly occur on the SPML interface and are
related to SPML request processing.
· 3500 – 3999
This range contains error messages, which occurred during the LDAP execution.
· 5000 – 8999
This range contains error messages, which are generated by the mapping and validation
framework using semantic and integrity checks by Provisioning Gateway. For more, refer
to application IF specifications.
Note: The following error texts contain number in parenthesis. For example, ‘{0}’, which
represent a parameter that is replaced with a real value at runtime.

4.2 SPML Processing Errors

These errors are related to the SPML interface and not to an SPML application.
Error code Error Text Repair Text

3000 The user specified in the SPML request has The user policy denies the execution of the request. User
insufficient rights. policies are specified in user management on the
provisioning gateway administration Web GUI. See the online
help for the provisioning gateway administration GUI.

3001 The request was not executed (inside of a
batchRequest), because an error occurred which
was caused by other request or because of
processing time-out.
An SPML request inside a batch request is not executed
when an 'exit_commit' or 'exit_rollback error type occurs'.
This is caused by another SPML request (inside the batch
request) that finished with error. In addition, this situation
can be caused by the time out of a request that took too
long to be processed. To check the timeout value set in the
provisioning gateway, see the online help for the
provisioning gateway administration GUI (the request
manager properties).

3002 The object specified in the modifyRequest is not Using a search request, check whether the required object
available in the One-NDS. exists in the One-NDS.

3003 The syntax of the modifyRequest is not valid. The syntax of the modify request is not allowed by the SPML
interface specification. See the SPML interface specification
for the correct syntax.

25-05-2016 – A50016-E4160-C104-2-7618 Confidential © Nokia Solutions and Networks 2016

165 / 191
 Error code Error Text Repair Text

3004 There are too many requests within the
batchRequest. The maximum number of allowed
requests inside of a batchRequest is {0}.
You have exceeded the maximum number of allowed
requests inside a batch request. This value is configurable
on the provisioning gateway administration GUI. See the
online help for the provisioning gateway administration GUI
(global configuration data).

3005 Processing of the request was interrupted. The execution of the request took too long and was
interrupted by the provisioning gateway. To check the
timeout value set in the provisioning gateway, see the online
help for the provisioning gateway administration GUI
(request manager properties).

3006 Cannot perform {0} modification(s) for object {1}; The required modification cannot be performed because the
reason: the element specified in the defined object does not exist in the One-NDS.
modifyRequest does not exist in the One-NDS.

3007 The execution of the sub-request(s) failed. One or more requests inside a batch request have failed. For
a reason, refer to the error response of the failed sub-
request(s).

3008 Validation of request against the XML schema The received request does not correspond to the XML
failed. schema definitions. This request is rejected. Do not retry.

3009 The provisioning gateway is shutting down and
does not accept new requests. The request with
the reguestId={0} was rejected.
The provisioning gateway does not accept any new requests
while shutting down or restarting. Try to send the request
later.
All requests that were accepted before shutdown or restart
are processed later.

3010 Request was canceled. A request was successfully canceled by the client.

3011 The status of the request with the requestId={0} The request specified in the status request cannot be
could not be obtained. identified by the provisioning gateway. This means that it is
neither processed nor stored in the request history.

3012 The request with the requestId={0} was found in The request was rejected. You provided the
the request history. 'newGenerated=true' attribute, but this request was already
processed by the provisioning gateway. To obtain the result
of the processed request, send the request again with the
”newGenerated=false” attribute.

3013 The request with the requestId={0} was not found The request was rejected. You provided the
in the request history. ”newGenerated=false” attribute, but this request was not
found in the request history and therefore no result can be
provided. Either the request is old and was deleted from the
request history or the request was not received by the
provisioning gateway.

3014 The request with the requestId={0} was rejected. The provisioning gateway cannot accept more requests
The Provisioning Gateway is overloaded. because of an overload situation. Try to send the request
later when the load is lower.

3015 Unknown object class received: The object class The object class provided in the request is not supported by
{0} cannot be retrieved from the XML schema. the XML Schema used. Do not retry. Correct the request.

25-05-2016 – A50016-E4160-C104-2-7618 Confidential © Nokia Solutions and Networks 2016

166 / 191
 Error code Error Text
3016 Unsupported application: cannot find the
application with the target namespace {0}.
3017 Unsupported application: cannot find the
application for category ''{0}'', application
namespace ''{1}'', spml namespace ''{2}'', request
type ''{3}'', object type ''{4}''.
3018 Invalid first class object attribute received: {0}.
3019 Negative index used in SPML modification: {0}={1}.
3020 The bulk file contains more requests than the
allowed number for the OnError attribute
exit_rollback allows..
3021 Unsupported version string in the request.
3022 Validation of the request failed.
3023 Validation of the addRequest failed.
3024 Execution of request {0} is not allowed/supported.
3025 The maximal number of occurrences [{0}] has
been exceeded for attribute {1}.
3026 The Request ID {0} is not valid. ID must contain
only letters, digits and chars '-' and ':' and must be
shorter than 40 characters.
25-05-2016 – A50016-E4160-C104-2-7618 Confidential
167 / 191
Repair Text
The application with this namespace is not supported by the
provisioning gateway. Do not retry. Correct the request.
The application specified in the request is not supported by
the provisioning gateway. Do not retry. Correct the request.
The first class object used in the request is not supported
by the XML Schema used. Do not retry. Correct the request.
The modify request contains an index with negative values.
Only positive values are allowed. Do not retry. Correct the
request.
With the OnError attribute set to “exit_rollback”, the
maximum number of requests allowed in a single batch
request is restricted to a fixed value. Check the
configuration.
The request contains a version string which is currently not
supported. Check the list of applications and persistency
plug-ins installed and issue only requests for supported
versions.
The submitted SPML request is not valid. Syntax validation
has failed. You can find more information in the
ValidationInfo of the SPML response.
The submitted SPML add request is not valid. Syntax
validation has failed. You can find more information in the
ValidationInfo of the SPML response.
The submitted request cannot be executed by Provisioning
Gateway because it is not supported. The reason might be
one of the following:
- the request was submitted on an interface which does
not support such a request
- the request is not allowed in your Provisioning Gateway
configuration
- the request is not supported in your Provisioning
Gateway configuration
The submitted SPML requests tries to add an SPML attribute
value which exceeds the allowed number of values for this
attribute. You have to delete at least one of the existing
values for this attribute in order to be able to add a new
value. After you deleted at least one value, the request can
be retried.
The supplied requestID within the SPML request contains
invalid characters. Provide a compliant requestID and retry
the request.
© Nokia Solutions and Networks 2016
 Error code Error Text Repair Text

3027 Unavailable / Unsupported version string in the The version string within the SPML request (element
request in root level. <version>) contains an unsupported version string. Do not
retry. Either correct the version string or check the installed
plug-ins of Provisioning Gateway whether the required
version is also installed.

3028 The request with the requestId={0} was rejected. Request with same requestId is in processing. Change
The request was found in the Request Queue. requestId or try again later.

3029 Request was queued, but timeout elapsed prior to The request was queued for processing, but possibly due to
request processing. its low priority it was not processed within pre-configured
time period or the processing itself was blocked.

If this error is frequent it may require cautious tuning of

following configuration parameters:

- request priorities - explicit in requests or configured

priority profiles per request type. Request priorities
distribution might be inadequate to meet real traffic
profile requirements.

- increase request timeout that request is allowed to

spend in request queue

It is also possible that NDS or network causes that

processing was blocked and has to be analyzed as well.

3030 {0} The re-encryption of the SIM card is not possible. For more
information see the error message.

3031 AucEncrypter returned wrong re-encryption The received response from the re-encryption end-point
result. does not correspond to the re-encryption interface. Wrong
configuration of Provisioning Gateway or re-encryption
software.

3032 Request can not be executed in asynchronous The supplied SPML request cannot be executed in
mode. The request with the requestId={0} was asynchronous mode (usually the cancelRequest or
rejected. statusRequest). Specify a synchronous execution mode and
retry.

3033 The complete batchRequest was rolled back
because of failure of a sub-request.
The submitted batchRequest was rolled-back as a whole
because an error occurred during sub-request execution.
Although you might notice that some of the sub-requests
are provided with success, all the changes were rolled back.
Refer to the details of the failed sub-request(s) to find the
reason of the failure. In some circumstances the retry might
be successful, dependent on SPML requests provided.

3034 LDAP referral problem: The search result might An internal error occurred. Contact Nokia Solutions and
not be complete. Networks personnel.

3035 SearchForUpdate for identifier {0} failed with An internal error occurred. Contact Nokia Solutions and
errorCode={1}. Networks personnel.

25-05-2016 – A50016-E4160-C104-2-7618 Confidential © Nokia Solutions and Networks 2016

168 / 191
 Error code Error Text Repair Text

3036 Unable to move the file from ''{0}'' to ''{1}''. An internal error occurred. Contact Nokia Solutions and
Networks personnel.

3037 Could not find the file: ''{0}''. An internal error occurred. Contact Nokia Solutions and
Networks personnel.

3038 I/O Error occurred while accessing file/directory: An internal error occurred. Contact Nokia Solutions and
''{0}''. Networks personnel.

3039 Could not create the directory ''{0}'.' An internal error occurred. Contact Nokia Solutions and
Networks personnel.

3040 Unexpected internal error occurred. An internal error occurred. Contact Nokia Solutions and
Networks personnel.

3041 Internal Error occurred: User ''{0}'' does not have The SFTP user doesn’t have rights to execute the OS
enough rights to perform function: ''{1}''. operation. Contact Nokia Solutions and Networks personnel.

3042 Could not open file ''{0}''. An internal error occurred. Contact Nokia Solutions and
Networks personnel.

3043 Unexpected Request received in Bulk interface. The root tag of the xml doesn’t have the supported value.
Root tag should be ''batchRequest'' or Do not retry. Correct the request.
''searchRequest''.

3044 Unexpected request. Bulk interface does not Communication using callback is not supported on bulk
support Call Back. interface. Do not retry. Correct the request.

3045 Unexpected request. Bulk interface does not Bulk interface doesn’t support provided execution type. Do
support Execution Type as: ''{0}''. not retry. Correct the request.

3046 Unexpected request. Bulk interface does not Bulk interface doesn’t support provided onErrorType. Do
support onErrorType as: ''{0}''. not retry. Correct the request.

3047 Error occurred while parsing request. The provided file couldn’t be parsed. The request is not well-
formed (opening or closing tags are missing). Correct the
request.

3048 Bulk file ''{0}'' contains more requests than The file contains more requests then it is allowed. Check the
maximum permissible number of requests: ''{1}''. configuration.

3049 Shutdown in progress. File: ''{0}'' will not be Re-try after start-up of PGW.
processed.

3050 Execution timeout. Bulk file: ''{0}'' could not be Try to increase the configuration limit or simplify the
processed within the configured time limit ''{1}'' request to be able to finish with in the configured time or
try to execute the request is low traffic time.
hour(s) .

3051 Processing Type : ''{0}'' is not supported in bulk The provided processing type is not supported on bulk
file interface. interface. Do not retry. Correct the request.

3052 Request not executed: error during exit commit. Check the reason of failure of the failed request.

25-05-2016 – A50016-E4160-C104-2-7618 Confidential © Nokia Solutions and Networks 2016

169 / 191
 Error code Error Text
3053 Request cannot be executed because information
about Bulk User : ''{0}'' could not be fetched.
3054 Unsupported request : One or more values of
''{request type,ObjectClass,version,spml
namespace,application namespace}'' is not valid.
3055 The maximum attempts of order recovery has
exceeded the configured value of
bfiMaximumOrderRestarts {0}, hence the
execution of this order is aborted.
3056 Request rejected: Bulk request can only be
present in a file with extension ''{0}''
3057 Invalid bulk request:Either
identifierRangeFilename or filter should be
present in request.
3058 Invalid bulk request:When operation is "modify",
modification element is mandatory in the request
3059 Invalid bulk request:When operation is "delete"
,modification element should not given in the
request.
3060 Request rejected: Already a bulk request with
name: ''{0}'' is executing and only one bulk request
can be executed at a given instance of time.
3061 The identifier range file ''{0}''specified in request,
is not present in directory ''{1}''
3062 Internal error occurred while processing few
identifiers. Please check the identifiers file(s): {0}
in outbox and check the status of these identifiers
with a separate request.
3063 Execution aborted as no configured slave
instances could be contacted for processing the
request.
3064 Execution aborted and order cancelled due to
shutdown from user.Please check the identifiers
file(s): {0} in outbox and check the status of these
identifiers with a separate request.
3065 Request cancelled :This request is cancelled by
the user
25-05-2016 – A50016-E4160-C104-2-7618 Confidential
170 / 191
Repair Text
An internal error occurred. Contact Nokia Solutions and
Networks personnel.
Either the request is wrong or the plug-in that supports that
request is not installed. Contact Nokia Solutions and
Networks personnel.
The PGW host was restarted to many times during the
request execution. Contact Nokia Solutions and Networks
personnel.
Correct the file extension to the supported one “.mass”.
Correct the request. Provide the filter or list of identifiers on
who’s the operation shall be executed.
Correct the request. Provide the modification element.
Correct the request. Remove the modification element.
Only one bulkRequest can be executed in time. Wait for the
pending bulkRequest to finish and re-try.
Upload the identifier range file to the “identifiers” directory
and re-try.
An internal error occurred. Contact Nokia personnel.
An internal error occurred. Contact Nokia personnel.
The request is cancelled because of shutdown of PGW.
Check the status of the finished requests and re-try those
that are needed.
The execution of the request was stopped on behalf of the
user. Check the results and proceed accordingly.
© Nokia Solutions and Networks 2016
 Error code Error Text Repair Text

3066 Execution aborted due to a cancel request from
user. Additionally internal error detected while
processing few identifiers. Please check the
identifiers file(s): {0} in outbox and check the
status of these identifiers with a separate
request.
The execution of the request was stopped on behalf of the
user. Check the results and proceed accordingly. . Some
errors have been discovered. Check the status of those
subscribers.

3067 Delete scope ''{0}'' is not supported for this Correct the SPML request using a proper (application
application or version. specific) deleteScope value.

3068 This bulk request is rejected, as it is not submitted Check the configuration and upload the request to the
in configured master PGW host {0}. proper / master host.

3069 {0} Correct the alias name or value to select an existing object
in database

3070 Request rejected: Already a search request is Repeat the request execution after the running search
executing and only one search request can be request finishes.
executed at a given instance of time.

3071 Search for {0} was unsuccessful. {1} Identity / Alias used in the request does not identify an
object in database. Correct the request.

3072 Different request sent with the same Use another (or none) request ID and repeat the request.
requestId={0}.

3073 Could not retrieve final result for request with The request with the given id is still in execution and the
requestId={0}, since not available, yet. response is not available yet.

1) This may happen because the requestId of the current

request matches that of another request already in
execution. Correct the request id and retry.

2) If 1 is not true, Check the load on the system and then

execute the request again.

3074 Request cannot be processed. Application {0} is Contact the system administrator to check the SPML user
not allowed for user {1}. rights

3075 This order is rejected as it could not be executed Re-issue the order again.
on scheduled time.Please re-issue the order
again.

3076 Request rejected: Already configured number of Repeat the request execution after a running search request
search requests are executing. finishes.

3077 Member specified by {0} not found. Check why the member is missing in the application SPML
schema. Correct the request.

3078 Extended Request operation {0} failed with result Check the detailed error information and possibly correct
{1}. the request.

3079 This search request is rejected, as it is not Check the configuration and upload the request to the
submitted in configured master PGW host {0} proper / master host.

25-05-2016 – A50016-E4160-C104-2-7618 Confidential © Nokia Solutions and Networks 2016

171 / 191
 Error code Error Text Repair Text

3080 The received request could not be mapped, A mapping error occurred. Contact the PGW module
please check configuration files. provider (Nokia personnel).

3083 Unique Member Expected: Member ({0}) Correct the request and try again.
addressed via slash notation is not unique.

3084 Slash notation is not correct: {0}. Correct the request and try again.

3100 Re-encryption of secret subscriber key was not Invocation of multiple HLR-FEs from PGW configuration for
possible even after re-invoking HLR-FEs. re-encryption was not successful. Check the configuration
and contact Nokia personnel.

3101 Value of {0}:{1} is invalid since {2}. Attributes provided in SPML request, which are need for re-
encryption, are not correct. Correct the request.

3102 HLR-FE returned failure re-encryption response. An internal error occurred on HLR-FE side. Contact Nokia
Error Code: {0}. Error message: {1} personnel.

3168 Request with only filterType as negative is not Correct the filter in the SPML request
supported.

3169 The responseFileSize in the request {0} is not Correct the response file size attribute in the SPML request
valid, and should be within range of {1}.

3400 The applicationVersion provided is not currently
supported as there is no application plugin which
supports this applicationVersion.
The application version string within the SPML request
(element <version>) contains an unsupported version string.
Do not retry. Either correct the version string or check the
installed plug-ins of Provisioning Gateway whether the
required version is installed or not.

3402 Alias {0} is not supported. Unsupported alias name is used in the request. Retry the
request with a supported alias.

3403 Request cannot be processed, module {0} is not Provisioning data of unsupported module is not possible.
installed or not configured in the PC. Retry with a valid request.

4000 Could not get instance of {0}. An internal error occurred. Contact Nokia personnel.

4001 Attribute {0} is missing. Configure the attribute given in the error message.

4002 The object {0} could not be created. An internal error occurred. Contact Nokia personnel.

4003 Error occurred while retrieving {0}. An internal error occurred. Contact Nokia personnel.

4004 Mapping information for {0} could not be found. An internal error occurred. Contact Nokia personnel.

4005 Internal error in Mapper. An internal error occurred. Contact Nokia personnel.

4006 Internal system error occurred: {0}. An internal error occurred. Contact Nokia personnel.

4007 Internal error in mapper due to invalid subscriber It is not possible to map the object from PST to SPML
in database: {0} objects, because it violates the SPML rules. The message
provides information what rules are violated. The error
condition must be resolved, before any operation can be

25-05-2016 – A50016-E4160-C104-2-7618 Confidential © Nokia Solutions and Networks 2016

172 / 191
 Error code Error Text Repair Text

done via SPML to the subscriber, except delete as specified

in SPML IF. Contact Nokia personnel.

4008 Mapping could not be done for attribute {0}. An internal error occurred. Contact the Nokia service
department.

4009 {0} cannot be administered. The requested object cannot be administered with the
Provisioning Gateway. Related attributes are only modified
during call-processing operations.

4010 Input/output error occurred while accessing: {0}. An internal error occurred. Check the disk usage or contact
the Nokia service.

4011 Configuration missing for {0}. An internal error occurred. The expected configuration is
missing. Contact the Nokia personnel.

4012 Invalid value {0} for attribute {1}. The attribute specified cannot contain the value assigned.
Check the schema for the allowed set of values.

4013 Error encountered while performing response An internal error occurred. The response received from
handling for {0}. database cannot be processed. Contact the Nokia
personnel.

4014 Modification of {0} is not allowed The requested object/attribute cannot be modified. Contact
the Nokia service department.

4015 Entry {0} in {1} already exists. Set another value appropriate for the service given in the
error message because the given entry already exists.

4016 Internal error occured: Invalid configuration found An internal error occurred. Contact Nokia personnel.
/ unable to read configuration value. ''{0}''.

4017 Entry with dn: {0} does not exist in DS. An internal error occurred. Contact Nokia personnel.

4018 Operation type: {0} is not supported. The specified operation cannot be performed.

4019 Date in {0} is either invalid or not of format yyyy- Provide the value for the given attribute in the date format
MM-dd. YYYY-MM-DD.

4020 Number format of {0} is invalid. Provide a valid number for the specified attribute.

4021 The SPML object with value {0} not found. SPML object is not found in the schema.

4022 The received list of controlValue has many entries. An internal error occurred. Contact Nokia personnel.

4023 {0} cannot be modified or deleted Attribute mentioned in error message cannot be modified
or delete

4024 SPML Request {0} content is invalid because: {1}. SPML request is not consistent. Correct the request and try
again.

4025 Entity {0} does not exist. SPML request requires existence of specified entity in DB,
which is missing. Correct the request.

25-05-2016 – A50016-E4160-C104-2-7618 Confidential © Nokia Solutions and Networks 2016

173 / 191
 Error code Error Text Repair Text

4026 Read of Entity {0} failed with: {1}. SPML request requires entity to be read from DB, which
failed with the specified error. The issue reported may be
temporary or permanent. If the problem persists contact
Nokia personnel.

4027 Entity {0} is not valid for operation because: {1}. The operation required by the SPML request for the
reported entity cannot be performed due to some detected
inconsistencies reported in the error message. Check the
request and the state of the reported entity and apply
corrections to the request or the entity as required.

4101 {0} requires {1} feature to be SOLD and ACTIVE in The feature given in the error message is currently not sold
CONFIGURATION DATA. or not active. Contact Nokia personnel.

4102 Administration of {0} is not allowed if {1} is not Administration of attribute{0} mentioned in the error
subscribed. message is not allowed if attribute {2} is not subscribed

4103 {0} cannot be empty if {1} is mentioned. Correct the request by giving an appropriate value for the
attribute given in the error message.

4104 Value of {0} cannot be greater than value of {1}. Administer a lower value for the attribute given in the error
message and retry.

4105 Current number of instances for {0} is {1}. Administer the service given in the error message within the
Minimum no of instances expected is {2}. range specified.
Maximum no of instances expected is {3}.

4106 {0} value is not in the allowed list of values {1}. Administer a value given in the allowed list of values.

4107 {0} is not configured in {1}. The specified value is not configured in the given
configuration table.

4108 {0} and {1} are mutually exclusive. Subscribe only one of the two services given in the error
message.

4109 {0} cannot be deleted as {1} is present. Dependency exists between two objects. Correct the
request.

4110 Deletion of {0} not allowed. Deletion of the given attribute is not allowed. Correct the
request.

4111 Internal error in Validator. An internal error occurred. Contact Nokia personnel

4112 Default value for {0} not set. An internal error occurred. Contact Nokia personnel.

4113 Length of {0} is invalid. Minimum length should be The length of the given attribute is invalid. Give a proper
{1} and maximum length allowed is {2}. value.

4114 {0} is invalid since it is not in range {1}. Administer the value in the given range.

4115 Administration of {0} is not allowed if {1} is Correct the request by removing one of the attributes given
subscribed. in the error message and retry.

25-05-2016 – A50016-E4160-C104-2-7618 Confidential © Nokia Solutions and Networks 2016

174 / 191
 Error code Error Text Repair Text

4116 Multiple values are not allowed for {0}. Cannot assign multiple values for single-valued attribute
given in the error message. Retry the request with the single
value.

4117 {0} cannot be deleted as {1} is present. Consistency check failed: attribute specified in the error
message cannot be deleted if the other specified attribute
is present in the DB. Correct the request.

4118 Mandatory attribute {0} is missing. Missing mandatory attribute. Check and correct the SPML
request to provide valid value for the required attribute.

4119 {0} is not a valid decimal number. The value is not a valid decimal number, please correct the
value and try again.

4120 {0} is not a valid hexadecimal number. Invalid hexadecimal number. Retry with a valid hexadecimal
number.

4121 Delete Scope 'subscription' cannot be supported The retainConfiguration.xml configuration file is either
as retainConfiguration.xml file is missing or missing or empty. Provide the valid retainConfiguration.xml
empty. file in the plug-in configuration and retry the delete request.
Or do not provide delete scope subscription in the delete
request if not needed.

4122 Number format of {0} is invalid. Number format is invalid. Retry with a valid number format.

4123 {0} is mandatory for {1}. Correct the request and provide all required
attributes/objects.

4124 The number of entries allowed for {0} has Number of values exceeds the allowed number, please
exceeded the allowed value : {1}. correct the request and try again.

4125 The value of {0} is invalid. It should be of the The value mentioned in the error message is invalid. Please
format: {1} provide the value in the specified format.

4126 The value of {0} is invalid.Special characters are Special characters are not allowed for this value. Correct the
not allowed. request.

4127 Number of children of {0} for {1} is not within the This occurs when the input SPML request has more number
range {2}. of children for a given parent than allowed limit as per the
association metadata definition.

4702 Search request is aborted as the search request Retry the request.
execution has exceeded the configured number of
retries.

4703 Error occurred while performing search on Retry the request (when the directory server(s) is available).
dsaId(s): {0}.

4704 Request is cancelled due to the system shutdown Retry the request (or its part) when PGW is running again.
in progress.

4705 Problem with directory servers, please check the Please check the state of the directory server before retry
state of the directory server before retry of the of the request.
request.

25-05-2016 – A50016-E4160-C104-2-7618 Confidential © Nokia Solutions and Networks 2016

175 / 191
Table 37: Table of SPML processing errors

4.2.1 LDAP Errors

These errors are related to the LDAP interface at the DSA.

Error code Error Text Repair Text

3500 The LDAP Execution failed. The generated LDAP requests were not executed
successfully in the One-NDS. The exact error is
encapsulated in the LDAP info element of the SPML
response together with the appropriate LDAP error code
and message. For more information, refer to [DIP].

3501 The LDAP Connection to {0} failed. The LDAP connection to the given host was not established
because either the LDAP database is not available or there
are not enough LDAP connections configured in the
connection pool. If the LDAP database is not available, an
alarm is generated by the provisioning gateway. Check the
status of the database manually. To check the size of the
LDAP connection pool, see the online help for the
provisioning gateway administration GUI.

3502 Cannot carry out {0} unless transaction is started. An internal programming error occurred. Contact Nokia
service.

3503 The object: {0} – was not found in the One-NDS. The object specified in the search request cannot be found
in the One-NDS. Check your request.

3504 Object {0} already exists. The object specified in the add request already exists in the
One-NDS and cannot be created again.

3505 The LDAP object class is passed as {0}. An internal programming error occurred. Contact Nokia
service.

3506 Error occurred while retrieving {0}. An internal programming error occurred. Contact Nokia
service.

3507 Cannot carry out the searchRequest because the Please correct the filter criteria in the request.
search filter is invalid.

3508 Ldap user for : {0} is not defined. An internal programming error occurred. Contact Nokia
service.

3509 Only One SearchResult Is Expected For Update. An internal programming error occurred. Contact Nokia
service.

3510 Either Transaction request is made when Check configuration. Contact Nokia service.
transactions are disabled or An attempt is made to
modify schema during a transaction.

3511 Request to start a transaction made, when the Check database configuration. Contact Nokia service.
number of concurrent transactions was already at
the maximum.

25-05-2016 – A50016-E4160-C104-2-7618 Confidential © Nokia Solutions and Networks 2016

176 / 191
 Error code Error Text Repair Text

3512 An update within a transaction, or a transaction Contact Nokia service.

end request specified a transaction identifier that
is not recognized.

3513 Too many update operations within a single Check database configuration. Contact Nokia service.
transaction.

3514 A transactional update operation after issuing a An internal programming error occurred. Contact Nokia
request for the transaction to end. service.

3515 Attempt to end a transaction while there were An internal programming error occurred. Contact Nokia
pending update operations. service.

3516 Attempt to do a transaction update or a Other client possibly the application modified the data that
transaction commit operation if a non- the SPML request wanted to modify. Re-try the operation
transactional operation has updated a transaction later.
locked object.

3517 An update operation on an object that is currently Other client is already modifying this subscriber. Try again
locked by another transaction. later.

3518 A transaction handler (a primary node) has failed An internal error occurred in database. Contact Nokia service.
and the primary standby has assumed the primary Re-try the request.
role.

3519 The transaction controller does not receive pre- An internal error occurred in database. Contact Nokia service.
commit acknowledgements from all transaction Re-try request later.
handlers within the permitted maximum time.

3520 Network connectivity break or a server fail after Error occurred in database. Contact Nokia service. The result
the transaction controller has issued commit of the transaction is not known. Verify the subscriber data
requests to each transaction handler. and apply any updates, which have not been performed.

3521 Unique numeric search key range is mandatory for Please correct the filter criteria in the request.
the requests with NOT filter executing through
bulk interface.

3522 Unique numeric search key range is mandatory for Please correct the filter criteria in the request.
the requests executing through soap interface.

3523 Invalid unique numeric search key range filter Please correct the filter criteria in the request.
values.

3524 Invalid unique numeric search key range key for Please correct the filter criteria in the request.
this application.

3525 The unique numeric key range difference(Max-Min) Please correct the filter criteria in the request.
{1} is not within 1 and the configured limit {0}.

3526 Search request takes more than the configured Please correct the filter criteria in the request.
time to execute. Try with a smaller range of
subscribers.

3527 The maximum asynchronous operations exceeded, Too many LDAP write operations were issued in parallel.
could not acquire permit for execution. Either the limit of maximum parallel operations issued by

25-05-2016 – A50016-E4160-C104-2-7618 Confidential © Nokia Solutions and Networks 2016

177 / 191