Job Management Partner 1/Performance Management - Agent Option for Enterprise Applications Description, User's Guide and Reference

11.4 Messages

This section explains the messages issued by PFM - Agent for Enterprise Applications and the actions to be taken.

KAVF14000-I
Agent Collector has started. (host=host-name, service=service-ID)

Startup or initialization of the Agent Collector service has been completed.

(S)

Starts collecting SAP system performance data.

KAVF14001-I
Agent Collector has stopped. (host=host-name, service=service-ID)

The Agent Collector service has stopped for one of the following reasons: termination was requested by execution of the jpcspm stop (jpcstop) command, the Windows service terminated, or a signal interrupt occurred.

In the case of a signal interrupt, this message is preceded by the KAVF14151-E message indicating the signal reception event and supplemental signal number.

(S)

Stops the Agent Collector service.

KAVF14002-E
Agent Collector failed to start. (rc=maintenance-code)

The Agent Collector service cannot continue because startup or initialization of the Agent Collector service failed.

(S)

Stops the Agent Collector service.

(O)

Check the immediately preceding message in syslog (in UNIX), in the Windows event log (in Windows), or in the common message log, and then take appropriate action.

KAVF14100-I
Connected to the SAP system. (sid=SAP-system-ID)

RFC connection has been established with the SAP system.

(S)

Resumes initialization of the Agent Collector service.

KAVF14103-I
Reconnected to the SAP system. (sid=SAP-system-ID)

RFC connection has been re-established with the SAP system. This message is issued when connection had already been established with the SAP system since the Agent Collector service started but was broken for some reason, and now the connection has been re-established.

(S)

Resumes initialization of the Agent Collector service.

KAVF14105-I
The connection to the SAP system was closed. (sid=SAP-system-ID)

RFC connection with the SAP system has been closed.

This message is issued when processing based on a termination request is to be executed or when the RFC handle is to be released due to a transient error during operation.

(S)

If processing based on a termination request is to be executed, the system terminates the Agent Collector service.

If the RFC handle is to be released due to a transient error during operation, the system waits until the next connection.

KAVF14121-E
An error occurred in the RFC API. (name-of-API-resulting-in-error)

An RFC function call resulted in an error. For an RFC API error during connection establishment with the SAP system, the KAVF14127-E or KAVF14128-E message is issued instead of this message. Following this message, the KAVF14122-E message providing detailed error information is output to the common message log. Possible causes of this error are as follows:

The SAP system is not active.

The SAP system cannot accept an RFC request due to heavy workload.

There is a problem in the network settings.

(S)

When this error occurs during startup processing:
Stops the Agent Collector service.

When this error occurs subsequent to startup processing (during operation):
Continues monitoring. The system closes any open RFC handle and re-establishes connection when the next collection begins. Updating of the performance data that was supposed to take place during this collection period will be delayed.

(O)

When this error occurs during startup processing:
Re-evaluate the status, such as the connection parameters set in the Agent Collector service startup initialization file (jpcagt.ini), the operating status of the SAP system, and the network status, correct the error, and then restart.

When this error occurs subsequent to startup processing (during operation):
A fatal error, such as SAP system shutdown, may have occurred. Check the KAVF14122-E message output to the common message log before or after the time of this error and resolve the problem.
Before correcting an error in the connection parameters in the Agent Collector service startup initialization file (jpcagt.ini), check if PFM - Agent for Enterprise Applications was stopped by the jpcspm stop (jpcstop) command.
If this error occurred due to planned termination (such as for SAP system maintenance purposes), you can ignore this message. When the SAP system restarts, PFM - Agent for Enterprise Applications will re-establish connection and continue with monitoring.

KAVF14122-E
RFC_ERROR_INFO_EX: GROUP=error-group-name, KEY=error-key, MESSAGE=error-message

This message is output following the KAVF14121-E, KAVF14127-E, or KAVF14128-E message. It provides details of the RFC API error. The meanings of the values displayed in the message are as follows:

GROUP: 3-byte integer identifying the key

KEY: Code (maximum of 32 bytes) that identifies the error

MESSAGE: Text (maximum of 512 bytes) that describes the error (may include linefeed codes)

These are the member values in the RFC_ERROR_INFO_EX structure obtained by the GetRfcLastErrorEx function that returns the RFC API error. For details about RFC, see the documentation for the SAP system.

(S)

This message is preceded by the KAVF14121-E, KAVF14127-E, or KAVF14128-E message; see that message for the system processing.

(O)

Check the KAVF14121-E, KAVF14127-E, or KAVF14128-E message displayed before this message, and eliminate the cause of the error.

KAVF14125-E
An error occurred in the function module of the SAP system. (name-of-function-module-resulting-in-error)

An SAP system function module returned an unexpected error code. This message is followed in the common message log by the KAVF14126-E message that provides detailed error information. The cause of the error is defined for each function module that was called. For details about the cause of the error, see the KAVF14126-E message.

(S)

When this error occurs during startup processing:
Stops the Agent Collector service.

