Connection Problem in google cloud(Gen AI)

Hello !

I have the same problem and I dont know what to do.

Do you solve de issue?

Hi! ​@Aaron.Gleason or ​@Shreya.Kumar Could one of you support with this?

Possible Causes

1. Deprecated Library Issue:
   • The com.google.api.client.json.jackson2.JacksonFactory class is deprecated (Google recommends using GsonFactory instead). If Automation Anywhere’s Vertex AI package relies on an outdated library, it might fail to process JSON responses correctly.
2. Google Cloud Configuration Errors:
   • Incorrect setup of OAuth 2.0 credentials, API enablement, or service account permissions in Google Cloud.
3. Automation Anywhere Package Version:
   • The Generative AI package in Automation Anywhere might be outdated or incompatible with your Control Room version or Vertex AI’s current API.
4. Network or Proxy Issues:
   • A firewall or proxy might be blocking the connection between your Bot Agent and Google Cloud.
5. Service Account Misconfiguration:
   • The service account might lack the necessary roles or the JSON key file might not be properly configured.

Step-by-Step Resolution

1. Verify Google Cloud Configuration

Since you suspect the issue lies in Google Cloud config, let’s start there:

• Enable Required APIs:
  • Go to the Google Cloud Console (console.cloud.google.com).
  • Navigate to APIs & Services > Library.
  • Ensure the following APIs are enabled:
    • Vertex AI API
    • Cloud AI Platform API (if applicable)
    • IAM API (for service account management)
• Check OAuth 2.0 Credentials:
  • Go to APIs & Services > Credentials.
  • Verify your OAuth 2.0 Client ID:
    • Client ID and Client Secret should match what you entered in Automation Anywhere.
    • Redirect URI should be set to a valid endpoint (e.g., http://localhost:8080 for testing or a Control Room callback URL).
    • Authorized Domains should include your Automation Anywhere domain if applicable.
  • Test the credentials:
    • Use a tool like Postman to make a simple API call to Vertex AI with these credentials to confirm they work outside Automation Anywhere.
• Service Account Setup:
  • If using a service account instead of OAuth:
    • Go to IAM & Admin > Service Accounts.
    • Create or select a service account.
    • Assign it the role Vertex AI User (roles/aiplatform.user).
    • Download the JSON key file and note its location.
    • In Automation Anywhere, ensure the Generative AI: Connect action points to this JSON file correctly (more on this later).

2. Update Automation Anywhere Generative AI Package

• Check Package Version:
  • In the Control Room, go to Administration > Packages.
  • Look for the "Generative AI" package and note its version.
  • Compare it to the latest version available in the Automation Anywhere Bot Store or release notes.
  • If outdated, update to the latest version:
    • Download the new package and import it via Administration > Packages > Add Package.
• Why: Newer versions might use GsonFactory instead of the deprecated JacksonFactory, resolving the error.

3. Configure Generative AI: Connect Action

• OAuth Configuration:
  • Open your Task Bot in the Bot Editor.
  • Go to the "Generative AI: Connect" action causing the error.
  • Re-enter:
    • User Email Address: Your Google Cloud account email.
    • Client ID: From Google Cloud OAuth credentials.
    • Client Secret: From Google Cloud OAuth credentials.
    • Redirect URI: Ensure it matches exactly what’s in Google Cloud Console.
  • Test the connection by running the bot in debug mode and checking the logs.
• Service Account Configuration:
  • If using a service account:
    • Switch the authentication method to "Service Account" in the action.
    • Provide the path to the JSON key file (e.g., C:\Keys\vertex-ai-service-account.json).
    • Ensure the file is accessible by the Bot Agent (place it in a folder with read permissions).

4. Check Bot Agent and Network

• Restart Bot Agent:
  • On your local machine, stop the "Automation Anywhere Bot Agent Service" via services.msc, then restart it.
  • Ensure it’s connected to the Control Room (check the system tray).
• Network Test:
  • Run ping console.cloud.google.com from your machine’s Command Prompt to confirm connectivity.
  • If blocked, work with your IT team to whitelist Google Cloud endpoints (e.g., *.googleapis.com).

5. Review Logs for More Details

• Bot Execution Logs:
  • In the Control Room, go to Bots > View Logs after running the bot.
  • Look for additional error details beyond JacksonFactory.
• Node Manager Logs:
  • On your local machine, check C:\ProgramData\AutomationAnywhere\logs\node_manager.log.
  • Search for JacksonFactory or related exceptions to pinpoint the failure.

Workaround: Test with a Simple Bot

• Create a new Task Bot with just the "Generative AI: Connect" action and minimal configuration.
• Use the same credentials or service account.
• If it works, the issue might be specific to your original bot’s logic or dependencies.

If the issue persists:

• Contact Automation Anywhere Support:
  • Provide:
    • The full error message.
    • Control Room and Bot Agent versions.
    • Generative AI package version.
    • Logs from Step 5.
    • A screenshot of your Google Cloud credentials setup.
• Check Google Cloud Status:
  • Visit status.cloud.google.com to rule out a temporary Vertex AI outage.