Library Table of Contents Index Previous Next Comments

Examining the ContentReporter server log file

Understanding the "cs-comment" field return codes

About the ContentReporter return codes  Top

Three of the ContentReporter server components (the parser, the sorter, and the SQL bulk uploader) record return codes in the "cs-comment" field of the ContentReporter server log file. The return codes help you to identify problems and to understand the ContentReporter server's activities.

The parser return codes  Top

The ContentReporter parser processes collected log files. The parser return codes record information about the parser's activities. The parser return code value in the "cs-comment" field is "Parser return error code n" (where" n" is a numeric value from 0 to -12). The following table describes the parser return codes in the ContentReporter server log file.

Return Code

Description

Internal Code

0

The parser successfully parsed the log file.

SUCCESS

-1

The parser was unable to allocate enough memory to parse the log file.

ERR_MEMORY_ALLOCATION_FAILED

-2

There was a problem accessing (or related to) the stored log file folder.

ERR_COULD_NOT_OPEN_OUTPUT_FILE

-3

There was a problem accessing (or related to) the stored log file folder.

ERR_COULD_NOT_OPEN_LOG_FILE

-4

The log file contained an invalid header.

ERR_INVALID_LOG_FILE_HEADER

-5

There was a problem accessing (or related to) the stored log file folder.

ERR_COULD_NOT_OPEN_CSV_FILE

-6

The log file contained an unknown header field.

ERR_UNKNOWN_HEADER_FIELD

-7

There was a problem related to the datatypes.dat file in the folder:

..\Network Appliance\ContentReporter\

jakarta-tomcat\webapps\DataCollector

ERR_COULD_NOT_OPEN_DATA_FILE

-8

There was a problem accessing (or related to) the stored log file folder.

ERR_COULD_NOT_OPEN_CTL_FILE

-9

There was a problem accessing (or related to) the stored log file folder.

ERR_COULD_NOT_OPEN_SQL_FILE

-10

The log file was empty.

ERR_EMPTY_LOG_FILE

-11

The log file contained more than the maximum number of allowed error lines.

ERR_MAX_ERRORS

-12

The parser did not process the log file because the log file format changed at some point in the log file.

ERR_LOG_FMT_CHANGED_IN_LOG

The sorter return codes  Top

The ContentReporter sorter sorts and groups the log file data it receives from the ContentReporter parser. The sorter return codes record information about the sorter's activities. The sorter return code value in the "cs-comment" field is "crsort complete, returning n" (where "n" is a numeric value from 0 to -10). The following table describes the sorter return codes in the ContentReporter server log file.

Return Code

Description

0

The sorter successfully completed the sorting task.

-1

The ContentReporter server machine did not have enough memory for the sorter to complete the task.

-2

The sorter could not open its output file (".srt" extension). Possible causes:

  • The file may be in use
  • Not enough disk space to create it

-3

The sorter could not open the ContentReporter server log file. Possible causes:

  • The file may be in use
  • Not enough disk space to create it

-4

The sorter could not open its input CSV file generated by the parser.

To learn more about this, see the parser return error code -5 in The parser return codes.

-5

The sorter could not open the format file generated by the parser.

To learn more about this, see The parser return codes.

-6

The sorter could not open the "datatypes.dat" file in the ContentReporter server machine folder:

..\Network Appliance\ContentReporter\jakarta-tomcat\webapps\DataCollector

-7

The sorter could not open the format file generated by the parser.

To learn more about this, see The parser return codes.

-8

The sorter received one or more incorrect command line arguments. This is caused by an internal ContentReporter problem.

-9

The sorter received one or more incorrect command line arguments. This is caused by an internal ContentReporter problem.

-10

The sorter received one or more incorrect command line arguments. This is caused by an internal ContentReporter problem.

The SQL bulk uploader return codes  Top

The SQL bulk uploader return codes record information about the bulk updates to the database. The bulk uploader return code value in the "cs-comment" field is "Bulk load return: n" (where "n" is a numeric value from 0 to -4). The following table describes the bulk uploader return codes in the ContentReporter server log file.

Return Code

Description

0

The bulk upload is successful.

-1

There is a driver error.

-2

There is a connection error.

-3

A bulk copy program (bcp) error has occurred. The bcp may have rejected one row or may have totally failed. The user should check the log file to find out which bcp error has occurred.

-4

The bulk uploader has an error releasing its connection.

Library Table of Contents Index Previous Next Comments