1. Using Robots in Oracle Integration 3
  2. Troubleshoot
  3. Troubleshoot the Robot Agent and Environments
  4. Cannot Start a Robot Agent

Pre-General Availability: 2024-09-02

Cannot Start a Robot Agent

If you're unable to start running a robot agent, whether for the first time or after stopping it, use the troubleshooting steps to get back on track.

Issue

You cannot stop the robot agent, either immediately after you installed it or after someone stopped it.

Why It Happens

This issue typically occurs when the robot agent can't connect to Oracle Integration, or when the configuration of the robot agent requires some adjustments. Keep reading for step-by-step instructions on how to troubleshoot.

What to Do

After completing each step, try running the agent again.

Step Consideration More information

1

Did an error occur when you tried to start the agent?

Error text

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)

What to do

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.

2

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

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

See System Requirements.

3

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.

4

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.

5

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.

6

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.

7

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.

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.