Index of com.sap.SCC.ct

Index Log Message Description Impacts Actions Information
0 (ERROR) Invalid system properties for logging and tracing settings. Degraded mode is set temporarily.

Some of the system properties set in the startup configuration file are invalid for this instance of the SAP CC system to set up the logging and the tracing functions.

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 will load the final configuration settings from the SAP CC Core Database.

Check the JVM option javaParameters in the startup configuration file (jstart.config) of the instance of the SAP CC system.

Check the system properties that configure the logging and the tracing functions during the first phase of the launch. See the SAP CC System Parameter Reference to know the correct values.

Example

-Dls.trc.severity=PATH

Correct these system properties

Re-launch the instance of the SAP CC system

You can set up the following system properties in the JVM option:

  • ls.app.severity
  • ls.sys.severity
  • ls.trc.severity
  • ls.app.destination
  • ls.sys.destination
  • ls.trc.destination
  • ls.trc.domain
  • ld.console.formatter
  • ld.file1.enabled
  • ld.file1.name
  • ld.file1.size
  • ld.file1.setsize
  • ld.file1.formatter
  • ld.file2.enabled
  • ld.file2.name
  • ld.file2.size
  • ld.file2.setsize
  • ld.file2.formatter
  • ld.file3.enabled
  • ld.file3.name
  • ld.file3.size
  • ld.file3.setsize
  • ld.file3.formatter
  • ld.file4.enabled
  • ld.file4.name
  • ld.file4.size
  • ld.file4.setsize
  • ld.file4.formatter
  • ld.file5.enabled
  • ld.file5.name
  • ld.file5.size
  • ld.file5.setsize
  • ld.file5.formatter

Note

Consult the SAP CC System Parameter Reference to determine the values allowed for these system properties. The ranges of values are the same.

1 (INFO) {0} ({1}) is started

The unique instance of the SAP CC Communications Taxing Server system has successfully started.

2 (INFO) OS process identifier is [{0}]

The startup process for the SAP CC Communications Taxing Server system has started. The operating system process identifier is logged for information.

3 (WARNING) OS process identifier not available

The startup process for the SAP CC Communications Taxing Server system has started. The operating system process identifier could not be determined dynamically.

This warning has no impact on the SAP CC system.

Nothing to do.

4 (INFO) Starting the SAP CC Communications Taxing Server system...

The unique instance of the SAP CC Communications Taxing Server system is starting its services.

5 (INFO) {0} platform on {1}

The versions of the Java Virtual Machine (JVM) and Operating System (OS) used on the machine that host the SAP CC Communications Taxing Server system.

6 (INFO) SAP CC Communications Taxing Server system is started

The unique instance of the SAP CC Communications Taxing Server system has successfully started.

7 (INFO) Stopping the SAP CC Communications Taxing Server system...

The unique instance of the SAP CC Communications Taxing Server system is shutting down its services.

8 (INFO) SAP CC Communications Taxing Server system is stopped

The unique instance of the SAP CC Communications Taxing Server system has successfully stopped.

9 (FATAL) SAP CC Communications Taxing Server system cannot be initialized: {0}

The unique instance of the SAP CC Communications Taxing Server system could not start due to an error during the initialization.

  • Check the error reason dynamically added to this log message by the SAP CC system
  • Check the previous log messages related to errors
  • Fix the configuration

10 (FATAL) SAP CC Communications Taxing Server system cannot start due to an internal error: {0}

The unique instance of the SAP CC Communications Taxing Server system could not start due to an internal error.

Check the error message dynamically added to this log message by the SAP CC system.

Troubleshoot your SAP CC Communications Taxing Server system to identify a possible cause:

  • Verify the configuration of the SAP CC system
  • Analyze the information in the previous log messages related to errors
  • Analyze the technical information in the trace messages
  • Correct the error(s)
  • Re-launch the instance of the system

Otherwise:

  • Enable and configure the generation of traces
  • Set up the trace severity threshold to PATH
  • Re-launch the SAP CC Communications Taxing Server system
  • Analyze the technical information in the trace messages
  • Correct the error(s)
  • Re-launch the SAP CC system

11 (FATAL) SAP CC Communications Taxing Server system cannot start due to a JCo communication error: {0}

The unique instance of the SAP CC Communications Taxing Server system could not start due to an error in the JCo communication

Troubleshoot your SAP CC Communications Taxing Server system to identify a possible cause:

  • Verify the configuration of the JCo connection
  • Analyze the information in the previous log messages related to errors
  • Analyze the technical information in the trace messages
  • Correct the error(s)
  • Re-launch the instance of the SAP CC system

