Deploying botbuilder on azure is fine.
But when invoked from botframework I get the internal server error.
Log files show this error in the stack trace of application log.
builder.ChatConnector is not a constructor.
Anything to be done to solve this?
Redeoploying the application to a new azure site did the trick.
Related
I published a simple .NET 6.0 web app with user authentication on my IIS 10.0 web server hosted on Azure.
The application read and write data from a SQL Server 2017 database hosted on another machine on the same virtual network of the web server.
Everything works fine but after a while, even though nobody is using the app, it stop working and send Http Error 503 Service Unavailable and I have to restart it every time from the application pool.
I enabled tracing on the event log, but I don't receive any message explaining this.
These are the application settings:
IIS application settings
I tried to follow these advices but none of them worked:
IIS HTTP Error 503. The service is unavailable
503 “Service Unavailable” error for all apps after installing .NET Core 2.2 Runtime & Hosting Bundle for Windows
.Net core Service Unavailable after Publish to IIS
On the same web server I have other applications but this problem appears only on this one. None of the other apps is using .NET 6, most use .NET Framework 4.7/4.8 and another couple .NET Core 3.1.
I also tried to publish the application on Azure WebApp service and it has the same problem.
1. If you're deploying on IIS, we can install DebugDiag Tools and then use the DebugDiag collection to crawl the dump logs.
2. If you are using the azure app service, it is recommended to get dump in the azure portal.
My Suggestion
Enable Failed Request Tracing, and find which request will cause the Http 503.
Maybe this 503 is not a problem with the code, and it is possible to find some useful information in the log.
Check the EventViewer, try to find the useful info about the application.
Download the DebugDiag Tools, use debugdiag collection to collect the dump file when the issue occured, and use the debugdiag analysis to analyze the dump file and check the stacktrace.
My suggestion can't tell you the root cause directly, but it will help you to find it. You are also welcome to update the useful stacktrace information in the future, and there will be more people to help you.
I'm currently having the issue but using MySQL on a remote server.
Azure WebApp, Azure VM (IIS 10) and AWS EC2.
Http Error 503 Service Unavailable when the database connection timesout or fails to connect and the AppPool failed to restart.
No crashes when debugging in VS via console app.
I changed the hosting model to out-of-process and this solved the issue.
<aspNetCore processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" hostingModel="outofprocess">
I have developed a bot on node.js as a teams app using the yo teams generator. The bot is hosted and deployed on an azure app service web app. The bot was working fine all the while, but started throwing http 500 internal server errors in the past couple of weeks.
I am not sure what has changed, but I am trying to fix this issue but not finding any leads and useful information from appInsights or the trace logs. All I see is the below exception being thrown in appInsights:
"POST to the bot's endpoint failed with HTTP status 500"
The bot works perfectly fine locally, when debugging through ngrok. Please let me know how I can fix this or where I can look for useful logs to help resolve this.
I was able to resolve this with MS on a support ticket. Looks like the fix is to update the configuration setting to reflect the latest version of node from 12.13 to 16.13.0 in the app service config section.
I am using
Ver 4.1.0 Bot emulator
When I tried to use the production endpoint in the bot framework emulator. I have configured the endpoints in the bot file as below with information from the azure. But I am unable to the access it via the Emulator and also it does not connect in the "Test in Webchat" in Azure after deployment via Git to Azure. It works fine locally
It returns the following error
In the channels I see the following error triggered.
I analyzed the issue using Fiddler Trace. I think the tokens are being generated.
But the Emulator is not picking it. As seen in the below screenshot both of the fiddler and emulator refers to the same conversation ID.
what might be the issue that is triggering token failure?
I think the bot service is down at the moment.
I have developed a bot that works perfectly on my local machine and accessible through all channels via ngrok.
However, the Bot doesn’t work on its deployed Azure url which is https://mybot.azurewebsites.com/api/messages A test with the webchat or bot emulator returns an error 500 without further information on exact cause of the issue. How would I debug so that I can find out more information on what's causing the breakdown?
GET, PUT, DELETE request work fine, but everytime i make a POST request I get an 500 status code. I have no idea where to start debuggin or what to look for. My api is depolyed on Microsoft Azure.
Any tips on what to look for or how to solve this issue would be much appriciated. I know a 500 status code, could be pretty much anything, but i find it really wierd that POST is the only request that dosn't work.
I have no idea where to start debuggin or what to look for. My api is depolyed on Microsoft Azure.
Please make sure your API application could run fine locally before you deploy it to Azure. Besides, http 500 error indicates the server encountered an unexpected condition, if you deploy your app to Azure app service, you could remote debugging web apps to troubleshoot the issue. If you publish it as cloud service Web role, you could try to use Azure compute emulator to debug your cloud service on a local machine.