CheckOutFile and CheckInFile errors - InfoPath Dev
in

InfoPath Dev

Use our Google Custom Search for best site search results.

CheckOutFile and CheckInFile errors

Last post 12-06-2016 12:59 PM by greg.mcallister. 5 replies.
Page 1 of 1 (6 items)
Sort Posts: Previous Next
  • 11-17-2014 09:59 AM

    CheckOutFile and CheckInFile errors

    I am running SP 2013 and IP 2013.  I would like to place a button on a form that will check out the form after it is open.  I also want to check in the form on submit.  I configured the data connections to the web services and the rules per Hilary's posts, but I am running into some issues.  When the CheckOutFile rules run, the form is checked out to "System Account", and I cannot check it back in, or discard check out, from the list.  When I try to run the CheckInFile rules to check it back it, it fails with error 5566.

    Shouldn't the CheckInFile and CheckOutFile data connections be submit connections instead of receive?  Hilary's post says to create it as a receive connection, but it seems like I am wanting to write to the list (set to checked out, or set to checked in).  I am sure Hilary is right, I am not that familiar with web services.

    I had been struggling with the 5566 error during that last few weeks when trying to configure a connection to the web services that would populate a field with the currently logged in user.  I solved that through a combination of placing the data connection files in a local library, disabling LoopbackCheck on the web frontends, using a substring of my username in the Load rules, and by creating a secure store ID for the data connections to use. I suspect the issues with CheckIn/CheckOut are related to 2013 and claims, but I am not sure how to troubleshoot them. 

    The 5566 error reads as follows:

     Log Name:      Microsoft-SharePoint Products-Shared/Operational
    Source:        Microsoft-SharePoint Products-InfoPath Forms Services
    Date:          11/16/2014 11:17:01 PM
    Event ID:      5566
    Task Category: Runtime - Data Connections
    Level:         Warning
    Keywords:     
    User:          NT AUTHORITY\IUSR
    Computer:      sp-prodwfe1.seattlecca.org
    Description:
    The following query failed: CheckInFile (User: 0#.w|scca\mpalmgre, Form Name: xMatt2, IP: , Connection Target: https://apps.seattlecca.org/bct/DataConnectionLibrary/CheckInFile.udcx, Request: https://apps.seattlecca.org/bct/_layouts/15/FormServer.aspx?XmlLocation=/bct/xMatt2/test1.xml&ClientInstalled=true&DefaultItemOpen=1&Source=https://apps.seattlecca.org/bct/xMatt2/Forms/AllItems.aspx, Form ID: urn:schemas-microsoft-com:office:infopath:xMatt2:-myXSD-2014-11-04T22-21-45 Type: DataAdapterException, Exception Message: The remote server returned an error: (500) Internal Server Error.
    Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.
    The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
    The remote server returned an error: (500) Internal Server Error.)
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-SharePoint Products-InfoPath Forms Services" Guid="{A3499A35-DB34-421A-94FC-4D76522BEAB3}" />
        <EventID>5566</EventID>
        <Version>15</Version>
        <Level>3</Level>
        <Task>5</Task>
        <Opcode>0</Opcode>
        <Keywords>0x2000000000000000</Keywords>
        <TimeCreated SystemTime="2014-11-17T07:17:01.752477600Z" />
        <EventRecordID>384706</EventRecordID>
        <Correlation ActivityID="{97ECCC9C-AC85-10A5-8453-5311B8D88745}" />
        <Execution ProcessID="4772" ThreadID="8748" />
        <Channel>Microsoft-SharePoint Products-Shared/Operational</Channel>
        <Computer>sp-prodwfe1.seattlecca.org</Computer>
        <Security UserID="S-1-5-17" />
      </System>
      <EventData>
        <Data Name="string0">CheckInFile</Data>
        <Data Name="string1">0#.w|scca\mpalmgre</Data>
        <Data Name="string2">xMatt2</Data>
        <Data Name="string3">
        </Data>
        <Data Name="string4">https://apps.seattlecca.org/bct/DataConnectionLibrary/CheckInFile.udcx</Data>
        <Data Name="string5">https://apps.seattlecca.org/bct/_layouts/15/FormServer.aspx?XmlLocation=/bct/xMatt2/test1.xml&amp;ClientInstalled=true&amp;DefaultItemOpen=1&amp;Source=https://apps.seattlecca.org/bct/xMatt2/Forms/AllItems.aspx</Data>
        <Data Name="string6">urn:schemas-microsoft-com:office:infopath:xMatt2:-myXSD-2014-11-04T22-21-45</Data>
        <Data Name="string7">DataAdapterException</Data>
        <Data Name="string8">The remote server returned an error: (500) Internal Server Error.
    Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.
    The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
    The remote server returned an error: (500) Internal Server Error.</Data>
      </EventData>
    </Event>

  • 11-24-2014 09:28 PM In reply to

    Re: CheckOutFile and CheckInFile errors

    Hi Mattpalmgren,

    I'm sorry to hear about the errors you are receiving. According to Hilary's webinar InfoPath: Migration Issue from SharePoint 2010 to 2013, the 5566 error is a common issue on a SharePoint 2013 environment. One solution for this error is to convert the data connection to a UDCX connection and add an authentication to the UDCX. Hope this helps.

    Don Stephen Lambatin / Support Engineer
    Qdabra Software
  • 07-31-2015 07:42 AM In reply to

    Re: CheckOutFile and CheckInFile errors

    Hi,

    we're trying to configure check in /check out using the secure store credentials in a UDCX connection, but when the form is being checked out, the credential referenced in the udcx connection file is being displayed as the check out to value on form, not the user logged into sharepoint and working with the form

    <udc:Authentication><udc:SSO AppId="InfoPathGUPBN" CredentialType="NTLM"/></udc:Authentication> 

    • using sharepoint 2013 with claims (Active Directory)
    • designed form using infopath 2013
    • infopath form has Check in / Check Out data connections configured
    • infopath form is published directly to a forms library
    • both data connections have be converted to UDCX connections
    • UDCX connections are using the Secure store authentication

    secure store credentials has full control through central admin user policy on the web application

     has anyone found a solution to ensure the user working in the form is being displayed as the check out user

     

    thanks

     

    giovanni 


  • 08-03-2015 06:15 AM In reply to

    Re: CheckOutFile and CheckInFile errors

    Hi Giovanni,

    I have researched a bit and found this blog but it did not indicate adding credentials to the UDCX:

    Create an XTP to Check In and Check Out forms using UDC files

    Maybe this blog could help you out with the logic for checking your form in/out. Could you try this out and let us know if it works?

    I hope I am able to point you toward the right direction.

    Regards,

    Don Stephen Lambatin / Support Engineer
    Qdabra Software
  • 08-16-2016 11:49 AM In reply to

    Re: CheckOutFile and CheckInFile errors

    Hi, I have exact same issue. Where checkout and chekin happens using SSO credential i.e. admin names instead of logged in user name. How did you went on solving this one? Shruti
  • 12-06-2016 12:59 PM In reply to

    Re: CheckOutFile and CheckInFile errors

     Same issue here as well. I have been able to get all my form locking processes working but the Checked Out By name ends up being the SharePoint Service account set as the credential user and password for the Secure Store Service Application. I have tried Individual as well as Group and Group Ticket without any difference. Any assistance would be appreciated as this would kill a SharePoint 2013 migration of 2500 users if unable to lock a browser based InfoPath form to a user as it is done in non-claims based environment.

Page 1 of 1 (6 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.