locked
CRM Online SDK -- value cannot be null. parameter name identity provider RRS feed

  • Question

  • Hello,

    I subscribed to a online CRM trial.

    I am trying to access  CRM entities using SDK samples.

    So I am getting the above error "value cannot be null. parameter name identity provider".

    I already have windows identity foundation installed.

    Experts , please help me to solve this issue.

    Thanks

    OneK


    Friday, March 4, 2016 4:51 AM

All replies

  • It would help if you could post your code, along with which line is causing the error. Also, how is your code running - i.e. if it .Net code, is it a plugin, external .Net application or Silverlight application ?

    Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk

    Friday, March 4, 2016 6:06 AM
    Moderator
  • Hello david,

    Thanks for your Reply.

    Here is the code below.

    using (_serviceProxy = new OrganizationServiceProxy(OrgUri, ull,Creds, null))
                    {
                        _service = (IOrganizationService)_serviceProxy;
                       
                        Entity account = new Entity("account");
                        account["name"] = "Fourth Coffee2";
                        _accountId = _service.Create(account);                   
                        
    }
    

    I am getting error "value cannot be null. parameter name identity provider" exactly at the _service.create Statement.

    Thanks

    oneK

    Friday, March 4, 2016 9:50 PM
  • Hi oneK,

    Are you able to make sure that your parameters OrgUri and Creds are both not null and correct?

    Cheers,

    Stanley


    • Edited by Stanley_Lai Sunday, March 6, 2016 10:56 PM
    • Proposed as answer by OnlyoneK Wednesday, March 9, 2016 8:45 PM
    Sunday, March 6, 2016 10:55 PM
  • Hi Stanley,

    The OrgUri and Creds are not null and Correct.

    I was able to enter in to the using statement and create an Org service.

    Im getting the error when doing the crud operations.

    THanks

    Onek

    Monday, March 7, 2016 12:36 AM
  • After hours of debugging the code, I found out that user Credentials were changed by other developer.

    Finally made it work after updating credentials.

    Thank you all for your Support. 

    • Proposed as answer by OnlyoneK Wednesday, March 9, 2016 8:37 PM
    Wednesday, March 9, 2016 8:37 PM