Recently, I had a lot of trouble configuring InfoPath Forms Services in MOSS to handle a browser enabled form.
A couple of errors were cropping up and typically the Infopath interface for reporting these errors gave no real clue as to the exact nature of the problem.
Also, both these errors mentioned references in the server application log - neither appeared there, which really didn't help matters.
Fortunately, with the right settings in central admin, MOSS has very detailed logging. However, these logs can be large and cumbersome to search through, giving you eye-strain and a headache at the very least.
So, before you even try troubleshooting via the MOSS logs remember to configure the logging to an appropriate level of throttling. Having said that, the config options in MOSS to filter sets of info in the logs is pretty poorly designed imo.
In the Central Admin pages the diagnostic logging event throttling was set to:
Category: All
Least critical event to report to the event log: Warning
Least critical event to report to the trace log: Verbose
Number of log files: 30
Minutes to use log file: 5
----
Configuration/Background:
The InfoPath form uses two web services to retrieve data from an SQL 2005 db - there is no writing to the db.
The web services are hosted on the same web application as the MOSS portal web app but using a different port.
The form is set to use a Trust level of Domain
The form is set to be browser compatible.
MOSS is configured with Enterprise Features enabled & configured for InfoPath Forms Services http://server:12345/_admin/ipfsConfig.aspx
• Allow users to browser-enable form templates
• Render form templates that are browser-enabled by users
• Allow embedded SQL authentication
• Allow user form templates to use authentication information contained in data connection files
• Allow cross-domain data access for user form templates that use connection settings in a data connection file
The full form with web service data connections runs correctly when tested in InfoPath - ie the web service connections to SQL are good.
Issues:
• When the form is published to MOSS and accessed from a form library using the browser interface the form returns the following error:
An error occurred accessing a data source.
An entry has been added to the Windows event log of the server.
Log ID:6932
• No such error is listed in the server application event log
Check MOSS log:
Data adapter failed during OnLoad: Security settings on the server prevent the use of this data connection.
Warning The form could not retrieve data from http://server:10101/webservice.asmx because it would violate cross-domain restrictions. To allow this connection for administrator-approved form templates, enable full trust for the form template, or add the connection to a Data Connection Library.
For user form templates, cross-domain connections must be enabled in SharePoint Central Administration, and all connections must be in a Data Connection Library. For more information, please see the security documentation for InfoPath Forms Services.
Troubleshooting steps:• Converted each webservice data connection in InfoPath (Tools > Data Connection) to MOSS based location (data connection lib):
http://server/Data%20Connections/ This location is manually created in MOSS and used as the target location to publish converted web services data connections (.udcx) from InfoPath.
From here, the converted data connections are saved and uploaded to the admin location '
Manage Data Connections': http://server:12345/_admin/ManageDataConnectionFiles.aspx
Tested the form again and all is good :)
--- key locations to remember for publishing browser enabled InfoPath Forms ---
Central Administration > Applications:
-
-
-
Site Administration:
-
-
-