>>Hi all,
>>
>>We have a .Net webservice that sends the contents of an XML file to an IIS 6.0 server that works without problem until it gets to a certain size. When the file that we FILETOSTR() gets to over 100K, we get this error: "The underlying connection was closed: An unexpected error occurred on a send"
>>
>>Is there an IIS setting, including those in the Metabase.xml, that can be tweaked to fix this problem?
>Hi Ramil
>
>could it be this
>
>When specifying the ISAPI handler, you can use the registry key,
>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSOAP\SOAPISAP, to change the default
>values of the following three configuration variables:
>
>
> a.. MaxPostSize - the maximum size of the SOAP message that you can POST
>to the ISAPI handler. While this setting help you to keep hackers from tying
>up your service by posting extremely large messages, you may need to
>increase the default size (100 KB) if your service accepts large SOAP
>messages.
>
>
>Nick

Thanks for the help Nick.

We had two settings changed to fixed it. The MaxPostSize was one of the two. Here are the settings that we had to fiddle around, in case other people are interested in the solution.

1. Changed the IIS Metabase.xml - UploadReadAhead = "512000"
2. "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSOAP\30\SOAPISAP"
where we can increase the MaxPostSize to the desired limit. = "512000"