Agent jar version is either blank or not correct

The file name of the robot agent's JAR file no longer contains the robot agent's version number, such as 0.1.80.

Restore the file name of the JAR file to the original name, including the robot agent's version number. If you aren't sure of the correct format, you can download the agent again and copy the JAR file into your robot agent's directory. See Download the Robot Agent.

An error occurred while storing or trying to retrieve secrets from the local store.

or

An Exception occurred while retrieving secrets. Terminating agent

Oracle Integration was unable to write values to or retrieve values from the computer's local keystore. This error typically appears when a user doesn't have sufficient privileges. For example, one administrator might have downloaded the robot agent, and a second administrator is trying to start the robot agent. The second administrator might not be able to access the credential manager on the computer.

Run the command prompt as an administrator, and then try starting the robot agent again. See Start the Robot Agent.

Could not determine the path to the JAR file. Provide full path of the agent jar.

One of the following issues occurred:

• The folder name or directory where the robot is installed contains a space.

• The command that you used to start the robot agent didn't include the full directory of the robot agent's JAR file.

Check whether the folder name or directory contains a space. If so, remove the spaces from the directory, update the command to start the robot agent appropriately, and try again.

If no spaces are in the folder name or directory, review the command that you used to start the robot agent. update the command so that it contains the full directory to the JAR file. See Start the Robot Agent.

Either latest available version or current running agent version is null.

or

Either minimum supported version is not met or current running agent version is null.

or

Minimum supported agent version is version_number, current running version version_number

The robot agent's version is no longer compatible with Oracle Integration.

Update to a newer version of the robot agent. See Download the Robot Agent.

Error occurred while downloading dependencies like micromamba, robot runtime, rcc, etc.

or

Robot runtime is not available. Please check robot runtime installation before proceeding.

The environment on which you installed the robot agent doesn't have access to the public internet and is unable to download the required dependencies.

The environment must be able to access the public internet when you start the robot agent for the first time. Ensure that the computer has access to the public internet, such as by temporarily disabling the VPN, and try starting the robot agent again.

Depending on the robot's interactions, it might need access to the public internet in general. See Design Considerations.

Failed creating python virtual environment for flowRT

This error can occur when you're trying to start the robot agent or trying to start the robot agent as a Windows service.

• If you're trying to start the robot agent, the machine might not have network connectivity, or the robot agent might not be able to create subdirectories in the user home.

• If you're starting the robot agent as a Windows service, you might not have defined a required environment variable.

Starting the robot agent

The environment must be able to access the public internet when you start the robot agent for the first time. Ensure that the computer has access to the public internet, such as by temporarily disabling the VPN, and try starting the robot agent again.

Depending on the robot's interactions, it might need access to the public internet in general. See Design Considerations.

Additionally, run the command prompt as an administrator, and then try starting the robot agent again. See Start the Robot Agent.

Starting the robot agent as a Windows service

See Start the Robot Agent Automatically.

Failed saving the modified InstallerProfile configuration file

Oracle Integration was unable to update the robot agent's configuration file. Oracle Integration must remove sensitive values from the configuration file and add a comment to the file about the change.

Run the command prompt as an administrator, and then try starting the robot agent again. See Start the Robot Agent.

Failed to create environment in the control room or update Agent.properties file.

An issue occurred during the installation of the robot agent. For example:

• The installation parameters for the robot agent weren't correct.

• The robot agent couldn't register with Oracle Integration.

• The Agent.properties file couldn't be updated.

Confirm that your network allows the computer to access Oracle Integration. See Review Your Network Configuration.

Next, confirm that your network allows the computer to access the public internet. This access is required the first time that you start the robot agent. See Start the Robot Agent.

Finally, ensure that the person who starts the robot agent has the require file system permissions to save files on the computer.

Format of minimum supported version or current running agent version is not correct.

The file name of the robot agent's JAR file no longer contains the robot agent's version number, such as 0.1.80.

Restore the file name of the JAR file to the original name, including the robot agent's version number. If you aren't sure of the correct format, you can download the agent again and copy the JAR file into your robot agent's directory. See Download the Robot Agent.

InstallerProfile.cfg or Agent.properties file is either missing fields or has invalid data

The InstallerProfile.cfg file or Agent.properties file has been modified and is no longer valid.

