Request object error 'ASP 0101 : 80004005'
Unexpected error
/<file>.asp, line <line>
The function returned |. |
This usually occurs with upload components, and can happen when you upload files larger than they can support. This usually is around 2 MB, depending on the component.
If you are writing your own upload script / component, consider using BinaryRead in 'chunks' -- this way, you can write out to your own buffer file as you receive each chunk (so you don't overwhelm the server with a huge in-memory file), and before you read each segment, check if the client is still there by testing Response.isClientConnected.
Some components seem to have no upper bound on file size, except the server's inability to hold the file in the buffer, or the browser's inability to run a script for as long as it would take to transfer). If you believe you are exceeding IIS' ability to buffer files, you can try to increase this limit (see KB #260694. If that doesn't work, then try a different component. ASPUpload, for example, has no problems with files much larger than 2 MB (though according to PS01041741, you'll want to make sure you're using version 3.0 or higher).
Request object error 'ASP 0101 : 80070057'
Unexpected error
/<file>.asp, line <line>
The function returned |. |
If you are using Sybase, see KB #198943 for information on resolving 80070057 issues.
If you are using Informix, make sure you have the latest drivers. You can review IBM's documentation on how to get these drivers installed (let us know if you can find a download, we couldn't!), or you can purchase from DataDirect.
Response object error 'ASP 0101 : 80020008'
Unexpected error
/<file>, line <line>
The function returned |. |
If you are using Oracle, the error above probably means the Response object is trying to deal with a datatype that it doesn't know how to handle. Verify that your query works outside of an ASP environment, and check the datatype of each column that is coming back in the resultset. A way to quickly narrow down the column(s) causing the problem is to alter your SELECT query to only select one column at a time... keep changing this column until you reproduce the error (and we already know you're not using SELECT *, right?).
[ Comment, Edit or Article Submission ]
Share this:
More about:
| Nov |
December 2008 |
Jan |
| Sun |
Mon |
Tue |
Wed |
Thu |
Fri |
Sat |
| |
1 |
2 |
3 |
4 |
5 |
6 |
| 7 |
8 |
9 |
10 |
11 |
12 |
13 |
| 14 |
15 |
16 |
17 |
18 |
19 |
20 |
| 21 |
22 |
23 |
24 |
25 |
26 |
27 |
| 28 |
29 |
30 |
31 |
|
|
|
|
|
|
|
