![]() ![]() We also made corrections to InstallNETFX.cmd and deployed the project to Azure using NET Framework 4.6.2. We created the certificate by following this document: īy the way, before we opened this issue, we loaded HueBot solution and just fully recreated it from scratch, using NET Framework 4.6.2, Microsoft Azure Tools 2.9 and latest versions of all NuGet packages except. Inner Exception: Invalid provider type specified. ![]() Unhandled Exception: It is likely that certificate 'CN=' may not have a private key that is capable of key exchange or the process may not have access rights for the private key. We still couldn't publish your solution to Azure because during the publish process we have the error: When VS 2017 converts your HueBot solution to the format that can be supported by Microsoft Azure Tools 2.9 it loses references to several libraries (, ). Hope you guys has information on how to resolve this or what i'm doing wrong. Having that fixed and corrected and running, the issue that still exist, skype cannot make calls to the bot. I don't know if I'm on the right path of doing that and using that certificate coz it seems that the service is happily running. Yey! I uses the certificate thumbprint that was created after the deployment of the sample app. It's always recycling or on busy/restarting, but that I think is the only way to get it deployed (if you don't have a certificate yet.) I manage to have the WorkerRole instance in Running status by un-commenting and putting the correct values on the certificate and serviceDnsName. However, doing that causes the WorkerRole instance not functioning. I was able to deploy the sample to the Azure Cloud by commenting those config setting related to Certificate. ![]() I had that issue as well and I couldn't even downgrade the Azure tool version on the VS 2015 I'm using. I connected the Visual Studio 2017 debugger to the published job worker and saw that the controller didn't receive any requests.Īpp ID: bf0f99b0-1836-4548-b1c6-6540ee25d191Ĭould you help me what is incorrect in the bot configuration or maybe you have any other recommendations? But we are working on it." And at the bot framework dashboard, I have the issues: "There was an error completing this request due to an internal channel failure." I always get a response like here: "You can't talk to this bot just yet. I followed instructions for registering a bot ( ) and deploying a real-time audio-video bot ( ) to run the HueBot sample ( ).īut after my bot was added to my skype contacts I cannot make a video call to my bot. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |