Other known problems
Miscellaneous troubleshooting items lists miscellaneous troubleshooting problems.
Area | Item |
---|---|
r3batch and
r3event : output contains unreadable
characters |
Symptom: When you enter the r3batch and
r3event commands interactively (for example, to export an SAP calendar) the
output is returned in UTF-8 format. |
Solution: To resolve this problem, you can either use a shell that supports the UTF-8 code page or redirect the output to a file and open it with a text editor that supports the UTF-8 format. | |
r3batch:
SAP jobs
contain quotation marks (") or reverse quotes
(ˋ) |
Symptoms: SAP jobs whose names
contain quotation marks or reverse quotes are not displayed in the pick list of the
Dynamic Workload Console.
-OR- You have an HCL Workload Automation job that tries
to submit an SAP job whose name
contains quotation marks, but it abends with an error. The following message might
be displayed:
|
Solution: In your SAP system, make a copy of the SAP job and assign it a name that does not contain quotation marks or reverse quotes. | |
r3batch:
SAP job
containing Arabic characters. |
Symptom: An SAP job abends when the job contains Arabic characters. |
Solution: If you run an SAP job that contains Arabic characters, you must set the local codepage of the agent workstation hosting the r3batch access method to the Arabic codepage. Refer to the twsmeth_cp keyword in the common options file, Defining the common options. | |
r3batch: error messages submitting a
job on dynamic agents. |
Symptom: When working with dynamic workstations and
performing actions such as: displaying a process chain, restarting a process chain, or
retrieving the spool list, the following messages might be displayed from the Dynamic Workload Console:
|
Solution: These messages might indicate that the requested action is not supported on dynamic workstations. Refer to the HCL Workload Automation Release Notes® for more information about HCL Workload Automation features and minimum required versions for compatibility. | |
r3batch: r3batch hangs when
performing actions from the Dynamic Workload Console. |
Symptoms: r3batch hangs when performing actions from the Dynamic Workload Console such selecting from a pick list, submitting a job, or similar actions that require connection to the SAP system. The HCL Workload Automation joblog might also contain multiple "Timer expired" messages. |
Solution: This problem is caused by the HCL Workload Automation logging and tracing component. Modify the r3batch.properties files. Locate the r3batch.trace.handlers.traceFile.MPFileSemKeyproperties setting, and then either comment this property setting out or use a different value. Choose any numeric value and retry the operation. | |
r3batch: Submit same process chain
in parallel fails. |
Symptom: The SAP system returns an error message RFC_ERROR_SYSTEM_FAILURE when starting an SAP process chain. |
Solution: Verify if the corrections stated in SAP note 1723482 are applied to your SAP Business Warehouse system or avoid running the same process chain more than once simultaneously. | |
r3batch: When you restart the process of a subchain, the status of the original process chain is not changed to active | Symptom: When you restart the process of a subchain, the status of the original process chain is not changed to active. |
Solution: Refer to SAP Note 1075876. | |
r3batch: Refresh an SAP process chain
after a kill action on a running job instance. |
Symptom: If you perform a kill action on an HCL Workload Automation job instance running on a dynamic workstation which monitors an SAP process chain, and then subsequently perform a Refresh operation on this job, the job fails. |
Solution: You cannot perform a Refresh operation after having performed a kill action on an HCL Workload Automation job instance running on a dynamic workstation which monitors an SAP process chain. Verify the status of the SAP process chain on the SAP system, and then set the HCL Workload Automation job status accordingly. | |
r3batch: Wrong characters are
displayed in the Criteria Manager profile description. |
Symptom: Special characters such as, < (less than), > (greater than), or the ' (apostrophe) specified in the Description field of the Create criteria profile dialog are displayed incorrectly. |
Solution: Avoid using special characters in the Description field when creating a new criteria profile. | |
r3evmon: monitoring events is not
started, stopped, or
performed |
Symptom: You cannot start or stop event monitoring, or event monitoring is not performed. |
Solution: Ensure that TWSuser is the owner of the
following files, and that the user has read and write permissions:
|
|
r3batch: monitoring SAP events is not
performed |
Symptom: The SAP event on which the event rule is based is neither monitored nor committed. |
Solution: Ensure that the extended agent workstation you specified in the SAP event definition exists. When you define an SAP event within an event rule, no check on the extended agent workstation is made: if the workstation does not exist, the event rule is saved and activated but it will never be resolved. | |
r3batch: monitoring SAP events is not
performed |
Symptom: With XBP 3.0, the SAP event is raised but HCL Workload Automation is not notified and therefore does not act as expected. |
Solution: Ensure that the SAP event was not excluded from logging in the SAP event history table. | |
r3batch: monitoring SAP events is not
performed |
Symptom: The SAP events on which the event rule is based are not monitored nor committed. |
Solution: The SAP events being
monitored are listed in the following file:
where
XAname is the name of the SAP extended agent
workstation. Check that the file is updated and contains the current monitoring
plan. The SAP events are indicated by the following keyword (one for each SAP event on the
same extended agent):
where:
For each configuration file, an
r3evmon process is started to
monitor the SAP events listed.
To start an r3evmon monitoring process for a specific extended
agent workstation, enter the following command. Note:
where:
|
|
r3batch: IDoc monitoring is not
performed |
Symptom: The events on which the event rule is based are not monitored or no event is generated during IDoc monitoring. |
Solution: The events being monitored are listed in the
following file:
where
XAname is the name of the SAP extended agent
workstation. It is the same file that is used to monitor SAP events in general.
Check that the file is updated and contains the current monitoring plan. The
events corresponding to the
IDOCEventGenerated event type are
indicated by the following keyword (one for each event on the same extended agent):
where:
For each configuration file, an |
|
r3evmon: monitoring SAP and IDoc events
increases memory
consumption |
Symptom: Memory consumption increases continuously during monitoring of IDoc and standard SAP events. |
Solution: Refer to SAP Notes® 1021071 and 1109413. | |
r3batch: Duplicated events generated
during IDoc
monitoring |
Symptom: The action defined in an event rule with
IDOCEventGenerated event type is unexpectedly repeated. |
Solution: Reset the start date and time for the
next monitoring loop. These values are stored in the following file:
where
XAname is the name of the SAP extended agent workstation.
Therefore you can either:
Use the following format for the start date and time:
For example:
Check the value of the idoc_no_history option:
|
|
r3batch: No event is generated
during IDoc
monitoring |
Symptom: The expected event actions are not triggered. |
Solution: Check the value of the idoc_no_history
option; if it is set to ON (default value), check the date and time in the
XAname_r3idocmon.cfg file. |
|
Error defining an internetwork dependency based on SAP event | Symptom: If you work with XBP 2.0, when you try to define
an internetwork dependency based on an SAP event, the
following error message is displayed:
|
Solution: Perform the following steps:
|
|
r3batch: error message when
scheduling SAP jobs |
Symptom: When creating an SAP job, the following message is
displayed while trying to view the details of an ABAP's variant:
|
Solution: This defect is caused by an error in an SAP function module. SAP describes this problem and possible solutions in the SAP Notes® 0351293 and 0116354. | |
r3batch: modify job step
error |
You change print parameters with the
BAPI_XBP_MODIFY_JOB_STEP function module, and subsequently, they
are incorrect. As a consequence, r3batch gets error 221:
The problem is solved by installing SAP Note 758829. |
r3batch: modify job step
error |
The BAPI_XBP_MODIFY_JOB_STEP function module always uses the name
of the logged-on user as the name for the step user. In this case, when submitting a
job with the -vX options, r3batch creates a job by
copying all the data from the original template, except the variant name of the first
step (which is provided as the option parameter). This procedure is usually referred
to as the "old copy". However, when adding a step to a new job, the XBP 2.0 interface
ignores the user parameter passed by r3batch . The problem is solved by installing SAP note 758829. |
r3batch: does not start after
installation on Windows™ |
Symptom: After installing or upgrading the SAP R/3 access
method to version 8.5 on a Windows™ operating
system, you try to start r3batch but nothing happens. The following
message is displayed:
|
Solution: Ensure that you applied the SAP Note 684106 to install the required Microsoft™ DLLs. | |
r3batch:
HCL Workload Automation
environment variables are not resolved when specified in the task string for an R/3
batch job. |
Symptom: When HCL Workload Automation environment variables are used in the task string for an R/3 batch job and the job is launched, the environment variables are not resolved. The exact string used to specify the variable is used instead. |
Solution: To leverage HCL Workload Automation environment
variables, you must modify the access method as follows:
|
|
@longlink file present in installation directory | Symptom: After installing HCL Workload Automation on a
computer with an AIX® operating system where a
master domain manager is already installed, a @longlink file containing the following
is present in the installation
directory:
|
Solution: The file can be ignored. It does not present any problems for the proper functioning of the product. | |
Job throttling does not start on HP-UX | Symptom: You try to start the job throttler and the
following error message is displayed:
|
Cause and Solution: Java™ version 1.5 does not start because there are symbolic links of Java™ version 1.4 libraries used by third party
products. For example, you might have /usr/lib/pa20_64/libjava.sl
linked to /opt/java1.4/jre/lib/PA_RISC2.0W/libjava.sl
Before starting the job throttling again, change the PATH and SHLIB_PATH
environment variables as follows:
To apply this change definitively, edit the jobthrottling.sh file
by adding the environment settings after the following line:
|
|
Job throttling does not start | Symptom: When you start the job throttling feature, nothing
happens and the following error message is displayed:
|
Cause and Solution: Possible causes are:
|
|
Job throttling does not start | Symptom: When you start the job throttling feature, nothing
happens and the following error message is displayed:
|
Cause and Solution: Your password is encrypted in old format. To encrypt the password with the correct encryption version, use the enigma or pwdcrypt programs. For details about how to encrypt the password, see Encrypting SAP user passwords. | |
Job throttling does not stop | Symptom: When you stop the job throttling feature, nothing happens. |
Cause and Solution: You are connected as a TWSUser
who does not have write permission on the
XAname_jobthrottling_cmd.txt file. To solve this problem,
delete the XAname_jobthrottling_cmd.txt file and enter the
command again. For detailed information about stopping the job throttler, refer to
Step 5. Starting and stopping the job throttling feature. |
|
Job throttling: alerts for MTEs are not generated according to the threshold values set | Symptom: Alerts for the MTEs created by the job throttler are generated without respecting the threshold values that are set. |
Cause and Solution: You started a new job throttler
instance, which, being enabled to send data to CCMS, created the related MTEs. When
you include the MTEs in your monitoring set, the threshold values are automatically
set according to the existing MTE class. Nevertheless, alerts are generated without
respecting these values. To solve this problem, edit the MTE properties and save them again, even if you do not change anything. |
|
Job throttling: saving MTE properties generates an informational message | Symptom: When you edit and save the properties of MTEs
generated by the job throttler, the following informational message is displayed:
|
Cause and Solution: In the pop-up window that displays the message, click Continue and close the Properties window. Your settings are saved. | |
Job throttling: error message displayed when creating trace file on HP operating systems | Symptom: While the job throttler is stopping, there are
intercepted jobs to release on exit. The following error message is displayed:
|
Cause and Solution: The message does not report any real error, and can be ignored. | |
The system cannot intercept jobs | Symptom: Although the job interception feature is active on the SAP system, the intercepted jobs are kept in scheduled state. |
Cause and Solution: The job throttler feature or the Java™ Virtual Machine used by the job throttler
might still be active. On each extended agent where the job throttler was started
at least once, ensure that:
|
|
access method executables: r3batch, r3event,
psagent : permission denied messages in the job
log. |
Symptom: The job log reports multiple "Permission denied" messages. |
Cause and Solution: The root cause might be that the access
method executable, for example, r3batch, is submitted by the root
user and not the twsuser . This creates directories and files with the
wrong ownership and file permissions. Verify the ownership of the following
directories and files if you are running the product on UNIX® platforms. Ensure that the twsuser is the
owner of the files and that the user has both read and write permissions on the files,
and execute permission on the
directories.
|
|
psagent : misleading message
displayed if the local options file has no right
permissions |
Symptom: The job log shows the following message:
but
all the mandatory options were correctly set in the options file. |
Solution: Check that the options file has
read and write permissions available to the user
who is trying to launch the job. |
|
No messages written in the job log | Symptom: HCL Workload Automation does not write any messages in the job log if the file system for tracing is full or the ljuser does not have the correct permission to write in the trace directory. |
The submission of a PeopleSoft job fails | Symptom: The submission of a PeopleSoft job fails
and the HCL Workload Automation job log contains a Java™ exception similar to
the following:
|
Cause and Solution: The psjoa.jar path
contains special characters. Define a path without special characters. |
|
The submission of an Oracle job fails | Symptom: The submission of an Oracle job fails and the
HCL Workload Automation job
log shows the following information:
|
Solution: Submitting an Oracle job might fail because there is a connection problem to the Oracle database. Verify that your Oracle naming methods are set correctly. For details about how to configure naming methods, refer to the Oracle Net Services Administrator's Guide. | |
mvsjes: RACF® authorization problem on z/OS® version 1.7 | Symptom: An S047 abend is returned if the
EEWSERVE started task does not have an associated RACF® owner ID. |
Solution: In the RACF® database, associate an authorized RACF® ID with the EEWSERVE started task as specified in Setting RACF authorizations on z/OS. |
|
To upgrade the SAP environment, perform the following steps: |
|