When this error occurs subsequent to startup processing (during operation):
Continues monitoring. The system postpones updating of the performance data that was supposed to take place at this time.

(O)

When this error occurs during startup processing:
Check the version of the SAP system. BAPI_XMI_LOGON may result in an error during authorization checking.
In such a case, grant the SXMI_PROD authorization object to the user who is attempting to establish connection.

When this error occurs subsequent to startup processing (during operation):
Check the KAVF14126-E message output to the common message log before or after this error occurred, and resolve the problem.

KAVF14126-E
BAPIRET2: TYPE=message-type, ID=message-class, NUMBER=message-number, MESSAGE=message-text

This message provides the details of an error in the function module (BAPI). The meanings of the values displayed in the message are as follows:

TYPE: One-byte character indicating the severity level of the message (S: normal, E: error, W: warning, I: information, A: forced termination)

ID: Message class (maximum of 20 bytes)

NUMBER: Error code (maximum of 3 bytes) that identifies the error

MESSAGE: Text (maximum of 220 bytes) that describes the nature of the error

These are the member values in the BAPIRET2 structure that stores a BAPI error. For details about BAPI, see the documentation for the SAP system. For details about the specification of the called BAPI, see the documentation for the SAP system's object navigator (SE80), BAPI browser (BAPI) or the SAP system.

(S)

This message is preceded by the KAVF14125-E message; see that message for system processing.

(O)

Check the KAVF14125-E message displayed before this message and eliminate the cause of the error.

KAVF14127-E
Cannot connect to the SAP system. (name-of-the-function-resulting-in-error)

A connection error occurred during connection establishment with the SAP system. For an RFC API error during connection establishment with the SAP system, this message or the KAVF14128-E message is issued instead of the KAVF14121-E message. Following this message, the KAVF14122-E message providing detailed error information is output to the common message log.

Possible causes of this error are as follows:

The SAP system is not active.

The SAP system cannot accept an RFC request due to heavy workload.

There is a problem in the network settings.

The destination information is invalid (there is an error in the information, such as host name or system number).

(S)

When this error occurs during startup processing:
Stops the Agent Collector service.

When this error occurs subsequent to startup processing (during operation):
Continues monitoring. The system closes any open RFC handle and re-establishes connection the next time performance data is collected. Updating of the performance data that was supposed to take place during this collection period will be delayed.

(O)

When this error occurs during startup processing:
Re-evaluate the status, such as the connection parameters set in the Agent Collector service startup initialization file (jpcagt.ini), the operating status of the SAP system, and the network status, correct the error, and then restart.

When this error occurs subsequent to startup processing (during operation):
A fatal error, such as SAP system shutdown, may have occurred. Check the KAVF14122-E message output to the common message log before or after the time of this error and resolve the problem.
Before correcting an error in the connection parameters in the Agent Collector service startup initialization file (jpcagt.ini), check if PFM - Agent for Enterprise Applications was stopped by the jpcspm stop (jpcstop) command.
If this error occurred due to planned termination, such as for SAP system maintenance purposes, you can ignore this message. When the SAP system restarts, PFM - Agent for Enterprise Applications re-establishes connection and continues monitoring.

KAVF14128-E
Cannot log on to the SAP system. (name-of-the-function-resulting-in-error)

A logon error occurred during connection establishment with the SAP system. For an RFC API error during connection establishment with the SAP system, this message or the KAVF14127-E message is issued instead of the KAVF14121-E message. Following this message, the KAVF14122-E message providing detailed error information is output to the common message log. Possible causes of this error are as follows:

The logon information is invalid (there is an error in the information, such as client name, user name, or password).

The user's password has been changed.

The user does not have the required authorization.
This refers to the authorization (S_RFC) needed to establish RFC connection with the function module (BAPI).

An extended password containing lower-case letters is defined in the SAP system based on SAP NetWeaver 7.0 or later, but N (do not use extended passwords) was specified in the EXTPWD instance information item.

(S)

When this error occurs during startup processing:
Stops the Agent Collector service.

When this error occurs subsequent to startup processing (during operation):
Continues monitoring. The system closes any open RFC handle and re-establishes connection the next time performance data is collected. Updating of the performance data that was supposed to take place during this collection period will be delayed.

(O)

When this error occurs during startup processing:
Re-evaluate the settings, such as the connection parameters in the Agent Collector service startup initialization file (jpcagt.ini) and the user definitions in the SAP system, correct the error, and then restart.

When this error occurs subsequent to startup processing (during operation):
Possible causes include deletion of the user or a change in the password. Check the KAVF14122-E message output to the common message log before or after this error occurred, and resolve the problem.
Before correcting an error in the connection parameters in the Agent Collector service startup initialization file (jpcagt.ini), check if PFM - Agent for Enterprise Applications was stopped by the jpcspm stop (jpcstop) command.

KAVF14129-E
SAP instance=SAP instance-name

This message displays the name of the SAP instance resulting in a communication error when the KAVF14121-E or KAVF14127-E message has been displayed.

(S)

