Waiting for bot readiness after deployment

Question

Situation 1 I wrote my own bot structure and deployed Azure. The test in the web chat showed me "Waiting for the bot to be ready after deployment."

Situation 2 I downloaded the source code from Azure bot Services, after which I deploy back to Azure, the web chat showed me "Waiting for the bot to be ready after deployment."

Answer 1

I also ran into this problem, and that is how I solved it.

• Publish options changed to check Remove additional files at destination . This is an important step, because when you created a new bot of a web application, it will already have files in this place. Therefore, when you publish your code, it will be placed along with code files that already exist. You can also check it by going to the URL /api/messages . If this gives you an error, then this is likely to happen.

• I also updated all the NuGet dependencies.

• Another problem that caused me some problem is the application password. The application password in your web.config file should match the one already created for your BOT. Do not create a new password on the bot management page. If you have done this, make sure that you have changed / updated the password in the application settings for web applications, as well as in the web.config file. When you host the bot, by default it will use the Application Id and Application Password , which were generated automatically. These values ​​can be seen in the Web App Bot service type, which is located under App Service Settings>Application Settings . Scroll down the page and you will see these two settings. Copy the Application Id and Application Password values ​​and update them in the Web.config file.

Hope this help!

Answer 2

For me, this changed the destination URL in the publishing settings to https. The default is http.

Answer 3

I was missing node packages that I did not know about. I found errors in the output logs at https: // [bot-name-here] .scm.azurewebsites.net / dev / wwwroot /: vs.output

Or you can proceed with this by choosing Build -> Click 'Show output' (or Shift + Command + U) (its fifth icon in the left side menu in the build window)

Hope this helps!

Answer 4

I had a window open for several days, and the “Test in web chat” simply displayed “Waiting for the bot to be ready” and a progress indicator of juggling forever. I duplicated the tab, and it immediately appeared. I think that my session may have expired or something like that, because on any new duplicated tab I could just start the bot normally.

Answer 5

I solved the problem by setting the value of the .bot file property "Copy to output directory" to "Always copy" in Visual Studio Solution Explorer.

Details: the bot worked fine locally in the emulator. After deploying to Azure (continuous deployment), Test in Web Chat hung with Waiting for Bot Ready. (It would be nice if he discovered and reported errors.)

After setting up Azure storage, enabling Azure logging, detecting a FileNotFoundException exception, checking with Resource Explorer, and deploying several versions of bots, I isolated the reason. This document really helped me troubleshoot:

https://docs.microsoft.com/en-us/azure/app-service/troubleshoot-dotnet-visual-studio#a-nameapptracelogsacreate-and-view-application-trace-logs

Answer 6

I also ran into this problem, but the solution I have is completely different from the ones suggested above.

I created my knowledge base and web application bot exclusively using the portal. The problem is the configuration. At the time of writing, Bot Template: Node.js> Question and Answer is not working. I needed to create a new web application bot, and I chose C #> Question and Answer instead.

This solved my problem and allowed me to use the Test in Web Chat feature.

Answer 7

Some troubleshooting ideas for people having the same error:

• Make sure that the server hosting your bot really works. If the time https://YOUR_BOT.azurewebsites.net has expired, then your server is not working, check the settings
• Check if you have any logs in the application service: turn on everything in the "Application Service"> "Diagnostic Logs" section, then go to " App Service > Log Stream .
• Check for potential errors under Web App Bot > Channels > Web Chat > Issues
• Make sure the files on the server look normal by going to " App Service > App Service Editor (Preview)
• Close all your browsers, especially if they have been working for a long time and / or you recently changed a lot of configuration files

I fixed the problem using a combination of these points