General

Re: Load Balancing

qwer — Mon, 23 Jan 2006 21:44:40 GMT

Thanks a million Patrick

Re: Load Balancing

Patrick Halstead — Wed, 18 Jan 2006 07:11:38 GMT

Hi Qwer,
Microsoft is looking into this and I hope to have more information for you shortly.

Patrick Halstead [InfoPath MVP]
InfoPathDev

Re: Load Balancing

qwer — Thu, 12 Jan 2006 22:34:14 GMT

Hi Patrick,

In regards to the problem mentioned above where an InfoPath loads several times on a clustered server environment. I have checked the log files on the servers and it appears InfoPath is not LOADing a form several times, but they are merely HTTP calls to the servers.

What confuses the user is InfoPath display an "opening form" dialog box and it appears to the user it is loading several times. But really, only one form ever gets displayed on the view.

Is there a way to hide the "opening form" dialog box?

Re: Load Balancing

Patrick Halstead — Mon, 09 Jan 2006 06:59:24 GMT

Hi Qwer,
Thanks for your patience. I just sent e-mail to MS. More soon (I hope!)

Patrick Halstead [InfoPath MVP]
InfoPathDev

Re: Load Balancing

qwer — Sun, 08 Jan 2006 21:15:53 GMT

Thanks Patrick

Re: Load Balancing

Patrick Halstead — Fri, 06 Jan 2006 06:19:44 GMT

Great question for MS. I will ask them.

Patrick Halstead [InfoPath MVP]
InfoPathDev

Load Balancing

qwer — Thu, 05 Jan 2006 22:35:27 GMT

This is a publishing question. Has anyone hosted their forms on a web server with load balancing?

In brief, my organisation's intranet is made up of 8 servers with an identical image and users are automatically allocated access to one with the least load at the time. Each of the 8 servers has a unique identifier (eg, web01, web02, etc.) and they all use an alias ofhttp://intranet.

This architecture caused a problem as a result as InfoPath is able to resolvehttp://intranet into the physical server name (\\webxx). Therefore, usinghttp://intranet/xxxx.xsn as the publishURL causes "Insufficient Privilege" error because InfoPath knows a form is in \\webxx.

Therefore, I had to publish the form using \\webxx\xxxx.xsn. It works fine if the I access the form using \\webxx\xxxx.xsn, but if I access it using the aliashttp://intranet/xxxx.xsn, it unexpectedly loads the form several times before it pops up onto the view. I really need to get it workinghttp://intranet because there are policies that the physical server names cannot be exposed to employees. Has anyone experienced the same problem in this clustered environment and has a solution?