InfoPath Dev

We have a SharePoint 2007 form library that opens in the InfoPath 2007 desktop application. It's a small template with data connections to SharePoint lists; the resulting submitted XML files are about 3 KB in size. The form library has been in use for close to a month. At the beginning, submitting a form would take no more than 30 seconds. Since last week, it now takes between 10 to 30 minutes. After clicking the submit button the client app freezes, and at seemingly random intervals a status window pops up with the message "Contacting the server for information." The form library has less than 500 submitted forms – a relatively small amount, which I don’t believe is large enough to impact performance. I have no idea what is going wrong, and so far our tech support team doesn't have an answer. Has anybody seem this before? Thanks -Mike

Hi Michael and welcome,

SharePoint is slow but not that slow. You shouldn't see impact until you have 2000-3000 forms on MOSS 2007. Microsoft states this as a soft limitation. It wouldn't take 30 seconds though. Have you checked your SharePoint error logs? Does the form library default vidw take time to load? How much memory is on the box? Are there any other line of business processes happening on form submit?

You can try to submit to a Web Service and have it post to SharePoint. We created a Web Service to map XML to SQL and we have found that submit performance is ~4x faster than submitting to SharePoint. Here's a link.

 

Hi Patrick. Thanks for the welcome. I haven't been able to do much, as I'm just the site owner and don't have access to error logs or other admin features. What I can tell you is that the library's default view only takes a few seconds to load, and nothing (e.g. workflow) happens on form submit. Also, I just heard from our tech support group today that the problem is likely stemming from some updates that were run on the server. They didn't give details, but I hope that something went wrong, and once they fix it we'll be back at normal running speeds. I'll post back here if there is anything helpful to share with this forum. Btw, thanks for the link to that DBXL service. It sounds impressive, but we have a very buttoned-down environment and I'm sure it would never get approved - - - - - UPDATE July 21 2010: FYI, our problem is resolved. I never did get a technical answer on what went wrong. Our support group only told us that the problem was caused by some updates on the server, and recent additional updates have restored the library to the original submit speeds.