Unable to create knowledgebase for azure cognitive service (Error: “No Endpoint keys found.”)

[maheshkumagali]

I am creating a new knowledge base connecting it to an already existing Azure Cognitive Service. But I am getting error: "No Endpoint keys found." when i click "Create KB".
Error: https://i.stack.imgur.com/pp8tV.png

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: a29f839a-d836-5f3a-f58c-f60f71a4fc18
• Version Independent ID: b9a9aaef-ccad-0da5-1fbf-663145b71596
• Content: Quickstart: Create knowledge base - QnA Maker - Azure Cognitive Services
• Content Source: articles/cognitive-services/QnAMaker/How-To/create-knowledge-base.md
• Service: cognitive-services
• Sub-service: qna-maker
• GitHub Login: @diberry
• Microsoft Alias: diberry

[RohitMungi-MSFT]

@maheshkumagali Is it possible to check if you are facing a similar issue when you create a new QnA resource along with the KB?
From the error it looks like the existing QnA service keys or service might be having issues. Is it possible to raise a support ticket for this resource from Azure portal?

[maheshkumagali]

Thanks for replying.
Just to make another point: my QnAMaker cognitive service does have the endpoint as shown here: https://i.stack.imgur.com/6PDQA.png.

Also I am able to create new KB pointing to another QnAMaker cognitive service. I am facing issue only when creating the new KB pointing to a particular QnAMaker cognitive service. Any things I need to check on the new QnAMaker cognitive service?

[RohitMungi-MSFT]

@maheshkumagali If you are able to create a new KB with the new QnAMaker then there is an issue with the first QnAMaker resource. You can try to restart your app service and wait for some time for it to reinitialize. Checkout the help from the QnAMaker helper bot.

If the above does not help you can raise a user voice ticket against this resource from the General Enquiry through User voice link from the top right corner of QnAMaker portal or you can raise a support ticket against this resource if you have a support plan for this subscription.

[maheshkumagali]

@RohitMungi-MSFT Any idea on how to restart QnAMaker service? I dont find that option in azure portal.

[maheshkumagali]

I restarted the app services in the same resource group but in vain.

[RohitMungi-MSFT]

@maheshkumagali Please raise a support request against this QnA resource so the product team can help you with the same. If you are able to use your new QnA resource you can delete this resource.

[RohitMungi-MSFT]

@maheshkumagali We will now proceed to close this thread. Please raise a support case against this resource to resolve the key issue or proceed to use the new resource.

[oatsoda]

@maheshkumagali Did you solve this issue?

[abbodh]

I am getting the same issue while performing the deployment using ARM template.

[infact]

I restarted the app services in the same resource group but in vain.
I am facing the same issue.Any resolution ?

[tmccart1]

I can concur that some configuration is missing from the ARM template creation. If I provision everything manually from the QnA Maker web site, it works, but if I use an ARM template for all of the supporting Azure resources, it does not work. I made sure that the ARM template resources had all of the exact same configuration as the resources created from the QnA Maker site UI.

I tried all of the suggestions above and none of them worked.

It is very easy to reproduce this error from PostMan by issuing the following GET:

https://[your-cognitive-service-name].cognitiveservices.azure.com/qnamaker/v4.0/endpointkeys

Make sure to include the Ocp-Apim-Subscription-Key header and set its value to the "KEY 1" value of your Cognitive service, which can be found in the "Keys and Endpoint" blade.

Here is the return payload:

{
"error": {
"code": "EndpointKeysError",
"message": "No Endpoint keys found."
}
}

[abbodh]

I was able to run after scaling up the azure app service SKU. As after few deployments, I realized that the CPU consumption spiked really high.

Just to clarify, restarting the app service won't help and you have to re-create the resources again.

[tmccart1]

@abbodh , what sku did you use on the app service? I was using S1. Thank you for your insight, this may end up helping me a lot!

[abbodh]

@tmccart1 I changed it from S1 to S2. Interestingly, once endpoint got created, I switched back to S1 and did not noticed any issue since then (perks of azure scaling)

[tmccart1]

@abbodh , in my case I was also sharing the hosting plan with a bot app service (just a small demo, didn't think I needed much). The hosting plan was at S1. I am going to try splitting out the cognitive service app out to its own hosting plan and bump it up. Thanks again!

[tmccart1]

Ugh, it still did not help.

[mirojurisic]

this is still happening :(

[01]

having issue as well

[rliberoff]

Having this issue too when creating the QnA Maker from an ARM Template.

[Cokeisit]

I'm too is having this issue when creating from an ARM template. This is something that needs to be solved.