The SAP CC system or a subcomponent can recover from anomaly, and fulfill the
desired task,
but needs later follow-up activity by a system administrator or an SAP CC SAP
CC application administrator to avoid erroneous terminations in the future.
The administrators plan a follow-up activity to take into account the anomaly
and to determine the appropriate timeframe to perform preventive actions.
The administrators of the SAP CC systems may perform troubleshooting operations
relating to the following warning log messages:
| Warning Log Message |
Possible Impacts |
| "Unregister" operation has been interrupted due to a timeout |
The unregister operation will be retried until it can be completed.
|
| Activation process (with provider contracts) is already running. The request is ignored. |
Any new chargingContractActivate operation request sent by external systems will be
ignored by the SAP CC Core Server system
|
| Activation process (with subscriptions) is already running. The request is ignored. |
Any new activateAll operation request sent by external systems will be ignored by
the SAP CC Core Server system
|
| Activation process of {0} objects is already running. The request is refused. |
The operation request is refused.
|
| Admin XML Proxy received an execution request for the operation {0} which is unknown |
The request will be ignored.
|
| All rater instances received the order to start the Cleanup process. However, some
of these rater instances could not comply with the order. |
Some rater instances may not have started the execution of the Cleanup process.
|
| All rater instances received the order to stop the Activation process. However, some
of these rater instances could not comply with the order. |
Some rater instances may not have stopped the execution of the Activation process.
|
| All rater instances received the order to stop the Allowances Purge mechanism. However,
some of these rater instances could not comply with the order. |
Some rater instances may not have stopped the execution of the Allowances Purge mechanism.
|
| All rater instances received the order to stop the Cleanup process. However, some
of these rater instances could not comply with the order. |
Some rater instances may not have stopped the execution of the Cleanup process.
|
| Allowances Purge mechanism is already running. The request is ignored. |
Any new execution of the Allowances Purge mechanism will be ignored by the SAP CC
Core Server system.
|
| Allowances Purge mechanism is already running. The request is refused. |
The request will be refused.
|
| Audit field INSTANCE_ID with the value [{0}] has been truncated to [{1}] |
Some audit data will be lost.
|
| Audit field MESSAGE with the value [{0}] has been truncated to [{1}] |
Some audit data will be lost.
|
| Audit field OPERAND_REFERENCE with the value [{0}] has been truncated to [{1}] |
Some audit data will be lost.
|
| Audit field OPERATION_NAME with the value [{0}] has been truncated to [{1}] |
Some audit data will be lost.
|
| Audit field OPERATOR_NAME with the value [{0}] has been truncated to [{1}] |
Some audit data will be lost.
|
| Authentication attempt from [{0}] using the Web Services was refused because the authentication
data is invalid |
The operation request will be rejected by the SAP CC system.
|
| Authentication attempt with login [{0}] from [{1}] using the Web Services and Single
Sign-On was refused because the login is incorrect |
The operation request will be rejected by the SAP CC system.
|
| Authentication attempt with login [{0}] from [{1}] was refused because the SAP CC
user credentials are not valid |
The operation request is rejected by the SAP CC system.
|
| Authentication attempt with login [{0}] from [{1}] was refused because the SAP CC
user is locked |
The operation request is rejected by the SAP CC system.
|
| Authentication attempt with login [{0}] from [{1}] was refused because the SAP CC
user is not allowed to perform the operation |
The operation request is rejected by the SAP CC system.
|
| Authentication attempt with login [{0}] from [{1}] was refused because the login or
password is incorrect |
The operation request is rejected by the SAP CC system.
|
| Authentication attempt with login [{0}] from [{1}] was refused because the login or
the password is incorrect |
The operation request is rejected by the SAP CC system.
|
| Authentication attempt with login [{0}] from [{1}] was refused because the password
has expired |
The operation request is rejected by the SAP CC system.
|
| Authentication attempt with login [{0}] from [{1}] was refused because the provided
session [{2}] is unknown |
The operation request is rejected by the SAP CC system.
|
| Authentication attempt with login [{0}] from [{1}] was refused because the user does
not have the Message Charging Client role |
The operation request is rejected by the SAP CC system.
|
| Authentication attempt with login [{0}] from [{1}] was refused because the user session
[{2}] does not belong to the SAP CC user |
The operation request is rejected by the SAP CC system.
|
| Authentication attempt with login [{0}] from [{1}] was refused. Reason: {2} |
The operation request is rejected by the SAP CC system.
|
| Authentication attempt without credential from [{0}] was refused because authentication
is required |
The operation request is rejected by the SAP CC system.
|
| Authentication request was received from address {0} corresponding to a client application
whose version is unknown |
Some features of the client application might not work correctly.
|
| Authentication request was received from address {0} with a client version ({1}) different
from the SAP CC system version ({2}) |
Some features of the client application might not work correctly.
|
| Bad effective date {0} for tax {1}, ignoring this tax code |
The tax rate for the tax code will not be available in the system
|
| Cannot discover the dispatcher instances of the SAP CC system using the UDP discovery
function |
This instance of the SAP CC system will use information from the boot configuration
to determine a list of dispatcher instances of the same system.
|
| Cannot insert Web security policy reference in the following WSDL: \n{0} |
|
| Cannot insert the Web security policy in the following WSDL: \n{0} |
|
| Cannot publish the list of available dispatchers to the internal clients |
|
| Cannot put the data in the cache because it is larger than the cache |
The data will not be stored in the cache. If it is required, it will be fetched from
the back-end database.
This will have an impact on performance.
|
| Cannot put the provider contract in the data cache because it is larger than the cache |
The provider contract will not be stored in the cache. If it is required, it will
be fetched from the back-end database system.
This will have an impact on performance.
|
| Cannot put the rating data in the cache because it is larger than the cache |
The rating data will not be stored in the cache. If it is required, it will be fetched
from the back-end database system.
This will have an impact on performance.
|
| Cannot put the subscription in the cache because it is larger than the cache |
The subscription will not be stored in the cache. If it is required, it will be fetched
from the back-end database system.
This will have an impact on performance.
|
| Cannot send the change list to current destination due to error: {0}. |
The change list is not applied on the configured destination(s).
|
| Cannot send unregistration request to dispatcher instances |
The quality of Charging and Guiding Services is degraded until the issue resolution.
|
| Cannot start the activation process (with provider contracts) because a rerating process
is currently running |
chargingContractActivate operation will be ignored.
|
| Cannot start the activation process (with subscriptions) because a rerating process
is currently running |
The activateAll operation will be ignored.
|
| Cannot unmarshall operations with the NOP OFF framework, check your configuration |
The requested operation will not be executed.
|
| Cleanup process is already running. The operation request is refused and not dispatched
to the rater instances of the system |
The CleanupAllOp operation requests will be ignored by the dispatcher instances.
|
| Cleanup process is already running. The operation request is refused. |
The CleanupAllOp operation requests will be ignored by the updater instances.
The start_cleanup command of SAP CC Admin+ will not be usable.
|
| Concurrent master dispatcher detected: dispatcher [{0}] ([{1}]) will restart |
This instance will not be available during the restart sequence.
|
| Connection ({0}) with an unknown system ID requests to register |
The requesting instance will start.
|
| Connection ({0}) with an unknown system ID requests to start |
The requesting instance will start.
|
| Connection ({0}) with old protocol requests to register |
The version declared by the requesting instance will be used.
|
| Connection ({0}) with old protocol requests to start |
The version declared by the requesting instance will be used.
|
| Connection to the master dispatcher instance is down: Activation process is stopped |
Some provider contracts may not have been activated in customer master data.
|
| Connection to the master dispatcher instance is down: Cleanup operation is stopped |
Some subscriber accounts may not have been cleaned.
|
| Connection to the master dispatcher is down: Activation is stopped |
Some subscriptions may not have been activated in customer master data.
|
| Connection to the master dispatcher is down: the Allowances Purge mechanism is stopped |
All expired allowances will not be purged from the system.
|
| Counter snapshot count is not the same for all subscriptions/contracts |
|
| Counter snapshot is set to {0} in the database. Value {1} from the instance configuration
will be ignored. |
For instance:
If the counter snapshot count in the database is greater than the value of the COUNTER_SNAPSHOT_COUNT system parameter,
then it will not be possible to rerate from this extra counter snapshot that exists
in the system.
If the counter snapshot count in the database is lower than the value of the COUNTER_SNAPSHOT_COUNT system parameter,
then the system will propose a rerating of more days than what exists in the system.
|
| Data file [{0}] cannot be cleaned because the cleaning queue is full |
The data file is not archived and will not be available for the bulkloader instance
or for the third-party system.
|
| Directory [{0}] has not been loaded by the database |
The bulkloader instance will try again to load those files on the next schedule.
|
| Dispatcher instance cannot stop because a timeout has been reached due to a concurrent
operation |
The services provided by the dispatcher instance might be unavailable.
|
| Error occurred while receiving an asynchronous response for the transport web service:
{0} |
No transport request will be updated.
|
| Exception occurred while stopping the Charging output Integration Framework |
The data files may have not been closed properly.
Depends on the CIF configuration of the bulkloader.
|
| Expiration alert process already running. Request ignored. |
fireExpirationAlerts operation will be ignored.
|
| Expiration alert process already running. Request ignored. |
fireExpirationAlerts operation will be ignored.
|
| Forbidden entity resolution request for publicId=[{0}] and serviceId=[{1}] from [{2}]:[{3}]
- could be an XXE attack |
The message on the XML over HTTP communication channel (HCI) is ignored by the SAP
CC system.
|
| Guider instance is not configured to store the unique identifier of subscriber accounts
in the guiding cache |
The vertical scalability of the rater instances will not be optimal.
|
| Incompatibility between tax rate and tax code for tax {0}, ignoring this tax code |
The tax rate for the tax code will not be available in the system
|
| Instance [{0}] ([{1}]) is re-registered. Previous register connection is [{2}]. |
The connection was down between this instance and the instance that has just been
re-registered.
|
| Instance stopping and starting again for an internal reason |
This instance will not be available during the restart sequence.
|
| Instance {0} is not authorized to register because its system ID {1} is invalid |
The requesting instance will not start.
|
| Instance {0} is not authorized to start because its system ID {1} is invalid |
The requesting instance will not start.
|
| Instance {0} is still associated with a partition |
Some requests may not be answered.
|
| Invalid CIF configuration: inconsistent number of channels between bulkWriter "{0}"
({1} channels) and bulkReader "{2}" ({3} channels) |
Some output data files generated by the specified bulkWriter function in the rater
instances
will not be processed by the corresponding bulkReader function in the bulkloader instances.
|
| Invalid ISO 3166 file; Reason: {0}. |
This instance of the SAP CC Core Server system will not start.
|
| Invalid notification {0} for the JCo publisher |
The notification will be published through the error channel configured for the JCo
publisher.
|
| Invalid recurrence [{0}] for {1} scheduler |
The recurrence for the scheduler was not changed.
|
| Invalid tax rate for tax {0}, ignoring this tax code |
The tax rate for the tax code will not be available in the system
|
| Invalidation of the cache has been performed after a down connection to the master
dispatcher |
There will be an impact on performance while the cache is being reloaded from the
back-end database.
|
| Invalidation of the cache has been performed after the re-connection to the master
dispatcher |
There will be an impact on performance while the cache is being reloaded from the
back-end database.
|
| Master dispatcher emptied the guiders map |
The Guiding Service is not available.
|
| Master dispatcher emptied the raters map |
The rating service is not available.
|
| Maximum size of {0} bytes reached during the counter snapshot insertion for subscription/contract
[{1}]: {2} snapshot(s) between {3} and {4} have not been inserted into the database. |
The counter snapshot(s) for this subscription/contract are stored as erroneous in
the database between the 2 dates specified in the log message.
|
| No more {0} instance in the map |
The business and technical services of the instances of the specified type are not
provided.
|
| Operation {0} is stopped because the connection limit is reached |
The operation has not completed.
|
| Prefix for parameter names is missing in the CIF configuration for the {0} CIF processor.
Change the system settings. |
In the SAP CC Core Server system, this instance will start but the system parameters
for this CIF processor
will not be available when using the SAP CC Admin+ and the SAP CC Cockpit user interfaces
or the SAP CC APIs.
|
| Rater instance is not configured to use the unique identifier of subscriber accounts
for workload distribution |
The vertical scalability of the rater instances will not be optimal.
|
| Request handler queue is full for {0} |
The requests will be rejected while the queue is full.
|
| Retention period for rerating ({0} days) is greater than the retention period for
expired allowances ({1} days) |
Expired allowances may be deleted by the Allowances Purge mechanism while they are
still usable
by the chargeable items rerating process.
This could result in invalid results during the execution of the chargeable items
rerating process.
|
| Retry to publish the list of available dispatchers to the internal clients |
|
| SAP CC user [{0}] (from [{1}]) is not allowed to use the technical interface |
The operation request is rejected by the SAP CC system.
|
| SCIM REST API cannot be enabled because the Web Services are not secured |
|
| Scheduler cannot refresh the instance {0} of the system |
The instance will not be refreshed.
|
| Stop to check the status of the {0} (the timeout is reached, process has started at
{1}) |
|
| Stopping to waiting for {0} connection(s) to be closed due to timeout: {1}. |
|
| The SLD server was not recognized |
The SAP CC system cannot confirm that the SLD registration has been taken into account.
|
| The connection to the {0} can be closed, the {1} is already unregistered (Process
has started at {2}) |
|
| The connection to the {0} cannot be close because {1} has not be unregistered (Process
has started at {2}) |
|
| Threshold of {0} bytes reached during the counter snapshot insertion for subscription/contract
[{1}]: snapshot size is {2}/{3} bytes. |
If nothing is done, a following counter snapshot will reach the maximum size of a
counter snapshot and the rerating service will be compromised.
|
| Transport request cannot be executed due to error: {0}. |
|
| Transport requests execution already running. Request ignored. |
The execution of transport requests will be ignored.
|
| Transport scheduler execution error |
The transport requests execution has not been performed.
|
| Unable to receive {0} {1} due to exceeded message size during warm-up of the partition
{2} |
The requested data will not be warmed up and the instance may have to load this data
from the database.
|
| Unable to send {0} object(s) due to exceeded message size ({1}) |
The requesting instance will not receive the data and may have to load this data from
the database.
|
| Warm-up of the {0} data cache stopped because the cache is too small |
All the objects will not be stored in the cache. If one of the missing objects is
required, it will be fetched from
the back-end database. This will have an impact on performance.
|
| {0} is not an instance of the system ID {1} but an instance of system ID {2} |
The requesting instance will not start.
|
| {0} is not an instance of the system ID {1} but an instance of system ID {2} |
The requesting instance will not start.
|
| {0} is not authorized to register because the timeout of {1}ms has been reached due
to a concurrent operation |
The services provided by the specified instance are not available.
|
| {0} is not authorized to start because a timeout has been reached due to a concurrent
operation |
The new instance is not started.
|
| {0} is not authorized to unregister because the timeout of {1}ms has been reached
due to a concurrent operation |
The services provided by the specified instance might be unavailable.
|
| {0} session start operation(s) refused because the subscriber account has already
more than {1} started session(s). |
The operation is refused.
|
| {0} timeout(s) occurred. Maximum allocated handling time recorded since {1}: {2} ms. |
The SAP CC Core Server system may have finished processing the request(s) but the
remote client did not receive the answer(s) because of a client-side timeout.
|
| {0}s map is empty after a down connection |
The services provided by the specified instance type are not available.
|
