Web Tools and Component: File Upload, Flash Chart, Flash Stars Rating, Flash Calendar

  JobdaoUpload File Upload component - User Manual

System Requirements | Install | Reference | FAQs

System Requirements

Install

-Manual Installation
To install JobdaoUpload the first time, run the automatic installation. Once InstallShield has unpacked the dll files that contain JobdaoUpload, you can re-install JobdaoUpload manually (if, for example, you are moving JobdaoUpload to a different server):

Open a command prompt window and move to the directory JobdaoUpload.
For example, enter cd Program Files\Jobdao\JobdaoUpload.

Enter regsvr32 JobdaoUpload.dll. A dialog box will inform you that JobdaoUpload.dll registered successfully; click Ok.

Enter iisreset to reset IIS.

-Automatic Removal
If JobdaoUpload was installed with the automatic installer, use Add/Remove Programs to unregister and remove JobdaoUpload and all of its associated documentation and samples:

From the Start menu, select Settings -> Control Panel.
Double-click Add/Remove Programs.
Select Jobdao JobdaoUpload.
Click the Change/Remove button to remove the old copy of JobdaoUpload.

-Manual Removal

To manually remove JobdaoUpload:

Unregister the dll Files in JobdaoUpload
Open a DOS prompt window.

Go to JobdaoUpload COM directory.

Enter regsvr32 JobdaoUpload.dll /u and click Ok.

To reset IIS, enter iisreset.

-ASP Security Settings
In ASP, JobdaoUpload executes in a specific user context:

IUSR_MACHINENAME (The default anonymous user account)   OR  An authenticated user account

To allow uploads, the IUSR_MACHINENAME or authenticated user must have Read, Write, and Modify NTFS permissions for JobdaoUpload 's temporary and destination folders. An upload's destination folder is set in code by DestinationDirectory, DestinationPath, or SaveAs. The temporary directory for an upload can be set in code by the property TempStorageLocation. If you do not assign a value to TempStorageLocation, uploads will be cached in the system's default directory for cached files, which is determined by the system environment variable TEMP.

Reference

You can get more detail for programmer reference by clicking the object link below.

Why wait? Put JobdaoUpload to work now! Upload a few files to our server using the demo applications.
Just click here you can view the live demo and its sample source code.

FAQs

-Why aren't I getting any files uploaded?
First check the obvious things - your form must be enctype="multipart/form-data". Your file input field must have a name. Check you're submitting to the correct page. Finally try saving a dump of your upload (details in the documentation) and looking at it in Notepad - you will probably be able to see what's going wrong.

-How can I allow users to select multiple files into one file upload box?
Unfortunately it is impossible to do this kind of multi-selection upload unless you use client side code (eg Java Applet, ActiveX).

Many people on the internet cannot use this kind of code (eg Java Applet, ActiveX).. For example people in large companies often cannot use this kind of code because IT departments tend to disable client side code for security reasons.

An additional benefit of using pure server-side code is that you get security for free. You can do your uploads using an HTTPS link and both you and your clients can be certain that their data transfer is secure.

-Why does JobdaoUpload tell me 'Access is denied. - (0x00000005)' when I try and save a file?
For safety JobdaoUpload will not, by default, overwrite existing files. If you try to do so you will receive an access denied error. If you wish to overwrite files you should set the JobdaoUpload Overwrite property to true in your script.

file.saveas filename,true

Less commonly it may be that the IUSR internet user does not have sufficient permissions to write to the location you have specified. In this case you should alter the permissions on the write destination to allow access.

-Why does JobdaoUpload keep telling me that the 'Upload stopped unexpectedly.'?
The most likely cause of this is that there's a reference to the built in form object somewhere in your code. If the form object is referenced it grabs all the uploaded data which means that JobdaoUpload can't get it. This sometimes occurs when an include file is changed so that it references the form object.

If the error occurs during a large upload the cause is typically that the client has clicked on stop on their browser window or that they've dismissed the browser window or that there's been a network problem which has broken the connection. If the error occurs immediately on form submission you should look at the following explanation.

JobdaoUpload reports an error at the point it needs to obtain data. Typically the point at which it first has to gather the data is when you reference a field or you ask for information (such as the field count) that can only be derived from the upload data. The essential cause is that IIS isn't providing this data.

You can completely remove JobdaoUpload from this equation and you should find that the problem remains. Comment out your form upload code and try inserting something like:

theLen = Request.TotalBytes
theData = Request.BinaryRead(theLen)
Response.Write "Upload Size = " & theLen
Response.Write "Data Size = " & UBound(theData)

You should find that either the upload size or the data size is substantially wrong (they should both be appx equal to the size of your uploaded files) or that an error gets thrown.

-When uploading very large files I keep getting 'Upload stopped unexpectedly.'.
Our standard tests run up to about 100 MB. We've had clients uploading files of over 500 MB. However with files this big you can run into unusual problems so here are some points to check.

Make sure you've got enough disk space to save your files. Check the SessionTimeout and ScriptTimeout properties as mentioned in the 'Script Settings' portion of the documentation.

Ongoing uploads are stored on disk in the temp folder (you can change this location if you want). This means that your system drive has to have enough space. If you have five simultaneous 100 MB uploads you'll need minimum 500 MB free disk space.

If you have file system quotas then check the file system quota for the IIS user.

Your client browser has to have disk space free. Some browsers save the encoded form on the system disk before sending it through to the web server. This cache can be as much as twice as large as the uploaded files. If your client does not have sufficient space free the results can be unpredictable.

There is a theoretical limit to the number of large uploads available. Because you're working in a 2 GB address space the total upload size (for all ongoing uploads) must not exceed this value. Of course some other things will take up space as well so the total will probably be somewhat less than 2 GB. This is a limit that is only likely to come into play for large numbers of very large uploads.

If this doesn't help please mail us with an exact description of the problem and the system on which you're running. Also check the Application Event Log.
 

-IIS 6.0: upload issues
If any of you are having issues with uploads and downloads with file sizes greater than 200K and are running IIS 6.0, try these solutions first: open up the file "metabase.xml" with notepad...should be located in C:\windows\sytem32\inetserv. Find the variable named "AspMaxRequestEntityAllowed", it's set at 204800 (200K) and change it to the desired size. And there you have it. For downloading Find the variable named "AspBufferingLimit" and change it to something greater than what is there. By default this is set to around 4 megs. By changing this variable you are increasing the max size of ASP response buffer, thus letting you download files greater than 4 megs. By increasing the number of these variables, you can controll the size of uploads and downloads (respectively).

A NOTE: Before making changes to this file. You must first go to IIS and right click the server and select properties. Check the box that says allow changes to MetaBase configuration while IIS is running. If you don't you will find that the metabase.xml file is locked. For good house cleaning you should go back and uncheck this after making your changes.
 

-My upload just hangs. What gives?
Under some circumstances if you have an ASP with more than 32k of static HTML and you locate your JobdaoUpload script after the 32nd kilobyte of data then the upload can hang. We suspect that this is because IIS starts the HTTP response before the client has finished the request and this can confuse browsers.

-My NT 4 web server occasionally hangs during large uploads.
See the Microsoft article "ASP Request.BinaryRead Method Causes 100 Percent CPU Utilization". Please note that all upload components use this method to obtain files (even if it is hidden from you) so all are vulnerable to this NT 4 bug.