|
| |
|
aspSmartUpload FAQ
|
|
1) |
FAQ: does aspSmartUpload work
on Windows 2003 server ?
Yes, last versions of aspSmartUpload work fine on the
Windows 2003 server.
If you upgrade your OS and used an old version of
aspSmartUpload, you have to download and setup
aspSmartUpload 3.2+.
IIS6.0 prevent the upload of
files more than +200Kb.
For IIS6.0 users, the
AspMaxRequestEntityAllowed property specifies the maximum
number of bytes allowed in the entity body of an ASP request. If
a Content-Length header is present and specifies an amount of
data greater than the value of AspMaxRequestEntityAllowed,
IIS returns a 403 error response. This property is related in
function to MaxRequestEntityAllowed, but is specific to
ASP request. Whereas you might set the
MaxRequestEntityAllowed property to 1 MB at the general
World Wide Web Publishing Service (WWW Service) level, you may
choose to set AspMaxRequestEntityAllowed to a lower
value, if you know that your specific ASP applications handle a
smaller amount of data.
Open your MetaBase.XML which is located in c:\Windows\System32\Inetsrv
find the line "AspMaxRequestEntityAllowed" and change it to
"1073741824".
This change does not require stopping IIS, but to make the
Metabase.xml file write-able, you need to go to the IIS control
panel, right click the server, select properties, and check off
the box that says "allow changes to MetaBase configuration while
IIS is running".
|
|
2) |
FAQ : Uploading Large files under
IIS6.0
IIS6.0
prevent the upload of large files (+200Ko)
For IIS6.0
users, the AspMaxRequestEntityAllowed property specifies
the maximum number of bytes allowed in the entity body of an ASP
request. If a Content-Length header is present and specifies an
amount of data greater than the value of
AspMaxRequestEntityAllowed, IIS returns a 403 error
response. This property is related in function to
MaxRequestEntityAllowed, but is specific to ASP request.
Whereas you might set the MaxRequestEntityAllowed
property to 1 MB at the general World Wide Web Publishing
Service (WWW Service) level, you may choose to set
AspMaxRequestEntityAllowed to a lower value, if you know
that your specific ASP applications handle a smaller amount of
data.
Open your MetaBase.XML which is located in c:\Windows\System32\Inetsrv
find the line "AspMaxRequestEntityAllowed" and change it to
"1073741824".
This change does not require stopping IIS, but to make the
Metabase.xml file write-able, you need to go to the IIS control
panel, right click the server, select properties, and check off
the box that says "allow changes to MetaBase configuration while
IIS is running".
|
|
3) |
FAQ: does aspSmartUpload work on
Windows 98?
aspSmartUpload is working fine on the Personal Web Server on
Windows 98.
|
|
4) |
FAQ: On which Web Server does
aspSmartUpload work?
aspSmartUpload works with any web server that supports Active
Server Pages. We recommand using IIS3+ on Windows NT platform.
|
|
5) |
FAQ: With which browser does
aspSmartUpload work?
Any web browser that is compliant with RFC 1867 should work with
aspSmartUpload.
|
|
6) |
FAQ: Does the SaveAs method always
overwrite files?
The saveAs method always overwrites the existing files.
|
|
7) |
FAQ: Can aspSmartUpload be
installed by an ISP?
The Upload components are often a fault of security in
particular for the ISP, this is why aspSmartUpload offers many
parameters in the registry which makes it possible for a
provider to make safe the use of the component.
|
|
8) |
FAQ: Can aspSmartUpload upload
multiple files?
aspSmartUpload can upload multiple files from several file input
elements on an HTML form. To upload multiple files, refer to the
sample #1 and the sample #2. |
|
9) |
FAQ: Does aspSmartUpload support
BLOBs type?
Upload into a database and/or a download from a database is
possible with aspSmarUpload, even for the BLOB type (Binary
Large Objects)
|
|
10) |
PRB: Server.CreateObject causes
error '800a01ad' ActiveX component can't create object
This error is referenced by Microsoft (article ID : Q194801).
This error is usually generated because aspSmartUpload.dll are
one of the following: Missing from the system, Not in the system
path, Not accessible by the system because of security settings.
|
|
11) |
PRB: aspSmartUpload error
'800a0009' Subscript out of range
This error occurs when the asp is directly executed instead of
being called from an HTML form with an ENCTYPE="multipart/form-data"
tag.
|
|
12) |
PRB: aspSmartUpload error
'800a0035' File not found : aspsmartuploadutil.dll
This message occurs when the aspSmartUtil dll isn't in the PATH.
The message may be : aspsmartuploadutil.dll was loaded, but the
DLLregistryserver entry point was not found. DLLRegisterServer
may not be exported, or a corrupt version of DLL may be in
memory. Consider using PView to detect and remove it.
|
|
13) |
PRB: error '800a01b6' Object
doesn't support this property or method
This problem occurs with the 1.x versions of asp.dll. Among the
versions 1.x, only the version 1.0b is valid.
|
|
14) |
PRB: Cannot register ActiveX dll (aspSmartUploadUtil)
The aspSmartUploadUtil.dll musn't be registered with regSVR32.
This dll only has to be in a directory in the system PATH.
|
|
15) |
PRB: aspSmartUpload.File error
'80040460'. Unable to save file (Error 120)
This error may be returned by the component when it can't save a
file. It often comes from the NT permissions on the directory.
Check, and modify if needed, the security permissions on the
directories in which you want the files to be uploaded.
|
|
16) |
PRB: Internet Explorer 5 seems to
not stop when downloading a file.
While downloading a file, the cursor of the mouse remains
"busy". This problem can be fixed by the ContentDispostion
property of aspSmartUpload. This property allows you to
customize the AddHeader section of the MIME type.
|
|
17) |
PRB: Download a file larger than
300Ko '8007000e'
This problem is caused by a bug in ADO 1.5 described in the
Microsoft Knowledge Base article Q182423.
|
|
18) |
FAQ: Does aspSmartUpload support
the MacBinary header ?
aspSmartUpload automatically detecte files with MacBinary
headers. Then it automatically stores the files in a "standard"
format understood by all the browsers.
|
|
19) |
PRB: The upload causes 100 Percent
CPU utilization.
When you try to upload a large file to an IIS computer from a
browser, the CPU utilization on the IIS computer will go to 100
percent.
This problem is referenced by Microsoft at the article Q218880
of the KB BackOffice.
Install the Service Pack 6 to fix this problem.
|
|
20) |
PRB : IE4 systematically opens
files instead of displaying the download popup
IE4 systematically opens the files whose MIME type is known,
even if you want them to be downloaded (i.e. by using the
downloadFile function).
Solution : To download the file you have to right click on the
link, and select the 'save as' menu or ppgrade to Internet
Explorer 5.
|
|
21) |
PRB : Internet Explorer 5 seems to
not stop when downloading
Solution : This problem can be fixed by the ContentDispostion
property of aspSmartUpload.
MyUpLoad.ContentDisposition = "inline;"
|
|
22) |
PRB : The File Download dialog will
show up twice
The File Download dialog will show up twice when choosing 'Open
this file' and clicking 'Ok'.
Solution : This problem can be fixed by the ContentDispostion
property of aspSmartUpload.
MyUpLoad.ContentDisposition = "inline;"
|
|
23) |
PRB : Open or save a HTML file
instead of the doawnloaded file.
A Web server that uses the Content-disposition: attachment HTTP
header to force a file download should prompt the user to open
or save the file; however, in Internet Explorer 5.5 Service Pack
1 (SP1), the user is prompted to open or save the HTML file
instead.
|
|
24) |
PRB : Large file (>4MB) cannot be
download under IIS 6.0
Downloading files with aspSmartUpload and IIS 6 generates the
following error message : "File not found (Error 1040) Error
opening 'Z:\xxx.xxx'. Error 32 The process cannot access the
file because it is being used by another process."
In fact, the original error raised by IIS is "Response Buffer
Limit Exceeded".
Using IIS 6: If you get the above error when you click on an
attachment, the attachment is larger than IIS is configured to
allow. Change the AspBufferingLimit setting in Metabase.xml to a
larger size. The default value is 4194304, which is about 4 MB.
Change this to whatever limit is reasonable for the types of
files your users will be attaching.
This change does not require
stopping IIS, but to make the Metabase.xml file write-able, you
need to go to the IIS control panel, right click the server,
select properties, and check off the box that says "allow
changes to MetaBase configuration while IIS is running". |
|
| |
|
