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

500 internal server error- Azure web app hosting a botframework solution #3463

Closed
KwstasBol opened this Issue Sep 14, 2017 · 15 comments

Comments

Projects
None yet
7 participants
@KwstasBol
Copy link

KwstasBol commented Sep 14, 2017

Bot Info

  • Bot handle: amvrosiabot
  • App ID: fe2f78fd-c257-4e0f-92d6-79906b847172
  • SDK Platform: .NET
  • SDK Version: 4.6.1
  • Active Channels: Facebook Messenger
  • Deployment Environment: Azure App Service

Issue Description

My bot connects to the database of mine, takes the foods of the university restaurant compared to the current day, and displays the results. Although, it was operational, out of the blue we had a 500 internal server error and the message of the user was just sent to my Azure web service, without responding back.

Expected Behavior

The expected result was the response the the messenger user with the choices as show below at Expected Behavior

Actual Results

image

image

Expected Behavior

image

@JasonSowers

This comment has been minimized.

Copy link
Contributor

JasonSowers commented Sep 14, 2017

What SDK version are you using? It looks like you put in the .NET version in your form.

@advl03

This comment has been minimized.

Copy link

advl03 commented Sep 14, 2017

Could you please check if this is the same issue as this one?
#3466

@KwstasBol

This comment has been minimized.

Copy link

KwstasBol commented Sep 14, 2017

yeah i checked it i hope we find a solution soon! 4.6.1 is the version i guess, as i saw...

@EricDahlvang

This comment has been minimized.

Copy link
Collaborator

EricDahlvang commented Sep 14, 2017

@KwstasBol are you still experiencing this issue?

@KwstasBol

This comment has been minimized.

Copy link

KwstasBol commented Sep 15, 2017

Yes @EricDahlvang still the same httphandler-pipeline error..

@KwstasBol

This comment has been minimized.

Copy link

KwstasBol commented Sep 19, 2017

I am closing the issue, because the solution came. I had to change the Azure app service to bot service which is merged with the bot framework developer envinroment.

@KwstasBol KwstasBol closed this Sep 19, 2017

@iamthewall

This comment has been minimized.

Copy link

iamthewall commented Oct 2, 2017

Hi @KwstasBol . Could you share some detailed insights of what was happening with your bot and how you fix it? I'm facing a similar issue.

@KwstasBol

This comment has been minimized.

Copy link

KwstasBol commented Oct 2, 2017

Yes @iamthewall. Well all of the sudden after being one year online, the bot stopped. This event was due to my using web app at Azure and because of using the older version of BotFramework SDK. Eventually i made the transition to BotService which you can have for free with an Azure subscription and change the code of your app to the current version of the SDK. To put it in a nutshell, never ever again have a bot solution on a web app,only bot service. For more,inform me.

@savahmel

This comment has been minimized.

Copy link

savahmel commented Oct 6, 2017

@KwstasBol Bot service, you mean Azure Functions solution?

@KwstasBol

This comment has been minimized.

Copy link

KwstasBol commented Oct 6, 2017

image
This one, but you must make a subscription firstly. It is said that it is free,but it charged me 1 euro. Nevertheless, it is worth it.

@savahmel

This comment has been minimized.

Copy link

savahmel commented Oct 8, 2017

Thanks

@soloveyalex

This comment has been minimized.

Copy link

soloveyalex commented Oct 17, 2017

@KwstasBol I have the same issue. Tried to migrate my existing bot from web app to bot service. However, I noticed that upon a creation of Bot Service it requires to create a new bot only.
How did you manage to migrate existing bot to the Bot Service?

@KwstasBol

This comment has been minimized.

Copy link

KwstasBol commented Oct 17, 2017

Well, i was not the one migrating the new one,because i do not expertise in C# issues, but there were really small changes. However, i recommend you to consider in developing in Node.js,because it is really fast and more understandable to my opinion and if you have whichever problem in that platfom i could really help you!. So, i could maybe help you if you could provide me with some code, but i dont promise anything as long as it is written in C# :)

@soloveyalex

This comment has been minimized.

Copy link

soloveyalex commented Oct 18, 2017

@KwstasBol It's not a question of programming platform and language.
The problem is when you create Azure Bot Service it creates a NEW bot. With NEW name and MicrosoftAppID. I see no way to tell it "please create Azure Bot Service for already registered and configured bot"

In this perspective my question was regarding your statement "Eventually i made the transition to BotService". I'm wondering to know how to "transit" EXISTING bot rather then create a NEW one.

So, how did you do that? Or, you didn't and just did register a new one with the same code?

@KwstasBol

This comment has been minimized.

Copy link

KwstasBol commented Oct 18, 2017

Okay.Firstly i used the new MicrosoftAppId, there is no problem in using this. Nevertheless, you are right about not having the option of already registered bot. Secondly, certainly the new name is needed everywhere.The facebook keys of course stay the same.Last but not least, the answer to your last question,is that i did a new with the same code.That's all,nothing to worry about.(so facebook data remains, bot framework data changes and becomes new). Hope it helps...

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