This message is preceded by the KAVF14121-E or KAVF14127-E message; see that message for the system processing.

(O)

Check the KAVF14121-E or KAVF14127-E message displayed before this message, and eliminate the cause of the error.

KAVF14131-E
The system resources are insufficient.

There is a shortage in system resources, such as memory or handles. The resources required by Performance Management are insufficient or the system is unstable due to another application's resource leakage.

(S)

When this error occurs during startup processing:
Stops the Agent Collector service.

When this error occurs subsequent to startup processing (during operation):
The Agent Collector service attempts to continue monitoring as much as possible. A series of operations or requests is rejected, and updating of the performance data that was supposed to take place at this time is delayed.

(O)

Identify the problem as soon as possible and recover the system status. Secure the system resources by re-estimating the required resources as well as re-evaluating the memory expansion and kernel parameters.

KAVF14133-E
An error occurred in an internal function. (func=function-name, rc=maintenance-code)

A function error occurred in an internal function interface.

(S)

If this error occurs during startup processing, the Agent Collector service terminates abnormally. If the error occurs after completion of startup processing (during operation), the Agent service continues monitoring. However, a series of operations or requests is rejected and updating of the performance data that was supposed to take place at this time is delayed.

(O)

If the error occurs frequently and cannot be recovered, collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter that describes error handling procedures in the Job Management Partner 1/Performance Management User's Guide.

KAVF14134-E
A file or directory cannot be accessed. (path)

An error (other than a shortage of disk space) occurred during a general file access, such as a creation, deletion, read, or write operation. Possible causes of this error are as follows:

The file does not exist.

There is no access permission.

The file system has been unmounted.

The specified file path is a directory path (invalid environment).

(S)

When this error occurs during startup processing:
Stops the Agent Collector service.

When this error occurs subsequent to startup processing (during operation):
The Agent Collector service attempts to continue monitoring as much as possible. A series of operations or requests is rejected, and updating of the performance data that was supposed to take place at this time is delayed.

(O)

Check the status of the file indicated by path in the message and correct the error.

KAVF14136-E
The content of the Agent Collector service startup initialization file is invalid. (section=section-name, subsection=subsection-name, label=label-name)

The Agent Collector service startup initialization file (jpcagt.ini) contains an invalid specification.

(S)

Cancels startup processing and stops the Agent Collector service.

(O)

Check the section-name, subsection-name, and label-name displayed in the message, correct the invalid specification in the Agent Collector service startup initialization file (jpcagt.ini), and then restart the Agent Collector service.

KAVF14150-E
The system environment is invalid. (rc=maintenance-code)

The system environment is invalid. This error occurs when installation and setup are incomplete or system files and registry information have been deleted or modified erroneously.

(S)

Terminates the Agent Collector service abnormally.

(O)

Back up all necessary data, uninstall the system, and then re-install it. If this does not resolve the problem, collect maintenance data and then contact the system administrator. For details about how to collect maintenance data, see the chapter that describes error handling procedures in the Job Management Partner 1/Performance Management User's Guide.

KAVF14151-E
The processing was interrupted by a signal. (signal=signal-number)

The Agent Collector service stopped because a process termination signal was accepted as a result of an event such as system shutdown.

(S)

Stops the Agent Collector service.

KAVF14152-W
Reception of a signal caused the service to stop. (signal=signal-number)

In UNIX, reception of the indicated signal caused the Agent Collector service to stop the processing.

(S)

Stops the Agent Collector service processing.

KAVF14160-I
The performance data will now be collected. (sid=SAP-system-ID, server=SAP-instance-name)

The Agent Collector service has started collecting performance data. At this point, all collection-related initialization processing has been completed.

(S)

Collects performance data.

KAVF14161-E
The SAP instance does not exist. (sid=SAP-system-ID, server=SAP-instance-name)

No instance information was found in the connection-target SAP system due to an error in the specification of the SAP system ID or SAP instance name in the [Agent]-[Target] subsection in the Agent Collector service startup initialization file (jpcagt.ini).

(S)

When this error occurs during startup processing:
Stops the Agent Collector service.

When this error occurs subsequent to startup processing (during operation):
Continues monitoring. The system delays the updating of performance data that was supposed to take place at this time.

(O)

Re-evaluate the SAP instance name (value of the SERVER parameter in the Target section) specified in the Agent Collector service startup initialization file (jpcagt.ini). The SAP instance name is usually in the format host-name_system-ID_system-number.

KAVF14171-W
The performance data could not be updated. (record-ID[.field-name])

Collection of performance data failed. This message is preceded by a message that indicates the direct cause of the error, such as a communication error or function module (BAPI) error. This message displays the affected record ID and field name, separated by a period. The displayed record ID and field name are PFM - Manager names.

(S)

Continues with performance data collection. Updating of the performance data is delayed until the next collection request.

(O)

Eliminate the cause of the error.

KAVF14172-W
The performance data cannot be collected now.

This message indicates that performance data is not being collected due to a communications error. Performance data cannot be collected at this agent until output of the KAVF14103-I message that indicates that connection to the SAP system has been recovered, followed by output of the KAVF14160-I message indicating completion of initialization.

(S)

Attempts to reconnect with the SAP system at each collection request. Note that the subsequent connection errors are not reported. When connection with the SAP system is recovered, the system displays the KAVF14103-I message.

(O)

Check the KAVF14121-E and KAVF14122-E communication error messages displayed before this message, and eliminate the cause of the error.

KAVF14173-W
The performance data cannot be reported. (record-ID[.field-name])

The connection-target SAP system does not support this performance data.

No data source corresponding to the performance data was found in the connection-target SAP system.

This message displays the record ID and field name, separated by a period, of the unsupported performance data. The displayed record ID and field name are PFM - Manager names.

(S)

Stops monitoring for this performance data and resumes initialization of agent.

(O)

Check the supported performance data. For details about the supported performance data, see 9. Records.

KAVF14174-W
During collection of data, the number of instances of a multi-instance record exceeded the maximum. (record=record-ID, limit=maximum-value, instance=instances-count)

During data collection, the number of instances for a multi-instance record exceeded the maximum value. The excess instances are being discarded.

(S)

Resumes processing.

(O)

Check and, if necessary, revise the target monitor settings.

KAVF14175-W
The specified monitor set name is invalid. (monitor-set-name)

One of the following may apply to the settings in the [Agent] - [PI_UMP] folder for the properties of the Agent Collector service:

The MONITOR_SET property has not been set.

The monitor set name that was set is undefined in the SAP system.

The defined monitor set name is invalid.

(S)

Cancels collection of the User defined Monitor (Perf.) (PI_UMP) record and resumes processing.

(O)

Check in the [Agent] - [PI_UMP] folder for the properties of the Agent Collector service whether the monitor set name set in the MONITOR_SET property exists in the SAP system.

You can check the monitor set name by means such as transaction code RZ20. The monitor set name may be shown as monitor set. Note that the settings are case sensitive.

KAVF14176-W
The specified monitor name is invalid. (monitor-name)

One of the following may apply to the settings in the [Agent] - [PI_UMP] folder for the properties of the Agent Collector service:

The MONITOR_SET property has not been set.

The monitor name that was set is undefined in the SAP system.

The defined monitor name is invalid.

(S)

Cancels collection of the User defined Monitor (Perf.) (PI_UMP) record and resumes processing.

(O)

Check in the [Agent] - [PI_UMP] folder for the properties of the Agent Collector service whether the monitor name set in the MONITOR_SET property exists in the SAP system.

You can check the monitor name by means such as transaction code RZ20. The monitor name may be shown as monitor set. Note that the settings are case sensitive.

KAVF14177-W
The Performance data could not be collected. (record-ID, monitor-set-name, monitor-name, MTE-name)

Collection of the performance data indicated by the MTE name failed (BAPI error). This message is preceded by a message that indicates the specific cause of the error, such as a communication error or function module (BAPI) error.

(S)

Cancels collection of the performance data indicated by the MTE name and resumes processing. Updating of the performance data that was to be acquired at this time will be delayed until the next collection time.

(O)

Check the message output immediately preceding this message and eliminate the cause of the error.

KAVF14178-W
It failed to issue JP1 system event or Agent event extension.

The Agent Collector service failed to issue a JP1 system event or an extended agent event. Any subsequent event issuance failures will not be reported.

(S)

The Agent Collector service resumes processing.

(O)

Check if JP1/Base is running on the same host as for PFM - Agent for Enterprise Applications. Also check and, if necessary, revise the settings by referencing the chapter that describes operation monitoring linked with the integrated management product (JP1/IM) in the Job Management Partner 1/Performance Management User's Guide. If the problem remains unresolved, collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter that describes error handling procedures in the Job Management Partner 1/Performance Management User's Guide.

KAVF14179-W
It failed to issue JP1 system event or Agent event extension, because Memory is insufficient.

The Agent Collector service failed to issue a JP1 system event or an extended agent event due to insufficient memory. The resources required by PFM are insufficient or the system is unstable due to resource leakage in another application.

(S)

The Agent Collector service resumes processing.

(O)

Identify the problem and recover the system status. Secure the necessary system resources by re-estimating the required resources as well as by expanding the memory.

KAVF14200-I
Usage:
jr3slget [-h application-server-host -s system-number]
[-c client -u user {-p password | -p2 extended password}
[-l language] [-codepage codepage]]
[-server sap-instance-name]
[-lasttime time-stamp-file]
[{-x log-file | -x2}]
[-cnf environment-parameter-file]
[-help] [-v]

This message displays the usage of the jr3slget command when the -help option has been specified.

(S)

Terminates the command normally.

KAVF14201-I
Usage:
jr3alget [-h application-server-host -s system-number]
[-c client -u user {-p password | -p2 extended password}
[-l language] [-codepage codepage]]
[-c client -u user -p password [-l language] [-codepage codepage]]
[-ms monitor-set-name -mn monitor-name]
[-lasttime time-stamp-file]
[{-x log-file | -x2}]
[-cnf environment-parameter-file]
[-help] [-v]

