Troubleshooting
Certain issues can arise that are common to many of the app templates. Please check here for reference to these.
1. File is not digitally signed
While running PowerShell script, sometimes user gets an error showing 'File is not digitally signed'.
Fix: If this type of error occurs then run this: "Set-ExecutionPolicy -ExecutionPolicy unrestricted"
2. Azure subscription access failed
Connect-AzAccount : The provided account **.onmicrosoft.com does not have access to subscription ID "XXXX-". Please try logging in with different credentials or a different subscription ID.
Fix: User must be added as a contributor on the Azure subscription."
3. Failed to acquire a token
Exception calling "AcquireAccessToken" with "1" argument(s): "multiple_matching_tokens_detected: The cache contains multiple tokens satisfying the requirements
Fix: This means user is logged-in with multiple accounts in the current powershell session. Close the shell window and open a new one."
4. Azure AD app permission consent error
The apps created by this app template requires an admin consent for "User.Read" graph permission so it can operate correctly.
Errors: Forbidden({"ClassName":"Microsoft.Portal.Framework.Exceptions.ClientException","Message":"Graph call failed with httpCode=Forbidden, errorCode=Authorization_RequestDenied, errorMessage=This operation can only be performed by an administrator. Sign out and sign in as an administrator or contact one of your organization's administrators., reason=Forbidden
Please ask your tenant administrator to consent the "User.Read" permission for both apps (bot app, config app).
5. Error when attempting to reuse a Microsoft Azure AD application ID for the bot registration
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.
6. Error while deploying the ARM Template
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.
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 Knowledge-base
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 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
This happens when the user alias is not a part of the UPN admin list of the config web application.
Please add the user alias to the ConfigAdminUPNList parameter in parameters.json file. Append the user alias/email to the list using semi-colon ; separator. e.g. [email protected];[email protected]
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 Question Answering portal or add it from the messaging extension in the experts' team.
Didn't find your problem here?
Please, report the issue here