Bot Framework bot works in Emulator but gets Microsoft.Bot.ChannelConnector.BotAPI.ThrowOnFailedStatusCode on deployed bot

1
votes

I'm using the bot framework v4. When I test my bot locally using the emulator it works fine. When I deployed my bot and try to access it using the direct line or web chat no messages show up and when I try to send the bot a message it fails. In the Channels health I get "There was an error sending this message to your bot: HTTP status code InternalServerError"

Application Insights shows an Exception that says "POST to failed: POST to the bot's endpoint failed with HTTP status 500 POST to the bot's endpoint failed with HTTP status 500"

This is the call stack 

   at Microsoft.Bot.ChannelConnector.BotAPI+<PostActivityToBotAsync>d__31.MoveNext (Microsoft.Bot.Base.ChannelConnector, Version=3.2.3.8, Culture=neutral, PublicKeyToken=null)
Inner exception System.Exception handled at Microsoft.Bot.ChannelConnector.BotAPI+<PostActivityToBotAsync>d__31.MoveNext:
   at Microsoft.Bot.ChannelConnector.BotAPI.ThrowOnFailedStatusCode (Microsoft.Bot.Base.ChannelConnector, Version=3.2.3.8, Culture=neutral, PublicKeyToken=null)
   at Microsoft.Bot.ChannelConnector.BotAPI+<PostActivityToBotAsync>d__31.MoveNext (Microsoft.Bot.Base.ChannelConnector, Version=3.2.3.8, Culture=neutral, PublicKeyToken=null)

I've been able to get the bot working before. I recently made a new bot on my Azure account and it's working fine.

Thank you in advance.

1
node.jstypescriptazurebotframework
If you recent made a bot purely on azure, and it works, but this bot is created locally and deployed, but doesn't, then something went sideways in the deployment. How did you deploy your bot? – JJ_Wailes
Hi @JJ_Wailes I deployed it using az webapp deployment source config-zip --resource-group "<resouce-group-name>" --name "<bot-resource-name>" --src "allfiles.zip" – 123me
This is the way I've previously deployed it – 123me
Are you still working on this? – Kyle Delaney
Yes I am still working on it – 123me

1 Answers

0
votes

This could be related to a bug in the commands az bot prepare-deploy and az webapp deployment source config-zip. As a workaround, try manually correcting the name of your assembly in your .deployment file as described here and then redeploy.