These errors may be caused by multiple reasons, such as:
1. AspUpload is not installed on the server
Make sure the AspUpload component is installed on the server. XUpload requires
AspUpload to capture uploaded files.
2. The Server and/or Script <PARAM>'s are invalid
When uploading files to the server, XUpload invokes
a server-side upload script. The location of this script
is specified by the parameters
<PARAM NAME="Server" VALUE="server address">
<PARAM NAME="Script" VALUE="/path/script.asp">
Make sure these parameters are correct. All XUpload code samples
use localhost as the Server address which
is convenient for testing on a single machine, but must be changed to the actual
server address in a production environment.
3. Upload script throws an error
This is the most common cause of a 12030 error. The upload script pointed to by the Server/Script parameters
may not be working properly. There can be many reasons
why an upload script would fail, such as failure to create the Upload object,
a permission problem when saving an uploaded file, invalid syntax, etc.
You must make sure that your upload script is functional. The best way to do it is to
create a simple HTML file with an upload form
and point this form's ACTION attribute to the same URL as your Server/Script parameters. Then
try to upload a small file using this form. If your upload script has a problem,
you will be able to see it immediately. Your form may look like this:
<FORM ACTION="http://server/path/script.asp" METHOD="POST" ENCTYPE="multipart/form-data">
<INPUT TYPE="FILE" NAME="FILE1">
4. SSL is used but corresponding PARAM is not set
If your upload script is running under Secure Socket Layer (SSL), you
must include the following parameter in your <OBJECT>:
<PARAM NAME="SSL" VALUE="True">
5. Server-side upload script times out
When uploading large files, the upload process may take several minutes
and as a result the server-side upload script may time out.
You should increase the Script Timeout value
for your virtual directory from MMC (IIS4) or Internet Services Manager (IIS5)
under Application Configuration/App Options.
6. AspUpload 3.0+ is used with XUpload 2.0 (or earlier).
Version 3.0 and higher of AspUpload requires
that the Content-Type header of an upload
POST be set in accordance with RFC 1867. XUpload 2.0 and earlier
did not set this header properly. Therefore,
if you use AspUpload 3.0 or higher on the server,
you must use XUpload 2.1 (or higher).
To upgrade to XUpload 2.1, follow this link:
Upgrades from XUpload 2.0 (and earlier) to XUpload 2.1 are free.
7. See Article PS02041393
8. If your server is running Windows 2003, see article PS030911112
9. If your server is running IIS Lockdown and URLScan, see article PS030924114