We are facing issue in Azure chatbot, LUIS is not responding in Test in Web Chat on Azure. Chatbot is working fine Emulator and integration with direct line. My client is testing always from Azure so it is some critical issue for us. We are using Standard LUIS runtime subscription. It would be great if someone can help us. I did below trouble shooting steps.
Subscription key for standard plan and verify keys , it is correct.
Re-deployed
See application Insights error code is 400 only when i run it from Azure Test in Web Chat
I opened MS support ticket for this issue and find same issue was running at support team side as well. There were no code and configuration change after some time it suddenly start functioning.
Thanks
I'm trying to connect an application I've written with an old on-premise Exchange 2010 server. Obviously this is not supported, I was wondering if Outlook 2010 end users + Exchange online server would allow the use of Microsoft Graph API?
If the Mailbox is an Office365 Mailbox (or you've configured hybrid https://blogs.msdn.microsoft.com/deva/2019/03/16/deep-dive-how-to-configure-exchange-on-premise-server-hybrid-integration-with-office-365-test-rest-api-calls/) then you can use the Graph API to access that Mailbox. The version of Outlook doesn't really matter as the API is strictly service side, but depending on what your actually doing client side you may find a lot client side integration pain and you would be better to upgrade the latest version of Outlook on the clients. That would give you more options when you redevelop your application as you can make use of the new Addin's platform etc.
Im trying to add wsdl web service in windows form application to connect a web service. It gives error of
"The request was aborted: Could not create SSL/TLS secure channel."
here is the screenshot regarding the issue:
I checked the similar questions but they didnt help. How can i get out this issue. im using Windows 10, Visual Studio 2013
Any help is appreciated.
We just received an update to Dynamics CRM 9.0, but it seems like a get a unresolved reference when I try to programmatically access the Organization Service Endpoint.
The Uri I am using for this CRM online instance is https://xxxxxxxxxxxxxtest.api.crm.dynamics.com/XRMServices/2011/Organization.svc?wsdl&sdkversion=9'.
Please let me know if anything has changed that I cannot use this endpoint anymore?
Please check if the following blog article helps you. There are several different possibilities why this is happening, but with version 9, so are easily fixed:
https://community.dynamics.com/crm/b/nishantranaweblog/archive/2018/01/31/metadata-contains-a-reference-that-cannot-be-resolved-https-orgname-crm8-dynamics-com-xrmservices-2011-organization-svc-wsdl-amp-sdkversion-9-error-in-dynamics-365
Hope this helps.
The OData URL is
https://[ORGNAME].crm.dynamics.com/XRMServices/2011/OrganizationData.svc/[EntitySet]
The Organization URL is
https://[ORGNAME].api.crm.dynamics.com/XRMServices/2011/Organization.svc
(Double check the info by going under Settings -> Customizations -> Developer Resources)
2011 aka soap endpoints are deprecated, which means will be retired anytime. So you don’t have much time, earlier is better to convert to Web Api.
Beginning with the Dynamics 365 (8.0) release, a new OData 4 endpoint was added to the Dynamics 365 application stack. This endpoint is known as the Web API. The Web API provides a development experience that can be used across a wide variety of programming languages, platforms, and devices. The Web API is intended to replace the CRM 2011 endpoint, also known as the SOAP endpoint, for accessing the Dynamics 365 organization web service and other provided web services.
As of the release of Microsoft Dynamics CRM Online 2016 Update 1 and Microsoft Dynamics CRM 2016 Service Pack 1 (8.1.0), the CRM 2011 endpoint has been deprecated. The 2011 endpoint will be removed some time after the release of Dynamics 365 version 9. We plan to provide updates to the Dynamics 365 SDK assemblies and tools over the next several minor releases, retargeting them to use the Web API instead of the 2011 endpoint.
Till then check if TLS 1.2 is the issue like discussed here.
Check, please, that option "Don't use proxy server for local (intranet) address" off on Proxy tab in Network settings
I am planning to implement Microsoft Bot framework, using Qna and LUIS, but my organization policy restricts me from using hosting my KB outside premice, Can i host Microsoft Bot framework in house?
You can't host Microsoft Bot Framework on your premises right at the moment. But what you can do is consuming their APIs inside your application.
Please refer this LINK
Thanks