Having Issues Creating the QnA Maker Knowledge Base-Step 4

[rajivsr23]

I am having Issues creating a Knowledge Base . This is the Error Message that I get “Oops!! Something went wrong. Please try again. If this error persists, please provide details via the feedback menu.” On Step 4, we have to create a Knowledge base, by following the Instructions listed here https://docs.microsoft.com/en-us/azure/cognitive-services/qnamaker/tutorials/create-publish-query-in-portal#create-a-knowledge-base And I’m stuck in Step 7 under “Create a Knowledge Base”.

Any help on this matter would be greatly appreciated!

[garrytrinder]

I'm having the same issue, attempting to create a new knowledge base results in the below ### error.

[volks79]

same error no endpoint keys found. Anyone can provide help?

[himsoni85]

Ok, I just reported this issue as well, but now realized that others are facing the same. Seems like some configuration is missing in the QnA service created via ARM template. This error is not addressed anywhere on Google either.

[himsoni85]

I found the fix for the issue (or at least a workaround). If your Resource Group (RG) holding all resources from the template, is in a different location than the one hosting your QnA Cognitive service, then you will face this issue with Keys not being discoverable by the QnA Maker service. For example, in my case I had chosen East US as the location for hosting a dedicated RG for all these resources, but the QnA service endpoint was provisioned in West US. I am not sure why that was the case since all three required services: Application Insights, QnA Maker and Azure Search are available in East US as well. However, as soon as I deleted my RG and created it again in West US region, I was able to create the Knowledgebase without any errors.

[jreed5]

I also ran into this a couple of times. I ended up having problems in a creation attempt, and reused the resource group I had started with. I ended up having to delete the resource group and start all over from the beginning. Once I did that, it finally worked.

[archmangler]

This appears to be a performance problem with the Cognitive Services platform. These failures are intermittent, If I persistently retry a failure, the knowledgebase will often eventually get created. This often happens for 1 out of 3 or so attempts.

Currently I am running a for loop to test creation, today is particularly bad with all out of 100 tries failing over a period of an hour. Running the loop for 10 000 iterations at 20 second intervals, will post back my results in a few hours.

[archmangler]

After 100 tries, I delete the resource group and run the creation script again, knowledgebase is created. This is without any changes to the configuration process. This service has serious reliablity and consistency issues!

[garrytrinder]

Oh wow, thats incredibly poor 😬

Nice research @archmangler 👍🏻

[ghost]

Hello all, another trick to get the knowledge base creation to work is at the time of deployment select the following values: You should do this for the first time, and after you have created the knowledge base, and published it - then you can always downgrade.

Hope this helps

[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." } }

[cahuertav]

i have this problem: