locked
Error 5566 raised only if form is published to https but not if published to http RRS feed

  • Question

  • Hi,

     

    After spending today looking at my error 5566 issue_  (-o'_O-)  _I know in principle what is causing it not to render in forms services.

    SSL in IIS.

    If I publish here:

    If I publish here:

     

    I can not turn SSL off - how can you get round it? Please.

     

    :( sniff

     (-o'_O-) 

     

     

    • Edited by Mike Walsh FIN Tuesday, March 8, 2011 5:55 PM Do not Shout in Titles
    Tuesday, March 8, 2011 5:43 PM

All replies

  • There's no easy answer.  You have to figure out why the server can't browse to the HTTPS URL when invoking your data connections via Forms Services.  When a browser form is opened, all queries are made by the server itself.  So, if your data connections point to HTTP, but your form is being accessed from HTTPS then that is considered crossing site collections.  You can't mix and match your URLs.
    SharePoint Architect || Microsoft MVP || My Blog
    Planet Technologies || SharePoint Task Force
    Wednesday, March 9, 2011 1:20 AM
  • Can you suggest any tools to give further info?

    There is nothing to help in the logs as far as i can see - i searched a few for 5566 - nothing!

     

     

     

     

    Wednesday, March 9, 2011 9:49 AM
  • Can you suggest any tools to give further info? There is nothing to help in the logs as far as i can see - i searched a few for 5566 - nothing!
    I don't think you need tools.  I think you need to go find the errors to see what's wrong.  YOu can't just "search a few for 5566."  Every time you get that error, it logs an entry in the ULS logs within the 14 hive.  YOu have to go find the error details and see what they say.  I mentioned a very important part at the end of my reply, but you didn't comment on it.  It seems pretty cut and dry as to WHERE the issue lies.  You publish to HTTP; it works.  You publish to HTTPS - it cannot access one or more data connections.  This is a very big indicator.  I said that you can't mix'n'match URLs (this includes HTTP vs HTTPS), so did you change the data connections when you published each time?  Did you switch the data connections from HTTP to HTTPS?  If not, then that's a very important thing to do...

    SharePoint Architect || Microsoft MVP || My Blog
    Planet Technologies || SharePoint Task Force
    Thursday, March 10, 2011 7:40 AM
  • 14 hive? Don't you mean the 12 hive?

    The data connection is https. If you config it as http it does not work.

    As for finding the errors - i looked in the logs but nothing mentioned 5566...

    Thursday, March 10, 2011 12:53 PM
  • I see this happen all the time if you don't have your SharePoint Alternate Access Mappings (AAM) configured (or not configured correctly).  The AAM tells the site where to point based off the redirecting url.  See this article on how to configure your AAM:

    http://technet.microsoft.com/en-us/library/cc263208(office.12).aspx

    Thursday, March 10, 2011 7:12 PM
  • Yes, I spent 95% of my time in the 2010 forums, so I said 14 hive.  12 hive is correct.

    "The data connection is https. If you config it as http it does not work"

    The data connections are always HTTPS in both scenarios?

    You don't search for 5566...that's the point.  You have to find InfoPath errors...5566 itself does not get logged.  We're flying blind without the actual error details.


    SharePoint Architect || Microsoft MVP || My Blog
    Planet Technologies || SharePoint Task Force
    Friday, March 11, 2011 3:05 AM
  • OK thanks.

    In your comment of: "Thursday, March 10, 2011 7:40 AM" you said:

    " It seems pretty cut and dry as to WHERE the issue lies." 

    Did you mean by that statement that in your opinion the problem was that the date connection was probably configured as http and not https?

    In relation to the question in your last post which was:

    "The data connections are always HTTPS in both scenarios?"

    Yes they are. If you config it as http InfoPath raises an error in the add a data source wizard.

     

     

    Friday, March 11, 2011 8:54 AM