Errors

The SAP CC system or a subcomponent can recover from error, but cannot complete the desired task due to the error. The SAP CC system is still usable, but corrective actions need to be performed by administrators. Refer also to the fatal error messges.

Resolution Plan and Troubleshooting

Immediate Correction Actions

The administrators do an immediate follow-up activity to determine the resolution and the corrective actions needed to be performed to avoid another erroneous termination in the future.

Error Messages

The administrators of the SAP CC systems may perform troubleshooting operations relating to the following error log messages:

Error Log Message	Possible Impacts
Activation process cannot activate [{0}] due to error: {1}	The contract may not have been activated, recurring and non-recurring fees may not have been all generated.
An error occurred during the generation of a thread dump file: {0}	The thread dump file will not be generated, and no information will thus be available for the execution context of the related thread.
An error occurred while purging file metadata from the Core database. Reason is: {0}.	Some metadata will not be purged.
An error occurred while recording file metadata in the Core database. {0} files could not be recorded. Reason is: {1}.	Metadata will not be recorded for the impacted data files. The data available in the "Analyze Item Files" web application will not be consistent for these data files.
B2B taxation place is not a number in VAT rule [{0}]	This instance of the SAP CC Core Server system will not start.
B2B taxation place is out of range in VAT rule [{0}]	This instance of the SAP CC Core Server system will not start.
B2B taxation place of the existing VAT rule [{0}] has changed	The new VAT rules are not imported in the SAP CC Core Server system.
B2C taxation place is not a number in VAT rule [{0}]	This instance of the SAP CC Core Server system will not start.
B2C taxation place is out of range in VAT rule [{0}]	This instance of the SAP CC Core Server system will not start.
B2C taxation place of the existing VAT rule [{0}] has changed	The new VAT rules are not imported in the SAP CC Core Server system.
CIF/RIF configuration settings not found	This rater instance of the SAP CC Core Server system will not start.
Cannot commit the request in database. Error code: [{0}], reason: {1}	All or a part of the operation has not been recorded.
Cannot configure a function of the SAP CC system	This bulkloader instance of the SAP CC Core Server system will not start.
Cannot connect to the SLD at the URL: {0}	The SLD payload will not be sent
Cannot contact the BART server to open the rerating session	The operations performed by BART are unavailable.
Cannot contact the BART server to start the rerating session	The operations performed by BART are unavailable.
Cannot determine the IP address of the host [{0}] specified in the parameter [{1}]	This dispatcher instance of the SAP CC Core Server system will not start.
Cannot finalize the parameter manager function; Reason: {0}
Cannot initialize the Batch Rating Group Assignment Processor function	This updater instance of the SAP CC Core Server system will not start.
Cannot initialize the Charging Service	This rater instance of the SAP CC Core Server system will not start.
Cannot initialize the Exportable Item Connector	This updater instance of the SAP CC Core Server system will not start.
Cannot initialize the External Service	This dispatcher instance of the SAP CC Core Server system will not start.
Cannot initialize the Internal Service	This dispatcher instance of the SAP CC Core Server system will not start.
Cannot initialize the Transaction File Processor: Cannot open the writing channel in [{0}].	The TFP is not initialized.
Cannot initialize the Transaction File Processor: I/O exception in [{0}]. The reason is {1}	The TFP is not initialized. The launching of the rater is aborted.
Cannot initialize the Transaction File Processor: Several files found for current transaction in [{0}].	The TFP is not initialized.
Cannot initialize the Transaction File Processor: The current file name [{0}] in [{1}] is malformed, its expected length is [{2}] characters.	The TFP is not initialized.
Cannot initialize the Transaction File Processor: The current file name [{0}] in [{1}] is malformed.	The TFP is not initialized.
Cannot initialize the multicast service	This bulkloader instance of the SAP CC Core Server system will not start.
Cannot initialize the network interfaces of the host machine	The instance communications will not work.
Cannot initialize the parameter manager function; Reason: {0}.	This instance of the SAP CC Core Server system will not start.
Cannot initialize the properties; Reason: {0}.	This dispatcher instance of the SAP CC Core Server system will not start.
Cannot initialize the system parameters. Reason is: {0}	This updater instance of the SAP CC Core Server system will not start.
Cannot initialize the tax service in this taxer instance	This taxer instance of the SAP CC Core Server system will not start.
Cannot initialize the tax system in this rater instance	This rater instance of the SAP CC Core Server system will not start.
Cannot initialize the tax system in this updater instance	This updater instance of the SAP CC Core Server system will not start.
Cannot load the bulk loader sources configuration due to an I/O error
Cannot load the bulk loader sources configuration due to an XML parsing error
Cannot load the bulk loader sources configuration due to an error in the parser configuration
Cannot load the charged item processor shell of the bulkloader	The bulkloader instance may not be completely functional. The parameters defined in the charged item processor shell configuration may not be accessible.
Cannot load the charged item processor shell of the rater	This rater instance may not be completely functional. The parameters defined in the charged item processor shell configuration may not be accessible.
Cannot load the charged item processor shell of the rater	This rater instance may not be completely functional. The parameters defined in the charged item processor shell configuration may not be accessible.
Cannot load the list of dispatcher instances from the boot configuration	This instance of the SAP CC Core Server system will not start.
Cannot load the notification policy configuration
Cannot load the rerate processor shell of the rater	This rater instance may not be completely functional. The parameters defined in the rerate processor shell configuration may not be accessible.
Cannot load the rerate processor shell of the rater	This rater instance may not be completely functional. The parameters defined in the rerate processor shell configuration may not be accessible.
Cannot load the shell configuration of the charged item processor function
Cannot load the shell configuration of the charged item processor function of the bulkloader instance	The bulkloader instance may not be completely functional. The parameters defined in the charged item processor shell configuration may not be accessible.
Cannot load the shell configuration of the rerate processor function
Cannot load the shell configuration of the transaction processor function
Cannot parse VAT rules file. Not enough fields in rule definition: {0}	This instance of the SAP CC Core Server system will not start.
Cannot parse VAT rules file; Error: {0}.	This instance of the SAP CC Core Server system will not start.
Cannot read European tax rates file; Error: {0}.	This instance of the SAP CC Core Server system will not start.
Cannot read tax policy file; Error: {0}.	This instance of the SAP CC Core Server system will not start.
Cannot read the log entries	The log extractor will not return the log entries.
Cannot reply to the remote client. Error code: [{0}], reason: {1}	The remote client may not receive the answer.
Cannot resend a renew reservation notification. Reason is: {0}	The client application (or system) will not receive the renew reservation notification and will not be able to manage properly the session-based charging services for certain end customers.
Cannot resend a spending status report. Reason is: {0}	The client application (or system) will not receive the spending status report and will not be able to manage properly the spending status monitoring services for certain end customers.
Cannot retrieve the bulkLoader sources configuration due to a parser configuration error	The bulkLoader sources configuration previously saved to the database will not be used in the current session.
Cannot retrieve the bulkLoader sources configuration due to an I/O error	The bulkLoader sources configuration previously saved to the database will not be used in the current session.
Cannot retrieve the bulkLoader sources configuration due to an XML parsing error	The bulkLoader sources configuration previously saved to the database will not be used in the current session.
Cannot retrieve the notification policy configuration due to an SQL error	The notification policy previously saved to the database will not be used in the current session
Cannot retrieve the notification policy configuration due to an XML parsing error	The notification policy previously saved to the database will not be used in the current session.
Cannot start due to previous errors	This instance of the SAP CC Core Server system will not start.
Cannot start the HTTP listener of the dispatcher instance	This dispatcher instance of the SAP CC Core Server system will not start.
Cannot start the activation process (with provider contracts) because it has not been possible to determine if a rerating process is running	The chargingContractActivate operation will not start.
Cannot start the activation process (with subscriptions) because it has not been possible to determine if a rerating process is running	The activateAll operation will not start.
Cannot stop the opened rerating session	The operations performed by BART are unavailable.
Cannot update the SLD due to an I/O error
Cannot update the notification policy configuration due to an SQL error	The notification policy will not be updated. The modifications to the notification policy will not be saved to the database.
Cannot warm up the cache because there is no space left	This instance of the SAP CC Core Server system will not start.
Cleanup operation fails on subscriber account {0} for session {1} and reservation {2} due to error: {3}	The operation is refused, it may be a cleanup operation or the operation that triggered the cleanup. The expired session is still attached to the subscriber account in the session history and may lead to other failures.
Cleanup process cannot clean [{0}] due to error: {1}	The sessions for this subscriber account cannot be removed from database. Further ratings on this subscriber account will be refused.
Country tax policy file not found in database	This instance of the SAP CC Core Server system will not start.
Data file [{0}] cannot be archived due to an error during cleaning	The data file is set in error ("cleanErr" file extension) and will not be available for the bulkloader instance or for the third-party system.
Database was not able to load some files from the directory [{0}]	Some of the files may not be loaded immediately in the back-end database. The bulkloader instance will attempt to load those files again on the next schedule.
Default B2B taxation place is empty in VAT rule [{0}]	This instance of the SAP CC Core Server system will not start.
Default B2B taxation place is not a number in VAT rule [{0}]	This instance of the SAP CC Core Server system will not start.
Default B2B taxation place is out of range in VAT rule [{0}]	This instance of the SAP CC Core Server system will not start.
Default B2B taxation place of the existing VAT rule [{0}] has changed	The new VAT rules are not imported in the SAP CC Core Server system.
Default B2C taxation place is empty in VAT rule [{0}]	This instance of the SAP CC Core Server system will not start.
Default B2C taxation place is not a number in VAT rule [{0}]	This instance of the SAP CC Core Server system will not start.
Default B2C taxation place is out of range in VAT rule [{0}]	This instance of the SAP CC Core Server system will not start.
Default B2C taxation place of the existing VAT rule [{0}] has changed	The new VAT rules are not imported in the SAP CC Core Server system.
Description is empty in VAT rule [{0}]	This instance of the SAP CC Core Server system will not start.
Description is too long in VAT rule [{0}]	The VAT rules are not imported in the SAP CC Core Server system.
Description of the existing VAT rule [{0}] has changed	The new VAT rules are not imported in the SAP CC Core Server system.
EU taxes file not found in database	This instance of the SAP CC Core Server system will not start.
EZTax base path not found (specified by the JVM option -D{0}=<eztax base path>)	This taxer instance of the SAP CC Core Server system will not start.
EZTax output path not found (specified by the JVM option -D{0}=<eztax output path>)	This taxer instance of the SAP CC Core Server system will not start.
Error occurred during the execution of the expiration alert process	The expiration alert process ended with an error status.
Error occurred during the refresh of the rater instances of the SAP CC system
Error occurred while sending the SLD payload
Error was raised in the core security module; Reason: {0}	This instance of the SAP CC Core Server system will not start.
Existing VAT rule [{0}] is missing	The new VAT rules are not imported in the SAP CC Core Server system.
File [{0}] cannot be processed completely because it is corrupted. Processed lines: {1}.	No line of the file has been processed.
Invalid system properties for logging and tracing settings. Degraded mode is set temporarily.	This instance of the SAP CC Core Server system did not apply the logging and tracing settings set in the startup configuration file. The instance will temporarily apply some degraded settings for the logging and tracing functions and continue the launching phase: It loads the final configuration settings from SAP CC Core Database.
Mandatory parameter [{0}] not found	This rater instance of the SAP CC Core Server system will not start.
Rater instance cannot send the expiration alert response because the connection to the client has been interrupted	The client application (or system) is not informed about the result of the expiration alert.
Rater instance cannot send the expiration alert response because the connection to the client is down	The client application (or system) is not informed about the result of the expiration alert.
Scheduler (triggering the expiration alerts) cannot communicate to the dispatcher instance	The client application is not aware of this expiration alert.
Some rater instances did not receive the order to start the Cleanup process before the timeout expiration with the following reason: [{0}]	Some rater instances may not have started the execution of the Cleanup process.
Some rater instances did not receive the order to stop the Activation process for provider contracts before the timeout expiration with the following reason: [{0}]	Some rater instances may not have stopped the execution of the Activation process for subscriptions.
Some rater instances did not receive the order to stop the Activation process for subscriptions before the timeout expiration with the following reason: [{0}]	Some rater instances may not have stopped the execution of the Activation process for subscriptions.
Some rater instances did not receive the order to stop the Allowances Purge mechanism before the timeout expiration with the following reason: [{0}]	Some rater instances may not have stopped the Allowances Purge mechanism.
Some rater instances did not receive the order to stop the Cleanup process before the timeout expiration with the following reason: [{0}]	Some rater instances may not have stopped the execution of the Cleanup process.
Some reachable servers did not acknowledge the fire expiration alerts order before timeout expiration with following reason: [{0}]	Some rater instances may not trigger the expiration alerts process.
Supplier country code is empty or invalid in VAT rule [{0}]	This instance of the SAP CC Core Server system will not start.
Supplier zone of the existing VAT rule [{0}] has changed	The new VAT rules are not imported in the SAP CC Core Server system.
The shared allowances cache could not be refreshed.
Transaction File Processor - Writing channel ({0}) writing error. Reason: {1}.	A new attempt will be made. If multiple attempts do not succeed, some transactions may be lost.
Unable to check if the activation process is running before launching the rerating process	The rerateBulk operation will not be performed.
VAT rule ID [{0}] already exists	This instance of the SAP CC Core Server system will not start.
VAT rule ID [{0}] is too long	The VAT rules are not imported in the SAP CC Core Server system.
VAT rule ID is empty in VAT rule definition: {0}.	This instance of the SAP CC Core Server system will not start.
Writing Channel [{0}] fell down and has been discarded. Available writing channel count: [{1}]	A writing channel has been lost.
Writing channel cannot be updated; Reason: {0}.	It can occurred during: the launch of the rater: The launching is aborted an operation: The writing channel is discarded
{0} request(s) were received late. Maximum delay recorded since {1}: {2} ms. Invalid configuration: increase client-side timeout or update parameter COLLECTOR_RTT to decrease server-side round-trip time according to your network average latency.	The SAP CC Core Server system may have finished processing the request(s) but the remote client application did not receive the answer(s) because of the client-side timeout.

See Also

• Fatal error messages
• Warning messages
• Security messages
• Index of com.sap.SCC.core_server