Hey everybody!
I have a fairly complicated ASP semantic search application that is failing at the first Request.Form on a page with a ASP 0104 (0x80004005) error. Of course this is on a Win2003 server/IIS 6.
I quickly researched this issue and everywhere I go people suggest altering the metabase.xml file AspMaxRequestEntityAllowed property to a larger number. I was passing close to 350K in post data, so an increase fixed it on the development server. Ok, easy enough. But, my question before I make a drastic change on the live servers, for anyone with more in-depth 2003 knowledge than myself is, what is the impact of this? If the default value is 200K and I raise it closer to 1MB is this overhead going to kill me in the virtual memory area?
Most people with this error at various sites were having an issue with a file upload problem. Whereas, mine is strictly ASP based because I have to pass a lot of information in the post with this application (it’s already slimmed down as much as it can be for the Request object). At MSDN documentation they mention that the default value is 200K for this property, but you can increase to 1MB as the general World Wide Web Publishing Service ( level. So, why such a disparity between default values and a standard?
Thanks a lot!
<== Some people say they are afraid of heights. With me its table widths. ==>
I have a fairly complicated ASP semantic search application that is failing at the first Request.Form on a page with a ASP 0104 (0x80004005) error. Of course this is on a Win2003 server/IIS 6.
I quickly researched this issue and everywhere I go people suggest altering the metabase.xml file AspMaxRequestEntityAllowed property to a larger number. I was passing close to 350K in post data, so an increase fixed it on the development server. Ok, easy enough. But, my question before I make a drastic change on the live servers, for anyone with more in-depth 2003 knowledge than myself is, what is the impact of this? If the default value is 200K and I raise it closer to 1MB is this overhead going to kill me in the virtual memory area?
Most people with this error at various sites were having an issue with a file upload problem. Whereas, mine is strictly ASP based because I have to pass a lot of information in the post with this application (it’s already slimmed down as much as it can be for the Request object). At MSDN documentation they mention that the default value is 200K for this property, but you can increase to 1MB as the general World Wide Web Publishing Service ( level. So, why such a disparity between default values and a standard?
Thanks a lot!
<== Some people say they are afraid of heights. With me its table widths. ==>