This message displays the usage of the jr3alget command when the -help option has been specified.

(S)

Terminates the command normally.

KAVF14210-I
The command ended normally.

This message indicates that the command has terminated normally. This message is displayed only when the -v option was specified in the command.

(S)

Terminates the command with termination code 0.

KAVF14211-E
The command ended abnormally. (exit=termination-code)

This message indicates that the command has terminated abnormally.

(S)

Terminates the command with the displayed termination-code.

(O)

Check the cause message that was displayed before this message.

KAVF14212-I
Connected to the SAP system.

RFC connection has been established with the SAP system. This message is displayed only when the -v option was specified in the command.

(S)

Following this message, the system displays the KAVF14213-I and KAVF14215-I messages indicating the parameter information used for connection, and then resumes processing.

KAVF14213-I
SAP system data: ashost=application-server-host, sysnr=system-number

Following the KAVF14212-I message during establishment of RFC connection, this message displays the parameters used as the RFC connection information (destination). This message is displayed only when the -v option was specified in the command.

(S)

Following the KAVF14212-I message, the system displays the parameter information used for connection establishment.

KAVF14215-I
SAP user data: client=client, user=user, lang=language, codepage=code-page

Following the KAVF14212-I message during establishment of RFC connection, this message displays the parameters used as the RFC connection information (logon information). This message is displayed only when the -v option was specified in the command. If the language and code page were omitted, no values are set in lang= and codepage=. This message does not display the password.

(S)

Following the KAVF14212-I message, the system displays the parameter information used for connection establishment.

KAVF14216-I
Logged on to the external interface. (interface=interface-name, version=version)

The system successfully logged on to the external interface of the SAP system. This message displays the interface name and version of the logon target. This message is displayed only when the -v option was specified in the command.

(S)

Resumes processing.

KAVF14220-E
An error occurred in the RFC API. (RFC-API-name-resulting-in-error)

An RFC API call resulted in an error.

(S)

Following this message, the system displays the KAVF14221-E message that provides detailed error information. The system may also display a supplemental message on the errors that can be classified into categories. The system then cancels execution of the command.

(O)

Check any subsequent messages, eliminate the cause of the error, and then re-execute the command.

KAVF14221-E
RFC_ERROR_INFO_EX: group=error-group-name, key=error-key, message=error-message

This message displays the details of an RFC API error. This message follows the KAVF14220-E message. The meanings of the values displayed in the message are as follows:

group: 3-byte integer identifying the key

key: Code (maximum of 32 bytes) that identifies the error

message: Text (maximum of 512 bytes) that describes the error (may include linefeed codes)

These are the member values in the RFC_ERROR_INFO_EX structure obtained by the GetRfcLastErrorEx function that returns the RFC API error. For details about RFC, see the documentation for the SAP system.

(S)

Cancels execution of the command.

(O)

Correct the error and then re-execute the command.

KAVF14222-E
An error occurred in the function module of the SAP system. (function-module-name)

The function module (BAPI) of the SAP system returned an error.

(S)

Following this message, the system displays the KAVF14223-E or KAVF14224-E message that provides detailed error information. The system may also display a supplemental message on the errors that can be classified into categories. The system then cancels execution of the command.

(O)

Check any subsequent messages, eliminate the cause of the error, and then re-execute the command.

KAVF14223-E
BAPIRET2: type=message-type, id=message-class, number=message-number, message=message-text

When an error is detected in the function module (BAPI), this message is displayed immediately after the KAVF14222-E message. The meanings of the values displayed in the message are as follows:

type: One-byte character indicating the severity level of the message (S: normal, E: error, W: warning, I: information, A: forced termination)

id: Message class (maximum of 20 bytes)

number: Error code (maximum of 3 bytes) that identifies the error

message: Text (maximum of 220 bytes) that describes the nature of the error

These are the member values in the BAPIRET2 structure that stores a BAPI error. For details about BAPI, see the documentation for the SAP system. For details about the specification of the called BAPI, see the documentation for the SAP system's object navigator (SE80), BAPI browser (BAPI) or the SAP system.

(S)

Cancels execution of the command.

(O)

Correct the error and then re-execute the command.

KAVF14224-E
RFC_EXCEPTION: error-cause-code

When an error is detected in a function module by an RFC exception, this message is displayed following the KAVF14222-E message.

(S)

Cancels execution of the command.

(O)

Correct the error and then re-execute the command.

KAVF14225-E
Cannot connect to the SAP system.

A communications error occurred while RFC connection with the SAP system was being established. This message immediately follows the KAVF14220-E and KAVF14221-E messages that provide the name of the function resulting in the error and detailed information. Possible causes of this error are as follows:

The specified RFC connection inventory is invalid (such as the host name cannot be resolved or the specified system number is invalid).

The SAP system is not active.

The SAP system cannot accept an RFC request due to heavy workload.

There is a problem in the network settings.

(S)

