Troubleshooting of Google Vertex AI Search: Difference between revisions

From LemonWiki共筆
Jump to navigation Jump to search
No edit summary
(+ Troubleshooting: "Requested Entity Already Exists" Error When Saving Data Stores)
Line 64: Line 64:
*# Go to the API & Services page in Google Cloud Console.
*# Go to the API & Services page in Google Cloud Console.
*# Search for Discovery Engine API and ensure it is enabled.
*# Search for Discovery Engine API and ensure it is enabled.
=== Troubleshooting: "Requested Entity Already Exists" Error When Saving Data Stores ===
'''Error:'''
When saving site indexing, the following error message appears<ref>[https://cloud.google.com/datastore/docs/concepts/errors Errors and Error Handling  |  Cloud Datastore Documentation  |  Google Cloud]</ref>:
<pre>
Failed to save sites
Requested entity already exists
Tracking number: <mix of English and numeric characters>
</pre>
'''Root Cause:'''
Conflicting URL patterns exist simultaneously in "Specify URL patterns to index":
<pre>
example.com
</pre>
and
<pre>
''.example.com/''
</pre>
These two patterns conflict with each other, causing the system to treat them as duplicate entities.
'''Solution:'''
Simply remove one of the patterns to resolve the issue. It's recommended to keep the broader pattern <code>''.example.com/''</code> as it already includes <code>example.com</code>.


== Related Pages ==
== Related Pages ==

Revision as of 23:13, 28 April 2025

Troubleshooting of Google Vertex AI API


icon_scale_pencil.png This article "Troubleshooting of Google Vertex AI Search" is still being written. If there are any incomplete parts, you are welcome to directly edit them. 這篇文章「Troubleshooting of Google Vertex AI Search」內容還在撰寫中,如果有不完整的部分,歡迎你直接動手修改


🌐 Switch language: EN, 漢字


Issues

Troubleshooting: Vertex AI Search: Data Repository Requires Enterprise Features

Error: When creating an application, encountered the error message "This application cannot currently use 4 data stores are..." Expanding the data repository list shows "Website data repository can only be linked to Enterprise version of Vertex AI Search applications"

Solution: When creating the application, enable "Enterprise Edition Features"

Troubleshooting: SearchLite API Blocked" Error in Discovery Engine

Issue Description: When attempting to retrieve search results using Google Vertex AI API[1], the following error occurs:

curl -X POST -H "Content-Type: application/json" \
"https://discoveryengine.googleapis.com/v1/projects/PROJECT_ID/locations/global/collections/default_collection/engines/APP_ID/servingConfigs/default_search:searchLite?key=API_KEY" \
-d '{
"servingConfig": "projects/PROJECT_ID/locations/global/collections/default_collection/engines/APP_ID/servingConfigs/default_search",
"query": "QUERY",
}'

Met the error

{
  "code" : 403,
  "message" : "Requests to this API discoveryengine.googleapis.com method google.cloud.discoveryengine.v1.SearchService.SearchLite are blocked.",
  "status" : "PERMISSION_DENIED",
  "details" : [
    {
      "@type" : "type.googleapis.com/google.rpc.ErrorInfo",
      "reason" : "API_KEY_SERVICE_BLOCKED",
      "domain" : "googleapis.com",
      "metadata" : {
        "service" : "discoveryengine.googleapis.com",
        "methodName" : "google.cloud.discoveryengine.v1.SearchService.SearchLite",
        "apiName" : "discoveryengine.googleapis.com",
        "consumer" : "projects/xxx"
      }
    },
    {
      "@type" : "type.googleapis.com/google.rpc.LocalizedMessage",
      "locale" : "en-US",
      "message" : "Requests to this API discoveryengine.googleapis.com method google.cloud.discoveryengine.v1.SearchService.SearchLite are blocked."
    }
  ]
}

Resolution Steps: Check API Key Restrictions

  • Verify if the key is restricted to specific APIs:
    1. Navigate to the API Key Management page in Google Cloud Console.
    2. Locate the API key being used and check if it is restricted to specific APIs. If the restriction includes discoveryengine.googleapis.com, ensure it is correctly configured.
    3. Remove unnecessary restrictions: If the key is restricted to unrelated IP addresses or applications, remove those restrictions.
  • Enable the Discovery Engine API
    1. Go to the API & Services page in Google Cloud Console.
    2. Search for Discovery Engine API and ensure it is enabled.

Troubleshooting: "Requested Entity Already Exists" Error When Saving Data Stores

Error: When saving site indexing, the following error message appears[2]:

Failed to save sites
Requested entity already exists
Tracking number: <mix of English and numeric characters>

Root Cause: Conflicting URL patterns exist simultaneously in "Specify URL patterns to index":

example.com

and

''.example.com/''

These two patterns conflict with each other, causing the system to treat them as duplicate entities.

Solution: Simply remove one of the patterns to resolve the issue. It's recommended to keep the broader pattern .example.com/ as it already includes example.com.

Related Pages


References