1. Download the robot agent, and copy the Agent.properties and InstallerProfile.cfg files to the directory where you've installed the robot agent.

   See Download the Robot Agent.

2. Update the Robot Agent's Configuration File

3. Start the Robot Agent

No value passed to -jar argument for agent jar. Wrong arguments passed

or

Unable to retrieve the -jar argument value. Wrong arguments passed

The command that you used to start the robot agent was missing one or more parameters. For example, the command might not contain a required parameter, or the command contains an environment variable that hasn't been set in the command prompt.

Update the command so that it contains the correct parameters. See Start the Robot Agent.

RPA Agent is supported on JDK version 1.17 and above, please install or upgrade JDK/JVM to run RPA Agent.

Java Development Kit (JDK) 17 isn't installed on the computer or virtual machine.

Install Java Development Kit (JDK) 17 on the computer or virtual machine. See Meet the Robot Agent's Requirements.

User agent set to: Oracle-JavaSDK/2.56.0 (Mac OS X/14.3.1; Java/17.0.8; Java HotSpot(TM) 64-Bit Server VM/17.0.8+9-LTS-211)
Exception in thread "main" com.oracle.bmc.model.BmcException: Error returned by GetAgentVersion operation in Agent service.(401, NotAuthenticated, false) The required information to complete authentication was not provided or was incorrect. (opc-request-id: debugging_identifier/debugging_identifier/debugging_identifier)
Timestamp: timestamp
Client version: robot_agent_version
Request Endpoint: endpoint
Troubleshooting Tips: See https://docs.oracle.com/en-us/iaas/Content/API/References/apierrors.htm#apierrors_401__401_notauthenticated for more information about resolving this error
Also see  for details on this operation's requirements.
To get more info on the failing request, you can enable debug level logs as mentioned in `Using SLF4J for Logging section` in https://docs.oracle.com/en-us/iaas/Content/API/SDKDocs/javasdkconfig.htm.
If you are unable to resolve this Agent issue, please contact Oracle support and provide them this full error message.
	at com.oracle.bmc.http.internal.ResponseHelper.throwIfNotSuccessful(ResponseHelper.java:160)

An issue has occurred with the Agent.properties file.

Navigate to the folder that contains the unzipped files for the robot agent, and delete the Agent.properties file.

Next, try starting the agent again.

1

Does the robot agent's computer meet the system requirements for the robot agent?

For example, the correct version of the JDK might not be installed, or the JAVA_HOME might not be set.

See System Requirements.

2

Does the robot agent's computer have internet access?

Navigate to a website that your network allows you to access, and confirm that the page loads.

If the computer doesn't have internet access, work with a network administrator to correct this issue.

3

Does your network allow the robot agent's computer to access Oracle Integration?

Sign in to Oracle Integration from the computer that the robot agent is installed on.

If you are unable to sign in, your network might restrict access to the internet based on IP address.

Work with an administrator to ensure that the egress rules allow access to the inbound IP address for Oracle Integration. Otherwise, the robot agent cannot access Oracle Integration.

See Obtain the Inbound and Outbound IP Addresses of the Oracle Integration Instance in Provisioning and Administering Oracle Integration 3.

4

Does a confidential application exist for the robot agent, and is it active?

A confidential application is an OAuth client application that allows robot agents to securely connect to Oracle Integration using the OAuth protocol.

See Ensure that the Confidential Application is Active.

5

Is the robot agent's configuration file defined correctly?

For step-by-step instructions on updating the file, see Update the Robot Agent's Configuration File.

6

Is there a space in the folder name or directory where the robot agent is installed?

Do not include any spaces in the folder name, or you cannot start the robot agent.

Additionally, Oracle recommends not including any spaces in the directory path.

7

Is there a space in the home directory of the computer?

Even if you don't install the robot agent to the home directory, the robot agent must create files in the home directory. The robot agent is unable to create the files if the home directory contains any spaces.

For information about how to create a new home directory and specify the new home directory in the startup command for the robot agent, see Start the Robot Agent.

8

Enter a service request

If you complete all of these steps and the robot agent still won't run, get help from Support by entering a service request (SR). Include the log files for the robot agent with the request. See Download the Log File for a Robot or Robot Agent.