Event ID: 5337 - Business logic failed due to an exception. - InfoPath Dev
in

InfoPath Dev

Use our Google Custom Search for best site search results.

Event ID: 5337 - Business logic failed due to an exception.

Last post 07-27-2009 05:42 AM by a.goodwin. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 07-13-2009 07:42 AM

    Event ID: 5337 - Business logic failed due to an exception.

    I'm getting problems with an admin published form using managed code. The preview in InfoPath works fine but the published form fails when opening with event ID 5337. The server application log has the following entry:

    Event Type: Warning
    Event Source: Office SharePoint Server
    Event Category: Forms Services Runtime - Business Logic
    Event ID: 5337
    Date:  2009-07-09
    Time:  14:37:09
    User:  N/A
    Computer: SERVERNAME
    Description:
    Business logic failed due to an exception.User:    DOMAIN\username,
    Form Name:   FormName,
    IP: ,
    Request:   
    http://address.domain.com/_layouts/FormServer.aspx?XsnLocation=http://address.domain.com/FormServerTemplates/FormName.xsn&SaveLocation=http://address.domain.com/FormLibrary&Source=http://address.domain.com/FormLibrary/Forms/AllItems.aspx&DefaultItemOpen=1
    ,
    Form ID:   urn:schemas-microsoft-com:office:infopath:FormName:-myXSD-2009-05-13T13-53-20,
    Type:    WebException,
    Exception Message:  Security Restrictions on the server are preventing the data connection being used.   (translated from Swedish so this might not be 100% accurate to the standard MS error)

    --

    Continuing to open the form shows the form as expected but the lookup fields are not populated from the secondary data source.
    There are two data sources accessed via webservices:
    1st. SharePoint UserProfileService.asmx
    2nd. the clients own custom webservice to a data source retaining orginisation data similar to Active Directory

    I can access the webservices directly (from the server) without problems, using the same logged in user ID.
    The webservices have not been changed.

    The form is published to MOSS with Domain trust.

    The previous version of the form worked as expected.
    The latest version of the form has had the code updated to better present the returned data from the 2nd data source and throws the error above.

    I've read other forums suggesting the win2k3 server loopback check is blocking this but I don't want to go messing with the registry until I've exhausted other avenues.

    Any ideas would be greatly appreciated!

  • 07-13-2009 07:30 PM In reply to

    Re: Event ID: 5337 - Business logic failed due to an exception.

    I thought browser forms with managed code required Full Trust and administrative approval.  You say you're using Domain Trust with a code-based browser form?

    Since the preview works, then it's definitely a permissions issue with one of the data connections - likely the custom one.  The error is pointing to the user that's trying to access the data source is not allowed.  Are both of your data connections converted to UDC files?  To avoid double-hop from browser forms, you sometimes have to also create an SSO app definition so that the credentials can be passed to that other data souce via the web service.

  • 07-27-2009 05:42 AM In reply to

    Re: Event ID: 5337 - Business logic failed due to an exception.

    Domain Trust was working previously with the form even with code. After some tweaks to the code it seems it doesn't like it any more. I've since republished the form with Full Trust and converted data connections.

    It fails with the following error:

    System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
    at System.Net.HttpWebRequest.GetResponse()
    at Microsoft.Office.InfoPath.Server.SolutionLifetime.WebServiceHelper.GetResponseHelper(WebRequest request, DataAdapterTimer dataAdapterTimer, DataAdapterCredentials credentials, Stopwatch timer, ExecWebRequestExceptionState state, String adapterName, Boolean isQuery)
    at Microsoft.Office.InfoPath.Server.SolutionLifetime.WebServiceHelper.ExecWebRequestSync(XPathNavigator inputSubDOM, Boolean[] inputUseDataset, XPathNavigator resultsSubDOM, Boolean resultUseDataset, XPathNavigator errorsSubDOM, Uri serviceUrl, Uri soapAction, Int64 timeOutMillisec, Solution solution, Document document, String name, Boolean isQuery, DataAdapterTimer dataAdapterTimer, DataAdapterCredentials credentials, Boolean useDcl, Boolean useProxy, Boolean useSelf)

    An entry has been added to the Windows event log on the server.

    Event ID:5337

    Further reading reveals:

    Event Type: Warning
    Event Source: Office SharePoint Server
    Event Category: Forms Services Runtime - Business Logic
    Event ID: 5337
    Date:  2009-07-27
    Time:  13:54:58
    User:  N/A
    Computer: <servername>
    Description:
    Business logic failed due to an exception. (User: DOMAIN\username, Form Name: Formname_v.0.3, IP: , Request:
    http://address.domain.com/_layouts/FormServer.aspx?XsnLocation=http://address.domain.com/FormServerTemplates/Formname_v.0.3.xsn&SaveLocation=http://address.domain.com/FormLibrary&Source=http://address.domain.com/FormLibrary/Forms/AllItems.aspx&DefaultItemOpen=1, Form ID: urn:schemas-microsoft-com:office:infopath:Formname-v-0-3:-myXSD-2009-05-13T13-53-20, Type: WebException, Exception Message: The remote server returned an error: (500) Internal Server Error.
    Server was unable to process request. --> Index was outside the bounds of the array.
    The remote server returned an error: (500) Internal Server Error.
    Server was unable to process request. --> Index was outside the bounds of the array.)

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    Which is essentially the same as the previous event error & leaves me none the wiser really... 


     

     

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