Troubleshooting
Certain issues can arise that are common to many of the app templates. Please check here for reference to these.
The bot is not valid.
Errors: MsaAppId is already in use.
Creating the resource of type Microsoft.BotService/botServices failed with status "BadRequest"
This happens when the Microsoft Azure application ID entered during the setup of the deployment has already been used and registered for a bot.
Either register a new Microsoft Azure AD application or delete the bot registration that is currently using the attempted Microsoft Azure application ID.
The bot will reply to the user post with the error message if it finds that it cannot store any additional QnA pair to the Knowledgebase
Errors: I cannot save this qna pair due to storage space limitations. Please contact your system administrator to provide additional storage space.
In case of such a scenario, the system administrator or the app installer will need to update the pricing tier accordingly for QnA service in Azure Portal.
This happens when the resources are already created or due to some conflicts.
Errors: The resource operation completed with terminal provisioning state 'Failed'
In case of such a scenario, the user needs to navigate to the deployment center section of failed/conflict resources through the Azure portal and check the error logs to get the actual errors and fix them accordingly.
Redeploy it after fixing the issue/conflict.
This happens when the admin tries to install the app to Microsoft Teams using the zip file.
In case of such a scenario, the admin user needs to click on the "Copy error details to clipboard" and check the error details.
If the error specifies as invalid value then fix the invalid value and create the new zip folder to install the app.
If the error specifies as format issue then fix the manifest format issue and create the new zip folder to install the app.
If the error specifies as related to folder structure then make sure the that the 3 files manifest.json,color.png, and outline.png are the top level of the ZIP package, with no nested folders
- The experts and end-user app packages were uploaded to the organization's app catalog, and
- The bot in the end-user app responds to questions from some users, but not others.
Check if the experts and end-user applications have different app permission policies applied to them. For example, you may have used permission policies to try to restrict the end-user app so that only members of the experts team can install it.
Option 1
- Change the app permission policy to be the same for end-user and experts apps.
- If desired, change the name and description of the experts' app to discourage end-users from installing the experts app.
FAQ Plus always restricts access to experts functionality based on the user's membership in the team of subject matter experts. Even if an end-user were to install the experts' app, they cannot perform operations reserved to SMEs unless they are a member of the experts team.
Option 2
Unpublish the experts' app from the organization's app catalog, and upload it only to the experts team.
This happens when the admin user does not update the knowledge base id in the configuration app or if there are no QnA pairs in the knowledge base.
In case of such a scenario, the admin user needs to make sure that the knowledge base id is updated in the configuration app and QnA pairs are existing in the knowledge base.
If no QnA pairs exist in the knowledge base then add new ones either directly from the QnA maker portal or add it from the messaging extension in the experts' team.
Please report the issue here