Following this message, the system displays the KAVF14227-E and KAVF14229-E messages that provide the parameter information used for connection establishment. The system then cancels execution of the command.

(O)

Check the destination specified as the RFC connection information to re-evaluate the operating status of the SAP system and the network status, correct the error, and then re-execute the command.

KAVF14226-E
Cannot connect to the SAP system, because an attempt to log on failed.

A logon error occurred when RFC connection was being established with the SAP system. This message immediately follows the KAVF14220-E and KAVF14221-E messages that provide the name of the function resulting in the error and detailed information. Possible causes of this error are as follows:

The specified RFC connection inventory is invalid (such as the specified user does not exist or the specified password is invalid).

The user has been locked out.

The user does not have the correct S_RFC authorizations.

An extended password containing lower-case letters is defined in the SAP system based on SAP NetWeaver 7.0 or later, but the specified connection information (-p option and PASSWD label in the environment parameters file) does not support extended passwords.

(S)

Following this message, the system displays the KAVF14227-E and KAVF14229-E messages that provide the parameter information used for connection establishment. The system then cancels execution of the command.

(O)

Determine the user specified for the RFC connection information and check for undefined information, password expiration, lockout, and authorizations, correct the error, and then re-execute the command.

KAVF14227-E
SAP system data: ashost=application-server-host, sysnr=system-number

In the event of an RFC connection error, following the KAVF14225-E or KAVF14226-E message, this message displays the parameters that were used as the RFC connection information (destination).

(S)

Cancels execution of the command.

(O)

Correct the error and then re-execute the command.

KAVF14229-E
SAP user data: client=client, user=user, lang=language, codepage=code-page

In the event of an RFC connection error and following output of the KAVF14225-E or KAVF14226-E message, this message displays the parameters that were used as the RFC connection information (logon). If the language and code page were omitted, no values are set in lang= and codepage=. This message does not display the password.

(S)

Cancels execution of the command.

(O)

Correct the error and then re-execute the command.

KAVF14230-E
Cannot log on to the external interface. (interface=logon-target-interface-name, version=version)

A logon request for the external interface of the SAP system was rejected (BAPI error). This message is preceded by the KAVF14222-E and KAVF14223-E messages that provide the name of the function module (BAPI) resulting in the error and detailed information. Possible causes of this error are as follows:

The connection-target SAP system does not support this interface.

The user does not have the S_XMI_PROD authorization.

(S)

Cancels execution of the command.

(O)

Make sure that the release and patch level of SAP Basis (SAP WebAS) in the connection-target SAP system meet the requirements. If the BAPI_XMI_LOGON function module resulted in an error during authorization checking, grant the SXMI_PROD authorization object to the user being used for RFC connection.

KAVF14231-E
The specified server name is invalid. (specified-SAP-instance-name)

The SAP instance name specified by one of the following methods is undefined or invalid (BAPI error):

-server option of the jr3slget command

Environment parameters file (SERVER label of the TARGET section)

This message is preceded by the KAVF14222-E and KAVF14223-E messages that provide the name of the function module (BAPI) resulting in the error and detailed information.

(S)

Cancels execution of the command.

(O)

Check the specified SAP instance name and re-execute the command. You can use transaction code SM51 to check the SAP instance name. The SAP instance name is usually in the format host-name_system-ID_system-number. The SAP instance names are case-sensitive.

KAVF14232-E
The specified monitor set name is invalid. (specified-monitor-set-name)

The monitor set name specified by one of the following methods is undefined or invalid (BAPI error):

-ms option of the jr3alget command

Environment parameters file (MONITOR_SET label of the TARGET section)

This message is preceded by the KAVF14222-E and KAVF14223-E messages that provide the name of the function module (BAPI) resulting in the error and detailed information.

(S)

Cancels execution of the command.

(O)

Check the specified monitor set name and re-execute the command. You can use transaction code RZ20 to check the monitor set name. The monitor set name may be shown as monitor set. The monitor set names are case-sensitive.

KAVF14233-E
The specified monitor name is invalid. (specified-monitor-name)

The monitor name specified by one of the following methods is undefined or invalid (BAPI error):

-mn option of the jr3alget command

Environment parameters file (MONITOR label of the TARGET section)

This message is preceded by the KAVF14222-E and KAVF14223-E messages that provide the name of the function module (BAPI) resulting in the error and detailed information.

(S)

Cancels execution of the command.

(O)

Check the specified monitor name and re-execute the command. You can use transaction code RZ20 to check the monitor set name and monitor name. The monitor set name may be shown as monitor set. The monitor names are case-sensitive.

KAVF14240-E
The command execution will be terminated because the system resources are insufficient.

Processing cannot continue because of a memory shortage.

(S)

Cancels execution of the command.

(O)

Terminate an unneeded application or expand the memory, and then re-execute the command.

KAVF14241-E
A file or directory cannot be opened. (name-of-file-or-directory-resulting-in-error)

An error occurred during file or directory open or creation processing. If a relative path is shown in the message, it is the path from the work directory for the command. If you have specified a different work directory in the environment parameters file, it may be different from the current directory. Possible causes of this error are as follows:

The file or directory does not exist (when an existing file is opened).

The user executing the command does not have the permission to open this file or directory.

There are not enough system resources to create the file or directory.

(S)

Cancels execution of the command.

(O)

Check the permissions of the user executing the command and the status of the indicated path, correct the error, and then re-execute the command.

KAVF14242-E
The available free space is insufficient for extending the file or directory. (name-of-file-or-directory-resulting-in-error)

A disk space shortage occurred when the open file or directory space was to be extended. If a relative path is shown in the message, it is the path from the work directory for the command. If you have specified a different work directory in the environment parameters file, it may be different from the current directory. If an access error has occurred on the standard input/output, a null character string is displayed for name-of-file-or-directory-resulting-in-error.

(S)

Cancels execution of the command.

(O)

Increase the available space in the indicated file system or change the location where the file is to be created, and then re-execute the command.

KAVF14243-E
An error occurred during the accessing of the file or directory. (name-of-file-or-directory-resulting-in-error)

A general access to a file or directory resulted in an I/O error. If a relative path is shown in the message, it is the path from the work directory for the command. If you have specified a different work directory in the environment parameters file, it may be different from the current directory. If an access error has occurred on the standard input/output, a null character string is displayed for name-of-file-or-directory-resulting-in-error.

(S)

Cancels execution of the command.

(O)

Check the status of the indicated path, correct the error, and then re-execute the command.

KAVF14250-W
A specified environment parameter is invalid. (section=section-name, label=label-name)

The value of the environment parameter indicated by section-name and label-name is invalid in the environment parameters file. Possible causes of this error are as follows:

The value is too long.

The value contains an invalid character.

The specified numeric value is outside the permitted range.

(S)

Ignores the specified value and resumes processing. The command will not terminate abnormally as a result of this warning.

(O)

Re-evaluate the values specified in the environment parameters file. If you do not specify an environment parameters file with the -cnf option, the default environment parameters file (command-name.ini in the current directory) is referenced.

KAVF14251-E
A required option is missing.

A required option or an option that cannot be omitted due to a required combination of options is missing. For example, if you specify the -h option for RFC connection information, you cannot omit the -s option.

(S)

Cancels execution of the command.

(O)

Re-evaluate the command syntax and then re-execute the command.

KAVF14253-E
The option value is invalid. (option)

The indicated option value is invalid. Possible causes of this error are as follows:

The value is omitted.

The value is too long.

The value contains an invalid character.

The specified numeric value is outside the permitted range.

(S)

Cancels execution of the command.

(O)

Re-evaluate the command syntax and then re-execute the command.

KAVF14254-E
An option is invalid. (option)

The indicated option character string is invalid.

(S)

Cancels execution of the command.

(O)

Re-evaluate the command syntax and then re-execute the command.

KAVF14255-E
Mutually-exclusive options are specified.

Mutually-exclusive options are specified. For example, the -x and -x2 options for specifying the output destination cannot both be specified.

(S)

Cancels execution of the command.

(O)

Re-evaluate the command syntax and then re-execute the command.

KAVF14256-E
An option is duplicated. (option)

The indicated option cannot be specified more than once.

(S)

Cancels execution of the command.

(O)

Re-evaluate the command syntax and then re-execute the command.

KAVF14257-E
Mutually exclusive keys or section names are specified as environment parameters.

Mutually exclusive key section names are specified in the environment parameters file. The following is a possible cause of this error:

PASSWD and PASSWD2 are both specified, but these sections are mutually exclusive for specifying a password.

(S)

Cancels execution of the command.

(O)

Check and, if necessary, revise the settings in the environment parameters file.

KAVF14260-E
The specified RFC connection parameter (destination) is incomplete.

Processing cannot continue because arguments (-h and -s options) were omitted and the RFC-connection-information environment parameters are undefined or invalid in the environment parameters file. If you are omitting the arguments, make sure that the following items are defined correctly in the CONNECT section of the environment parameters file:

Application server host (ASHOST)

System number (SYSNR)

(S)

Cancels execution of the command.

(O)

Re-evaluate the values specified in the environment parameters file and then re-execute the command. If the environment parameters file is not specified with the -cnf option, the default environment parameters file (command-name.ini in the current directory) is used.

KAVF14261-E
The specified RFC connection parameter (logon) is incomplete.

Processing cannot continue because arguments (-c, -u, and -p options) were omitted and the RFC-connection-information environment parameters are undefined or invalid in the environment parameters file. If you are omitting the arguments, make sure that the following items are defined correctly in the CONNECT section of the environment parameters file:

Client (CLIENT)

User (USER)

Password (PASSWD)

(S)

Cancels execution of the command.

(O)

Check the values specified in the environment parameters file and then re-execute the command. If you do not specify an environment parameters file with the -cnf option, the default environment parameters file (command-name.ini in the current directory) is referenced.

KAVF14262-E
The specified target is incomplete.

For the jr3slget command:
Processing cannot continue because an argument (-server) was omitted and the target environment parameter is undefined or invalid in the environment parameters file. If you are omitting the argument, make sure that the following item is defined correctly in the TARGET section of the environment parameters file:
Application server (SERVER)

For the jr3alget command:
Processing cannot continue because arguments (-ms and -mn) were omitted and the target environment parameter is undefined or invalid in the environment parameters file. If you are omitting the arguments, make sure that the following items are defined correctly in the TARGET section of the environment parameters file:
Monitor set name (MONITOR_SET)
Monitor name (MONITOR)

(S)

Cancels execution of the command.

(O)

Check the values specified in the environment parameters file and then re-execute the command. If you do not specify an environment parameters file with the -cnf option, the default environment parameters file (command-name.ini in the current directory) is referenced.

KAVF14263-E
The specified output place is incomplete.

Processing cannot continue because the -x2 option was omitted and the output-target path in the X2PATH label of the EXTRACTFILE section is undefined or invalid in the environment parameters file.

(S)

Cancels execution of the command.

(O)

Check the values specified in the environment parameters file and then re-execute the command. If you do not specify an environment parameters file with the -cnf option, the default environment parameters file (command-name.ini in the current directory) is referenced.

KAVF14270-E
The environment parameter settings file cannot be accessed. (path-name-of-erroneous-environment-parameters-file)

The environment parameters file specified with the -cnf option is not accessible. If a relative path is shown in the message, it is relative to the current directory. Possible causes of this error are as follows:

The file does not exist.

The user executing the command does not have the read permissions.

(S)

Cancels execution of the command.

(O)

Check the permissions granted to the user executing the command and the status of the indicated path, correct the error, and then re-execute the command.

KAVF14271-W
The trace file cannot be accessed. (path-name-of-erroneous-trace-file)

An error occurred one or more times during a trace file open or write operation. It may be that no maintenance information was collected or that some maintenance information is missing. If the indicated path is a relative path, it is relative to the work directory for the command. If you have specified a different work directory in the environment parameters file, it may be different from the current directory. Possible causes of this error are as follows:

The file does not exist.

The user executing the command does not have the read or write permissions.

(S)

Resumes processing. The command will not terminate abnormally as a result of this warning.

(O)

Check the permissions granted to the user executing the command and the status of the indicated path, and then correct the error. You can use the environment parameters file to change the output destination of the trace file.

KAVF14272-E
The work directory cannot be changed. (work-directory)

The work directory cannot be changed to the path specified in the environment parameters file (value specified for the WORKDIR label in the COMMAND section). Possible causes of this error are as follows:

An invalid path was specified.

The specified value is not a directory.

The directory does not have the execution (search) permissions.

(S)

Cancels execution of the command.

(O)

Check the path specified in the environment parameters file (value specified for the WORKDIR label in the COMMAND section), correct the error, and then re-execute the command.

KAVF14273-I
The time-stamp file was initialized. (timestamp-file-name)

A new timestamp file was created and management information was initialized. This message is displayed the first time the command is executed with the -lasttime option specified (when the specified timestamp file does not exist). This message is displayed only when the -v option is specified in the command.

(S)

Terminates the command normally.

(O)

Differential information is output the next time the command is executed. Re-execute the command with the same timestamp file specified.

KAVF14274-E
The time-stamp file cannot be updated. (timestamp-file-name)

An unexpected error occurred when the timestamp file was updated. Because the system was unable to store the command result, correct differential records may not be reported the next time the command is executed (records may be duplicated in reports).

(S)

Cancels execution of the command.

(O)

Check the status of the path indicated by timestamp-file-name and then correct the error.

KAVF14275-I
Number of processing records: processed-records-count

This message shows the number of records reported by the command. This message is displayed only when the -v option was specified in the command.

(S)

Resumes processing.

KAVF14276-W
The specified output format column value is invalid. (specified-value)

The value specified for a COLUMN label is invalid in the FORMAT section of the environment parameters file.

(S)

Ignores the value of the corresponding column and resumes processing (fewer columns are displayed). This command is not cancelled as a result of this warning.

(O)

Specify a valid field ID in the COLUMN label of the FORMAT section in the environment parameters file. For details about the field ID, see 10. Commands. If you do not specify an environment parameters file with the -cnf option, the default environment parameters file (command-name.ini in the current directory) is referenced.

KAVF14277-I
The time-stamp file was updated. (timestamp-file-name)

The timestamp file was updated. This message is displayed only when the -v option was specified in the command.

(S)

Terminates the command normally.

KAVF14278-E
The time-stamp file format is invalid. (name-of-erroneous-timestamp-file)

The file specified with the -lasttime option is not a timestamp file. If the indicated file name is a relative path, it is relative to the work directory for the command. If you have specified a different work directory in the environment parameters file, it may be different from the current directory.

(S)

Cancels execution of the command.

(O)

Specify the correct timestamp file and then re-execute the command. If the timestamp file management information has been damaged due to a file access error, delete the timestamp file and re-create it.

[Contents][Back][Next]

[Trademarks]