The parameter 'token' cannot be a null or empty string - Provider Hosted App SharePoint 2013

Hi,

Today while my research on SharePoint Provider hosted app with Azure, after deployment I was greeted with "The parameter 'token' cannot be a null or empty string ".
I was almost crazy behind finding the cause. However finally I found some points which leads me to resolve this error.

  • The ClientID in your AppManifest.xml and in your Web.Config should be same.
  • In AppManifest.xml file domain reference to Azure should be HTTPS rather than HTTP.
  • Should have proper permission on web,list,site collection according to your app.
    •   
    Happy coding!

    Comments

    1. UnknownJanuary 16, 2015 at 6:17 AM

      Hi Firstly thanks any idea how do we solve this error i am facing the same problem when i am connecting to office 365 using provider hosted apps please suggest.

      ReplyDelete

    Post a Comment

    Popular posts from this blog

    Search Query by ContentType name issue

    I ran into very weird issue in SharePoint Search while querying the items using ContentType name. Query: ContentType={content type NAME} This was giving me the result of content type, however some extra data/results where coming along in the result. There was no clue what is failing there. Spent few hours and got very useful tip from Search Guru,  MIKAEL SVENSON   that not to use ContentType but to replace that with  SPContentType. Modified Query: SPContentType={content type NAME} Learning: We should use SPContentType instead of ContentType. As Contenttype also includes the mime type and not just the name and may cause issues. SPContentType only stores the name. I hope this small piece of information will save your time!
    Read more

    Search Result Webpart,Filter result If QueryString is present in URL

    Image
    There was a requirement to filter the search result based on QueryString present in url, and if no QueryString present then should populate all the results. Issue was simple to resolve if every time there is QueryString present, then below Query will do the job. Below filtering the result by checking managed metadata property equals the query string value. Above query was filtering the result based on QueryString given in URL. However it fails if there is no QueryString present in url.  "No result found" message appear. Ideally should populate all the results. And filter should be optional in query for this scenario. So I need to modify the query and to add some condition like, if QueryString present then check managed metadata property equals the query string value, else no. To achieve this, there is syntax  {searchboxquery} {? <some KQL expression> } , If MyParameter querystring is not present in URL,  then just first part of KQL query will e
    Read more

    SharePoint 2013 Workflow gets canceled automatically

    Hi, I was struck with the error of Workflow gets canceled automatically. Scenario was : A new SP 2013 installation, one server with SP, WF, etc and the other is simply SQL Server. Went through the installation steps for Workflow including the powershell bits. In designer, I am able to create a simple workflow and select 2013 as the type. When the workflow is run, is shows internal status is canceled and has the following error text below. RequestorId: 55c6990b-c4a6-352c-4a5b-449fc1aecac4. Details: System.ApplicationException: HTTP 401 {"x-ms-diagnostics":["3001000;reason=\"There has been an error authenticating the request.\";category=\"invalid_client\""],"SPRequestGuid":["55c6990b-c4a6-352c-4a5b-449fc1aecac4"],"request-id":["55c6990b-c4a6-352c-4a5b-449fc1aecac4"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"SPRequestDuration":["61"],"SPIisLatency":["1&
    Read more