InfoPath Dev

For the past 3 days or so I have been seeing the following weirdness.

 I publish my changed InfoPath 2007 form to a sharepoint site. The publish step, which for other people takes 1-3 seconds, takes about 30 seconds for me. Sometimes the publish ends up successfully occurring - sometimes, the wizard states that the form could not be browser enabled ... even if there is nothing in the form that is non-browser compliant (because the changes tend to be spacing between controls, etc.). If the publish succeeds, the form runs fine.

The other weirdness is that typically after I press the wizard's "close" button, I see a Refresh (Connecting to server) dialog that sits for about 20-30 seconds seconds, followed by an error dialog whose detailed description indicates that

InfoPath either cannot connect to the data source or the service has timed out.

When I look in my PC's event logs, I see:

Is your connectivity to the SharePoint server worse than others?  I've had this when my connectivity was poor, and it just took too long to publish, so it would error.

Connectivity seems fine. When I ping the sharepoint site, it comes back with 0% packet loss and a minimum and maximum response of 0.

Does it happen with other forms or just this one?  Try a new, blank form and test the publish.

It is happening with just this form - and it doesn't occur every time. The form is less than 40k, and has 2 email data connections, a GetUserProfileByName data connection, and a data connection to retrieve a small amount of SharePoint list data.  The latter two are working against the same server used for publishing as well as compatibility checking.

Make a copy of the template and start removing things one at a time - start with the data connections.  Remove one...publish...repeat.  See if there is a point at which the publish process goes back to normal.

One thing to note - when publishing this form, the step of actually publishing to the InfoPath Forms Server takes long enough for a dialog to be seen and read - a few seconds. For other forms, and other users, that happens so quickly the dialog either isn't seen or disappears before being readable.

The machine doesn't seem to be particularly slow for other operations.

Interesting new data point. I was just publishing a new change. The publishing step informed me that it could not publish the form as browser ready.

 I noticed that a couple of the tabs in my browser were pointing to instances where I had executed the form in previous incarnations. So I closed those tabs, made a small change that I could look for the next time the publish indicated the problem, and published.

This time, the publish completed successfully.

 Perhaps the issue is that as the owner, if I happen to have a browser window/tab open somewhere to the application that publishing is not successful? I don't currently issue a "close the form" action, because I want the user to see the "Thank you for submitting your request" page.

Perhaps by not closing the form, it is left "executing" and thus presents a problem when publishing a new version?