I am new in using Bot Builder Framework. I was following this tutorial from Microsoft https://learn.microsoft.com/en-us/azure/cognitive-services/qnamaker/tutorials/integrate-qnamaker-luis.
I am using the code from GitHub(NLP-with-dispatch) and set up all the necessary requirements DISPATCH, Luis, Qnamaker, etc.
But after running the code using the bot emulator I got this error message.
"No such host is known".
BTW, I already updated the appsettings.json and bot config.
Anyone experience this?
I actually just created a PR for this, since the issue is so common.
With that sample, make sure that LuisAPIHostName in appsettings.json is just your LUIS region (ie westus).
Related
I'm having a pretty basic problem - trying to upgrade my botkit app from 0.7.x -> 4.x.
I've used yo botkit to generate a new v4 bot, according to these instructions. Now that I try to configure the bot with slack I can't verify the events api the same way I did with the v0.7 bot.
When I go to slacks events api url and try to verify a request url, my node app is responding with a 404 not found error.
Looking at the code, it seems that the endpoint for /slack/receive which slack is trying to access is indeed removed from the code.
This prevents my bot from listening to messages and responding to them.
When I was configuring the bot in v0.7.x, I just cloned this repo and followed these instructions, but when I try to follow these instructions with the starter provided for v4.x the guide fails and I can't find a more relevant one.
Any idea what I'm missing here?
The url has changed in v4 - it is now /api/messages
I created new LUIS bot from azure portal, and tested in "Test in Web Chat", it was working fine.
I created new app in luis.ai portal, with few indents and entities, also trained and published. Now updated the application id and and app key under Application settings for Luis APPId and LUIS API Key respectively in Azure portal, after that if i type anything in "Test in web chat" I'm consistently getting this below message
"Sorry, my bot code is having an issue."
If anyone solved this plz let me know, I'm not sure what mistake am making here
I tried recreating the scenario and it worked for me.The error message which you are getting is the default bot notification of an unhandled exception. I would suggest you do the following steps:
1.Download the bot code and run it locally to check for errors.
2.Try debugging the bot using ngrok.
You can use the documentation here to troubleshoot the issue.
I have a .NET Bot Framework bot created using the template and tested on other channels and in the dashboard.
I've added the Skype for Business channel and performed the PowerShell cmdlets for my tenant. However, I constantly get the reply "Error happened in contacting target user".
I looked in the Bot Framework Dashboard for issues, and the problem is that the Bot Framework is getting back a 401 Unauthorized from my code. Remember that this works fine in other channels.
Suspecting a problem with how Skype for Business passes (or doesn't pass) the authentication tokens I commented out the BotAuthentication decorator. Suddenly everything works fine. So I think there's a problem with the Skype for Business channel and how it passes the authentication credentials, as this situation clearly isn't ideal.
Just to answer my own question on this. The reason I was seeing this problem was because I did not have the latest version of Microsoft.Bot.Builder. I needed to be running 3.5+ and I wasn't. I've written it up here (along with instructions for updating the NuGet package if you need that): https://blog.thoughtstuff.co.uk/2017/06/how-to-enable-your-bot-framework-bot-on-skype-for-business-part-2-or-how-i-followed-the-instructions-and-it-worked/
I have created a bot service app in Azure that works fine when I create it. I go through the Microsoft App ID, password screen and it loads the chat emulator and code in browser (using the LUIS template and node.js language). After sometime, if I go back to load that app service from Azure dashboard, it keeps giving me "An Internal error occurred at the server" error message. I am not sure if I shouldn't be going to the newly created Bot Service from dashboard? I did this 3-4 times already, with new names, new RG etc., it's the same issue every time.
Thanks
Unfortunately this looks like a bug, there are are two open issues right now on the SDK's repo that look very similar to yours. Here is one of them; 'InternalServerError - Bot & QnA Maker'.
Regarding the downvote, it might be because there isn't a screenshot of the issue which usually helps in answering questions. Also, explaining the steps you undertook or compared against would have helped give a clearer picture for the community to answer.
I followed the instructions that were given in the online tutorial (Building a bot from 0 to 60), but the emulator doesn't work. It keeps on telling me "401 unauthorized". I looked online and some of you suggested that https should be used. However, when I did so the emulator displayed a message saying it cannot connect to a remote server. Some of you also suggested changing Appid to MicrosoftAppid and doing the same thing with the password, but again that didn't work. Some of you even suggested leaving both the Appid and password blank in both the emulator and Web.config and that didn't work as well.
Does anyone know how to fix this issue? (I also made sure that everything (like the port and my Appid and password) was written correctly, so there shouldn't be any syntax or user errors).
Thanks
If you are using v3.0.0, please note that there is currently an issue with authentication if you use node.js. The suggested workaround is to deactivate authentication by not handing over any appId and appPassword in your connector options in your bot and do not use any auth data in your emulator.
Also note as #Thegaram said that you use a matching emulator to the botbuilder version you use. If you have the v0/v1 of botbuilder, you should use the Bot Framework Emulator (v1), if v3+, then the Bot Framework Channel Emulator (v3+). They will have trouble connecting to mismatching versions.