Otherwise:

  • Enable and configure the generation of traces
  • Set up the trace severity threshold to PATH
  • Re-launch the SAP CC Communications Taxing Server system
  • Analyze the technical information in the trace messages
  • Correct the error(s)
  • Re-launch the SAP CC system

12 (FATAL) SAP CC Communications Taxing Server system cannot start due to an I/O error: {0}

The unique instance of the SAP CC Communications Taxing Server system could not start due to an I/O error.

Troubleshoot your SAP CC Communications Taxing Server system to identify a possible cause:

  • Verify the configuration of the SAP CC system
  • Analyze the information in the previous log messages related to errors
  • Analyze the technical information in the trace messages
  • Correct the error(s)
  • Re-launch the instance of the SAP CC system

Otherwise:

  • Enable and configure the generation of traces
  • Set up the trace severity threshold to PATH
  • Re-launch the SAP CC Communications Taxing Server system
  • Analyze the technical information in the trace messages
  • Correct the error(s)
  • Re-launch the SAP CC system

13 (INFO) Sending payload to SLD {0}

The SAP CC Communications Taxing Server system is connected to the SLD on the configured URL.

14 (ERROR) Cannot determine local host name due to: {0}

The SAP CC system is preparing data for the payload to be sent to the preconfigured SLD. However, the IP address of the local host could not be determined dynamically by the application.

The payload will not be sent to the configured SLD.

  • Check the error message dynamically added to this log message by the SAP CC system
  • Check the previous log messages related to errors
  • Fix the network configuration of the host

15 (WARNING) SID cannot be determined, sending [{0}] as SID

The SAP CC system is preparing data for the payload to be sent to the preconfigured SLD. However, the system identifier (SID) could not be determined dynamically by the application.

A default SID value will be used

  • Check the error message
  • Fix the configuration of the SID for this system

16 (WARNING) Cannot send SLD payload due to an invalid URL: {0}

The SAP CC system is trying to send the payload to the configured SLD. However, the SLD URL is invalid.

The payload will not be sent to the configured SLD.

Verify and fix the URL configured for the SLD.

17 (WARNING) Cannot send SLD payload to SLD [{0}] due to an I/O error: {1}

An I/O error occurred when trying to send the payload to the configured SLD. The reason is given in the error message.

The payload will not be sent to the configured SLD.

  • Check the error message
  • Fix the configuration of the SID for this system

18 (INFO) SLD updated by the SAP CC Communications Taxing Server system

The unique instance of the SAP CC Communications Taxing Server system has successfully sent its payload to the configured SLD. The SLD has been updated.

19 (WARNING) Using default configuration file: {0}

The SAP CC Communications Taxing Server system has not been configured to use a customized configuration file.

The default configuration file will be used.

Check that the JVM option sapct.config is filled in and corresponds to a valid configuration file.

20 (ERROR) Error occurred on RFC connection [{0}]: {1}

The RFC listener function in the SAP CC Communications Taxing (CT) Server system has encountered an abnormal error in one of its JCo connections.

The error will not be processed. Some JCo messages or answers may not have been received by the client application(s).

  • Verify the error message
  • Check the status of the JCo client
  • Check the JCo configuration of the SAP CC Communications Taxing Server system

21 (ERROR) Exception occurred on RFC connection [{0}]: {1}

The RFC listener function in the SAP CC Communications Taxing (CT) Server system has encountered an exception in one of its JCo connections.

The exception will not be processed. Some JCo messages or answers may not have been received by the client application(s).

  • Verify the error message
  • Check the status of the JCo client
  • Check the JCo configuration of the SAP CC Communications Taxing Server system

22 (INFO) EZTax configuration:\n>> Library version: {0}\n>> Database version: {1}\n>> Database path: {2}\n>> Override file: {3}\n>> Log file count: {4}>

This message displays information related to the BillSoft® EZTax library used by the SAP CC Communications Taxing Server system.

23 (ERROR) Error occurred for TXBIT [{0}]; Error code {1}: {2}

The RFC listener function in the SAP CC Communications Taxing (CT) Server system has encountered an error. An error has been inserted in the JCo error table.

The billable item identified by the specified TXBIT will not be taxed. The JCo client will need to retry the operation.

  • Check the details dynamically reocrded in the error log message
  • Check the status of the JCo client
  • Check the JCo configuration of the SAP CC Communications Taxing Server system

24 (ERROR) Error occurred for TXBIT [{0}]; Error code [{1}]: {2}

