Hey Jake:
Well, credit Lee for the 8192 web config setting. This essentially limits the length (in bytes) of form data POST/GET to the server. It is most definitely not in MBs--not that I know of anyway. 8192MBs is 8GBs! Yiikes. That would take a day even on a fast connection.
So I would definitely take Lee's advice first. To speed up your server, change the hosts file on your server. Find the name of the sql server. Add this name and the ip address of the web server to the hosts file. Just leave the ip address in the connection string (though I use the sql server name, it should make no difference...just don't put BOTH ipaddress and server name or it will reverse verfity *each* one!). Once the info is correctly entered in the host file (you should find a link on how to do this correctly if you haven't before...the computer name is not the same as the DNS name), I've found an average of a 25-50% faster sql access.
Now, just the fact you are having this problem tells me you need to find a faster server, or a better ISP. I know that doesn't help you at all. But to timeout on a 12K page is not a good sign. Do you host the SQL Server? Is this a dedicated server or are you sharing a server with others? If so, how much RAM is the ISP allocating to your shared server? Is the ISP hosting the SQL server such that there is one SQL server and 200 poor customers like you accessing the same server instance? You may have answered some of this before but I don't remember that far back and it's late.
If you have RDC access to the server, I'd be happy to take 20 minutes and have a look at it. You'd obviously want to change the PW after I left...
Posted By jakejays on 13 Mar 2007 12:09 PM
Thanks Andy, your help is really appreciated. I take it by 'That config setting' you are referring to the httpRuntime setting that Lee discusses above. I've looked at some notes on this and from what I can see the default setting (8192) is in megs not kb so I'm not sure how this could have a baring on a 14kb piece of html being posted through the fckeditor (I'm a newbie so sorry if I've got this wrong).
The production server is currently using an IP in the sql server name setting and not a server name. Are you saying that using an IP (which is specified in the specs I've seen as being an acceptable value) will actually be slower than resolving a machine name? Using the hosts file to get around this would be plausable.
I think the problem is a timeout error. The error is happening both on read and posting any edit. The post actually works but the page needs to be repeatedly clicked on to force it to eventually load and display correctly when logged in. When logged out the page does display fine every time but loads slowly.
The error displayed when logged in starts:
Error: Text/HTML is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException:
Timeout expired. The timeout period elapsed prior to completion of the
operation or the server is not responding. --->
System.Data.SqlClient.SqlException: Timeout expired. The timeout period
elapsed prior to completion of the operation or the server is not
responding. at System.Data.SqlClient.SqlInternalConnection.OnError... etc
Certainly seems to be a sluggish connection issue to the sql server. I've seen other posts (there aren't many with this problem) that mention the need to configure sql server to better handle larger sql queries. Maybe that's the problem here since it is a lot of html being posted.
Many Thanks