I'm new to this site so apologies if formatting or style of question is not as you would expect.We are an ISV in the process of getting a product listed on Microsoft AppSource.
We have a web application that is hosted in Azure and meets the requirements for using Azure Authentication.
Our Web application appears to be functioning normally up to the point when the AppSource team authenticate - which they do successfully - at this point they get a webpage error as follows which says ERR_TOO_MANY_REDIRECTS (see attachment)enter image description here
Can anyone suggest how to get around this ? It seems like it could be simple a proxy issue at the Microsoft end, although its not completely clear to us if this is the case. Interestingly our product acts as a proxy / reverse proxy encryption gateway.
Related
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 am trying to build my own WOPI host using ASP.NET MVC and its WebAPI functions according to this example
https://code.msdn.microsoft.com/office/Building-an-Office-Web-f98650d6
I successfully used that example to connect to my Office Web App Server and I can use that to access files of Excel and PowerPoint in local path and I am able to edit it, but I cannot use it to open word document in editing mode as the Post action handler isn't implemented completely without any response so that it cannot handle any edit request.
In order to add support for editing of Office document, I tried this example with POST request handler based on Cobalt library extracted from Office Web App Server.
https://github.com/marx-yu/WopiHost
With this example I managed to edit ans save all kinds of document with Office Web App Server. However, when I tried to integrate these two together I found that even if I can enter the edit window of Excel and PowerPoint and I can see that Post Requests from Office Web App Server like locking and Cobalt are handled by my WOPI Post API action handler. Those change doesn't take any effect on my local file at all. Moreover, I still cannot edit word document and when I checked the back log of Office Web App Server, I found the error message is Cobalt is not supported while I have already set the SupportsCobalt in CheckFileInfo response to true! Any help is very appreciated!
I think I have exactly what you are looking for. Check out my implementation of the WOPI host. It's an MVC6 app that takes the best from the both examples you are referring to and adds some extra features.
Recently announced at Microsoft Build is the ability to convert an existing ASP.NET Web API to an Azure Mobile Service. I was curious as to if anyone has successfully done this yet, and the steps needed to do so.
Things I've tried thus far:
Added the Azure Mobile Service .NET Backend & Azure Mobile Service -
Entity Framework Nuget Packages to my existing ASP.NET Web API
project.
Resolved an issue with OWIN and AMS(ZUMO) conflicting Startup.cs assemblies.
Ensured the ASP.NET Web API compiles locally, and published as an Azure Mobile Service.
However whenever publishing, it seems I only get a runtime error on the server.
Here was the best example of potentially doing this: http://channel9.msdn.com/Events/Build/2014/3-623
Secondly I've looked a bit into just running the OWIN pipeline via: http://www.strathweb.com/2014/02/running-owin-pipeline-new-net-azure-mobile-services/
I know that this is in a preview mode, but figured some document trail would help!
Can you try adding your existing WebAPI assets to Mobile Services project you create from VS? This will make sure all the right things are wired up. Also, check the Logs tab in the portal for any clues.
This should help..
http://blogs.msdn.com/b/azuremobile/archive/2014/04/10/creating-an-azure-mobile-services-net-backend-from-scratch.aspx
Thanks
Supreet
I have a public facing site e.g. www.mysite.domain.com which I have registered under Google console API to get API_ID & Client_ID. Which I am using in my javascript.
Now I have another site which I have to specially use for reporting purpose e.g. www.reports.domain.com. However when I use my - mywebsite API & ClientID values on reporting site I am unable to see data.
Both sites are on same machine and same instance of application - DotNetNuke framework
Can anyone tell me what more I have to do, so that I can see data on one site on to another.
Thanks,
Avinash
Microsoft has changed the authentication model for new CRM sites from LiveID to Microsoft Online Services. I set up a new site this week and have it up and running but code I wrote that connects to the site using early bound classes fails to authenticate.
My connection string for an older site using LiveIDs looks like this.
I am trying to connect to the new site that uses Microsoft Online Services for authentication with this connection string
I create an instance of XrmDataContext and it seems to work OK until I actually upll data fromthe site. The error I receive is
ACS10002: An error occurred while processing the SOAP body. ACS50012: Authentication failed.
I tried all of the authentication types list here http://technet.microsoft.com/en-us/library/ff681567 and none seemed to work.
I see a lot of forum posts saying that the discovery service URL has changed so I tried adding that to my connection string.
Discovery URL=https://disco.crm.dynamics.com/XRMServices/2011/Discovery.svc
No luck.
Has anyone written code that connects to the new security model? Did you do anything special?
Thanks in advance,
Bill Wolohan
MS released a new version of the SDK on 8/17/2012. I had downloaded the latest on 8/16/2012 and that version did not work. Once I downloaded the newer version and recompiled it worked great. I just had bad timing. :-(