Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to provision the bot using provisioncomposer.js command #3460

Closed
sandeepreddy0987 opened this issue Jun 23, 2020 · 7 comments
Closed
Assignees

Comments

@sandeepreddy0987
Copy link

I am unable to provision the bot. 1)Can someone provide where to find the App password?
2) Do we need to create a web bot in azure before publishing to azure?
image

@luhan2017
Copy link
Contributor

@sandeepreddy0987 , what version of Composer are you using? we had a fix on this #3359 , could you try to use the latest master or you can wait to the next release of the Composer Electron which will be available soon.

@luhan2017 luhan2017 self-assigned this Jun 23, 2020
@sandeepreddy0987
Copy link
Author

v1.0.1 is my botcomposer version

@luhan2017
Copy link
Contributor

@sandeepreddy0987 , this is a known issue in the v1.0.1, you can mitigate this by referring to this comment to add tenantId as a parameter for provision, #3313 (comment), or you can wait for v1.0.2 release which will be available soon.

@triciasinclair
Copy link

Hi @luhan2017 will this also resolve the below issue?
I've tried the workarount to also include the tenantid but with no success...

{
"error": {
"code": "InvalidBotData",
"message": "Bot is not valid. Errors: The bot name is already registered to another bot application.. See https://aka.ms/bot-requirements for detailed requirements."
}
}

error

This was identified as a related issue in #3324 and resolved together. I've tried the workaround you reported above - include the tenantid but with no success..

@luhan2017
Copy link
Contributor

@triciasinclair , according to the error message, you already passed the tenant id part, it should fail at the web app provision part, could you try to update your bot name, it looks like you are using an existing bot name which cause the provision failure.

@luhan2017
Copy link
Contributor

@triciasinclair @sandeepreddy0987 , is this issue resolved in your side?

@sandeepreddy0987
Copy link
Author

Resolved. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants