You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usually this is because the indexer hasn't started running yet. There is usually a little bit of a delay for the indexer to get going, and usually by the time you have built and deployed the website that delay is over so this code can successfully run, but it looks like in your case it wasn't, so sorry about that. It could also depend on if the region you selected for your search service to run in is currently busy with other jobs, in which case it may take a few minutes for there to be space for your newly created job.
I tried to add an if info.LastResult == null check inside the while loop to continue checking with a cap of 30x. But still after thread sleep 3000 x30 still the info.LastResult is still null.
I haven't changed any region on the deployment settings. Search service is at South Central US. Is this the right region?
Hmmm, it shouldn't take that long. South Central US is one of our busiest regions though. It should work but like I said might just take awhile. I am changing the default region to West US 2 to hopefully help with this in #111 and I was having no issues testing there over the last day or so.
When running the initializer I got this error:
Error retrieving indexer status: Object reference not set to an instance of an object
I tried to debug where does it happen and it is on this line.
AzureSearch_JFK_Files/JfkWebApiSkills/JfkInitializer/Program.cs
Line 338 in 9ba4234
Trying to check info.Status it is running. But info.LastResult is null.
The text was updated successfully, but these errors were encountered: