Azure AI Search
An Azure search service with built-in artificial intelligence capabilities that enrich information to help identify and explore relevant content at scale.
1,049 questions
Indexer failed whenever I create a vector index on documents from blob storage container
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(83.2, 57.00000000000001%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
Ahmad Shafiq
130
Reputation points
From the past two days whenever I Create an index from azure portal it failds to index my documents why it is happening????
Error:
Document Key: localId=https%3a%2f%2fsaorgdocsaskzoedev.blob.core.windows.net%2fdatarovers%2fA58876_20240516.pdf&documentKey=https%3a%2f%2fsaorgdocsaskzoedev.blob.core.windows.net%2fdatarovers%2fA58876_20240516.pdf
Operation:
Projection.IndexProjections.SearchIndex.test-dataroversdev
Message:
Could not 'Index' document to the search index
Details:
An unexpected error occurred while trying to process this document.
{count} votes
-
VenkateshDodda-MSFT 21,491 Reputation points Microsoft Employee2024-08-23T13:21:15.1133333+00:00 @Ahmad Shafiq Thanks for posting your question in Microsoft Q&A, apologize for any inconvenience caused on this.
Based on the shared information above, I have reviewed the backend logs(test-dataroversdev), I can see the indexer got created without any issues.
The creation operation of the indexer "test-dataroversdev" failed due to transient errors. You can refer to the documentation to learn more about these errors.If you want to know more about the failed operation, I suggest you raising a support ticket to investigate further.
Let me know if you have any further questions on this.
-
Ahmad Shafiq 130 Reputation points
2024-08-24T01:22:23.5466667+00:00 @VenkateshDodda-MSFT I have created an other resource with the same specifications there the indexer runs with out the failure, This issue starts happening when we upgraded our tier to s2 and this is done by the Microsoft team as we don't have any visible option in the azure portal to upgrade our AI Search, Moreover I do applied scheduling on the indexer to run after every hour but it fails every hour, I think this is some kind of glitch that causes to fail the indexer or may be the backend side that upgraded our resource tier have some bugs!
-
VenkateshDodda-MSFT 21,491 Reputation points Microsoft Employee
2024-08-27T11:33:13.4966667+00:00 @Ahmad Shafiq Thanks for your response and apologize for the delay in my response.
I understand that you have tried to create new indexer with same specifications, and it has worked out for you.
Moreover I do applied scheduling on the indexer to run after every hour but it fails every hour, I think this is some kind of glitch that causes to fail the indexer or may be the backend side that upgraded our resource tier have some bugs!
Are you experiencing this behavior on the newly created indexer or the older one. If you are experiencing this behavior on the older indexer as suggested earlier, I would suggest you to raise a support case to investigate and understand the issue better.
-
Ahmad Shafiq 130 Reputation points
2024-08-28T06:36:46.0333333+00:00 @VenkateshDodda-MSFT I'm experiencing this issue on my older indexer, Moreover I tried all the possible solutions including the indexer scheduling as well.
I had already opened a ticket for this purpose, lets see what happens next.
Thanks!
Sign in to comment
Sign in to answer