Why would I be getting a socket hang up when trying to create Sharepoint Indexer?

Jamie Owen 20 Reputation points

I am following this tutorial to create a Sharepoint Indexer: https://learn.microsoft.com/en-us/azure/search/search-howto-index-sharepoint-online

I am using Postman to send the http requests. The first two requests worked fine, and I managed to create the data source, as well as the Index. However, when I run the final two requests (POST request to create the indexer, followed by the GET request to allow me to login to the application), after I complete the login step the POST requests spins for a while before I get an error saying it could not get a response, and the socket hung up. See image.

Does anyone have any idea why this would happen?

User's image

Azure AI Search
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.
507 questions
A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
8,611 questions
{count} votes

1 answer

Sort by: Most helpful
  1. ajkuma 19,041 Reputation points Microsoft Employee

    Thanks for posting this question.

    To better assist you on this, just to clarify, is the machine behind a proxy? What Search tier are you leveraging?


    Just to highlight, Indexing isn't a background process. A search service will balance indexing and query workloads, but if query latency is too high, you can either add capacity or identify periods of low query activity for loading an index.

    As mentioned the doc,  if you don’t run the Get Indexer Status within 10 minutes the code will expire and you’ll need to recreate the data source.

    As an example (for Azure SQL) pointer, the default value of queryTimeout indexer configuration setting is 5-minute.


    --search-indexer-troubleshooting : This article covers problems and potential resolutions when indexer results are unexpected and there is limited information to go on.
    --To fetch more insights, review :#enable-resource-logging

    Kindly let us know, I'll follow-up with you further.