Please read the Installation section BEFORE reading this section.
Problem: When uploading the following error messages constantly shows up, but download is working perfectly.
ERROR: java.net.SocketException: Connection reset by peer
ERROR: java.net.SocketException: Socket write failed
Case 1: You may have enabled URLScan and/or IIS Lockdown, check the log file:
%WINDOWS%\system32\inetsrv\urlscan
[05-19-2004 - 09:38:27] ---------------- Initializing UrlScan.log ----------------
[05-19-2004 - 09:38:27] -- Filter initialization time: [05-18-2004 - 15:50:12] --
[05-19-2004 - 09:38:27] Client at 172.16.5.31: Content-Length 121098132 exceeded maximum allowed. Request will be rejected. Site Instance='10', Raw URL='/SpeedCheck_upload.aspx'
Edit urlscan.ini and add the following line: (The value is in Bytes: e.g. 104857600 = 100 MB)
Remember to RESTART IIS
[RequestLimits]
MaxAllowedContentLength=104857600
Case 2: You haven't setup the Web.Config file properly. (The value is in Kilo-Bytes, e.g. 102400 = 100 MB)
Refer to the Upload Configurations for details:
<system.web>
<httpRuntime maxRequestLength="102400" />
</system.web>
Case 3: Firewall and other external factors
Check your firewall log file to see if why the connection get dropped. Connection reset caused by many factors, it could also be a bad connection too. Consult with your network administrator.
Problem: When uploading is almost done, the following error messages constantly shows up:
ERROR: Cannot detect <speedcheck_success> or <speedcheck_failure>
This can be running out of memory problem. Check your server Event Viewer's Application Log to see if you can some clues. In our test, we pushed the limit by uploading a 115 MB file to the server Pentium 4, 1.8 GHz, 512 MB Ram with IIS 5.0 + ASP.NET 1.0. The server returned the error message. This has nothing to do with SpeedCheck, it is ASP.NET/IIS memory handling issue. The solution is to use a smaller sample size or add more memory.
For other problems, please refer to FAQ