The RFC listener function in the SAP CC Communications Taxing (CT) Server system has encountered an error. An error has been inserted in the JCo error table.

The billable item identified by the specified TXBIT will not be taxed. The JCo client will need to retry the operation.

  • Verify the error message
  • Check the status of the JCo client
  • Check the JCo configuration of the SAP CC Communications Taxing Server system

25 (ERROR) EZTax error occurred: {0}

The SAP CC Communications Taxing Server system has encountered an error in the use of the Billsoft EZTax library during the determination of a location code.

The tax information returned may be missing or incomplete.

  • Verify the error message recorded
  • Check the EZTax configuration of the SAP CC Communications Taxing Server system

26 (ERROR) No tax information but there are [{0}] tax details

An inconsistency was found in the JCo update function for EZTax. No tax information was found for the billable item (BIT), but tax details exist. An error has been inserted in the JCo error table.

The tax information returned may be missing or incomplete.

  • Verify the error message
  • Verify the JCo error table

27 (ERROR) No tax details but there are [{0}] rows of tax information

An inconsistency was found in the JCo update function for EZTax. Tax information was found for the billable item (BIT), but tax details do not exist. An error has been inserted in the JCo error table.

The tax information returned may be missing or incomplete.

  • Verify the error message
  • Verify the JCo error table

28 (ERROR) No tax detail for the tax information of TXBIT [{0}]

The tax information for the identified billable item (TXBIT) is incomplete due to missing tax details. An error has been inserted in the JCo error table.

The tax information returned may be missing or incomplete.

  • Verify the error message
  • Verify the JCo error table

29 (ERROR) Cannot match [{0}] tax detail(s) to tax information

An inconsistency was found in the JCo update function for EZTax. Some tax details are not consistent with the tax information. An error has been inserted in the JCo error table.

The tax information returned may be missing or invalid.

  • Verify the error message
  • Verify the JCo error table

30 (ERROR) Writing of the EZTax Log data has been interrupted due to error: {0}

The SAP CC Communications Taxing (CT) Server system could not write to the EZTax Log file. The process has been interrupted. An error has been inserted in the JCo error table.

The EZTax Log file may be incomplete.

  • Verify the error message
  • Verify the JCo error table

31 (ERROR) Cannot write the EZTax Log data in file due to error: {0}

The SAP CC Communications Taxing Server system could not write into the EZTax Log file. The process has abort due to an execution error. An error has been inserted in the JCo error table.

The EZTax Log file may be incomplete.

  • Verify the error code
  • Verify the JCo error table

32 (ERROR) Value of ORIGN must be set for TXBIT [{0}]

The transaction identified by the specified TXBIT is missing the Origin property (ORIGN). This property is mandatory for tax computation. An error has been inserted in the JCo error table.

The tax information returned may be missing or incomplete.

  • Verify the error message
  • Verify the JCo error table

33 (ERROR) Value of ORITY for TXBIT [{0}] cannot be [{1}]. It must be one of 'P', 'N' or 'S'

The transaction identified by the specified TXBIT has an invalid Origin Flag property (ORITY). This property must be 'P' for P-code, 'N' for NPANXX or 'S' for State code. An error has been inserted in the JCo error table.

The tax information returned may be missing or incomplete.

  • Verify the error message
  • Verify the JCo error table

34 (ERROR) Value of TERMN must be set for TXBIT [{0}]

The transaction identified by the specified TXBIT is missing the Termination property (TERMN). This property is mandatory for tax computation. An error has been inserted in the JCo error table.

The tax information returned may be missing or incomplete.

  • Verify the error message
  • Verify the JCo error table

35 (ERROR) Value of TERTY for TXBIT [{0}] cannot be [{1}]. It must be one of 'P', 'N' or 'S'

The transaction identified by the specified TXBIT has an invalid Termination Flag property (TERTY). This property must be 'P' for P-code, 'N' for NPANXX or 'S' for State code. An error has been inserted in the JCo error table.

The tax information returned may be missing or incomplete.

  • Verify the error message
  • Verify the JCo error table

36 (ERROR) Value of CHRGT must be set for TXBIT [{0}]

The transaction identified by the specified TXBIT is missing the Service Address property (CHRGT). This property is mandatory for tax computation. An error has been inserted in the JCo error table.

The tax information returned may be missing or incomplete.

  • Verify the error message
  • Verify the JCo error table

37 (ERROR) Value of CHRTY for TXBIT [{0}] cannot be [{1}]. It must be one of 'P', 'N' or 'S'

The transaction identified by the specified TXBIT has an invalid Service Address Flag property (CHRTY). This property must be 'P' for P-code, 'N' for NPANXX or 'S' for State code. An error has been inserted in the JCo error table.

The tax information returned may be missing or incomplete.

  • Verify the error message
  • Verify the JCo error table

38 (ERROR) Value of CUSTY for TXBIT [{0}] cannot be [{1}]. It must be one of 'B', 'R', 'I' or 'S'

The transaction identified by the specified TXBIT has an invalid Customer Type property (CUSTY). This property must be 'B' for Business Customer, 'R' for Residential Customer, 'I' for Industrial Customer or 'S' for Senior Citizen Customer. An error has been inserted in the JCo error table.

The tax information returned may be missing or incomplete.

  • Verify the error message
  • Verify the JCo error table

39 (ERROR) Value of INVDT must be set for TXBIT [{0}]

The transaction identified by the specified TXBIT is missing the Invoice Date property (INVDT). This property is mandatory for tax computation. An error has been inserted in the JCo error table.

The tax information returned may be missing or incomplete.

  • Verify the error message
  • Verify the JCo error table

40 (ERROR) Value of SALEF for TXBIT [{0}] cannot be [{1}]. It must be one of 'R' or 'S'

The transaction identified by the specified TXBIT has an invalid Client Resale Flag property (SALEF). This property must be 'S' for Sale or 'R' for Resale. An error has been inserted in the JCo error table.

The tax information returned may be missing or incomplete.

  • Verify the error message
  • Verify the JCo error table

41 (ERROR) Value of INCCD for TXBIT [{0}] cannot be [{1}]. It must be one of 'I' or 'O'

The transaction identified by the specified TXBIT has an invalid Inc-Code property (INCCD). This property must be 'I' for Inside an incorporated city area or 'O' for Outside an incorporated city area. An error has been inserted in the JCo error table.

The tax information returned may be missing or incomplete.

  • Verify the error message
  • Verify the JCo error table

42 (ERROR) Value of REGUL for TXBIT [{0}] cannot be [{1}]. It must be one of 'R' or 'U'

The transaction identified by the specified TXBIT has an invalid Regulated/Unregulated Flag property (REGUL). This property must be 'R' for Regulated in the state of sale or 'U' for Unregulated in the state of sale. An error has been inserted in the JCo error table.

The tax information returned may be missing or incomplete.

  • Verify the error message
  • Verify the JCo error table

43 (ERROR) Value of TELTY for TXBIT [{0}] cannot be [{1}]. It must be one of 'C', 'D' or 'P'

The transaction identified by the specified TXBIT has an invalid Telecom Type property (TELTY). This property must be 'C' for Calls, 'D' for Debit Card Calls or 'P' for Point of sale. An error has been inserted in the JCo error table.

The tax information returned may be missing or incomplete.

  • Verify the error message
  • Verify the JCo error table

44 (ERROR) Value of SERVC for TXBIT [{0}] cannot be [{1}]. It should be empty or one of 'D' or 'L'

The transaction identified by the specified TXBIT has an invalid Service Class Indicator property (SERVC). This property must be empty, 'D' for Primarily Long Distance or 'L' for Primarily Local. An error has been inserted in the JCo error table.

The tax information returned may be missing or incomplete.

  • Verify the error message
  • Verify the JCo error table

45 (ERROR) Value of FACIL for TXBIT [{0}] cannot be [{1}]. It should be empty or one of 'F' or 'N'

The transaction identified by the specified TXBIT has an invalid Facilities Based Flag property (FACIL). This property must be empty, 'F' for Facilities based or 'N' for Non-Facilities based. An error has been inserted in the JCo error table.

The tax information returned may be missing or incomplete.

  • Verify the error message
  • Verify the JCo error table

46 (ERROR) Value of FRANC for TXBIT [{0}] cannot be [{1}]. It should be empty or one of 'F' or 'N'

The transaction identified by the specified TXBIT has an invalid Franchise Based Flag property (FRANC). This property must be empty, 'F' for Franchise based or 'N' for Non-Franchise based. An error has been inserted in the JCo error table.

The tax information returned may be missing or incomplete.

  • Verify the error message
  • Verify the JCo error table

47 (ERROR) Value of BUSCL for TXBIT [{0}] cannot be [{1}]. It should be empty or one of 'C' or 'I'

The transaction identified by the specified TXBIT has an invalid Business Class Indicator property (BUSCL). This property must be empty, 'C' for CLEC or 'I' for ILEC. An error has been inserted in the JCo error table.

The tax information returned may be missing or incomplete.

  • Verify the error message
  • Verify the JCo error table