Sunday 14 July 2013

GetUserProfileByName Connection Error in SharePoint InfoPath Forms (Error 5566)


Scenario:

My web application uses claims based authentication with windows authentication (NTML). No other authentication provider is used. Whenever I try to connect to the web service from the InfoPath form I get the following error:
An error occurred while trying to connect to a Web service.
An entry has been added to the Windows event log of the server.
Log ID:5566
Correlation ID:fa658c2f-a405-433a-8895-27fb43fd5706

 

Solution

After some further investigation i found that it's actually the "ASP.NET Impersonation" that needs to be disabled under "Authentication Providers" for the web application in IIS.
I've tried this on several web applications and it's very consistent.
The web applications have been running without problems in my environment for several days so I think it's safe to disable it.
Posted by at

15 comments:

  1. iamquadry24 October 2013 at 14:04

    This worked for me mehn

    ReplyDelete
  2. Unknown24 October 2013 at 15:11

    Happy to hear that :)

    ReplyDelete
  3. Unknown5 November 2013 at 05:26

    This worked like a charm. Thanx buddy. But the actual question is: how did you find this solution?

    ReplyDelete
  4. Unknown5 November 2013 at 07:36

    Good to know that this worked for you :)
    I was able to locate the source of the problem from the event viewer then after deep investigation in SharePoint log files i found it...

    ReplyDelete
  5. Yazmin26 November 2013 at 16:27

    Muchas Gracias.... Resolví mi inconveniente..

    ReplyDelete
    Replies
    1. Santiago17 February 2014 at 09:57

      Yasmin Buenas tardes me puedes indicar como llegaste a la solución del problema

      Delete
  6. Idowu Ibrahim9 January 2014 at 02:55

    My case is different...I configured an AAM for external access and the form keeps showing the error. Pls any way out.Thanks

    ReplyDelete
  7. General Knowledge Kiosks14 April 2014 at 22:04

    verry good. So, if you disable the ASP.NET impersonation then the infopath form which you have created does't work as it should be. I hope you are getting what I am trying to say?

    For instance, you are using a web service to fetch who the current user is from AD using "getbyprofilename". If you disable the ASP.NET impersonation authentication then it would not get the desired records.

    ReplyDelete
  8. Unknown12 June 2014 at 11:15

    In my case I was trying to get the logged user on my infopath form, and the error was fixed, however as mentioned on the above comment I didn't get the desired results, on the field I was supposed to get the current user I received the application pool user instead. I will find out another solution

    ReplyDelete
  9. Halim EL BORGI4 February 2015 at 02:24

    The same problem, it tooks the credentials that we putted for the target application we created

    ReplyDelete
  10. Unknown11 February 2015 at 02:33

    add you service account to the infopath connection UDCX file and approve the udcx file:




    it worked for me without changing asp.net impersonation.

    ReplyDelete
  11. Unknown11 February 2015 at 02:34

    This comment has been removed by the author.

    ReplyDelete
  12. Unknown11 February 2015 at 02:35

    not able to paste correctly here: its UDC authentication, having appId and credential type.

    ReplyDelete
  13. Unknown11 February 2015 at 02:36

    This comment has been removed by the author.

    ReplyDelete

Subscribe to: Post Comments (Atom)