Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Dec 21, 2009 11:31 PM by cindy998
May 25, 2007 09:36 AM|LINK
why don't you open your own thread for your problem?
May 25, 2007 09:42 AM|LINK
sory for interfaring
i have posted new thread but cant even see that in list
may b pending in the queque
i didnt find any response
may be my request is pending in the queue for administrator to have a look at it
May 29, 2007 03:04 AM|LINK
To overcome the problem of sending large files via web services you can split a file into X number of file fragments, and then send them all to the server, where they would be combined to reproduce the original file on the server.
Here you can find sample code:
May 29, 2007 06:33 AM|LINK
thanks for the response. I used a similar solution to resolve the problem temporary. Is there no other way to send larger files? The max. file size is 10 MB, when I try to send an higher file size, the connection would be closed. If I can send files up to
20 MB, I'm happy....
May 30, 2007 08:25 AM|LINK
How about using the Message Transmission Optimization Mechanism (MTOM) specification for transmitting large amounts of data to and from Web services.
To send and receive the largest possible SOAP messages, you can set the value of the <maxMessageLength> element to -1.
Please have a look at below links for sample code:
Jun 01, 2007 10:50 AM|LINK
Thanks a lot! I have installed WSE 3.0 and reconfigured the web.config. Now I'm able to send files with size up to 70 MB. I don't understand, because now the limit is by 70 MB, but it works. Another configuration, that didn't work is to set the maxMessageLength
(described in the MSDN article) to an higher value. It says that httpruntime don't support a property named "maxMessageLength"....
Oct 31, 2007 02:24 PM|LINK
The link to the article on MSDN is now
Dec 21, 2009 11:31 PM|LINK
I had the same error a week ago and I found a solution here :
There are several solutions for this. You can find the list of solutions here: