Since Free ASP Upload is entirely made of source code, it is very easy to install, not only on your server, but also on the more restrictive environment of a web-hosting account. There are, however, some conditions to be met regarding the scripting environment and the file permissions. If you administer your own server, follow the instructions below to configure your machine correctly. If the upload code is going to be installed in a web-hosting account, it is very likely that the hosting company already performed all of these generic steps; if they didn't, ask for support from the hosting company and refer to these intructions.
To test your ASP environment, simply download the code, copy it to your ASP directory, and run the included example.
Not sure about all these technical details? Simply download the code, copy it to your asp directory, configure the variable 'uploadsDirVar' in the file 'uploadTester.asp', and test it.
Seeing it running is the quickest way to verify the requirements.
Make sure the IIS web server is not restricting the size of ASP uploads. For example: IIS 6 (Windows Server 2003) has a limit of 200 KB for ASP requests in general and file uploads in particular. To remove this limit in IIS there are different instructions depending on your version of IIS.
For IIS 6:
- Go to IIS and right click the server, select properties, and check the box "Allow changes to MetaBase configuration while IIS is running"; if after this step the metabase file is still locked, try turning off IIS or even restarting the machine in safe mode.
- Open in a text editor the Metabase file, which can be found at c:\Windows\System32\Inetsrv\MetaBase.xml.
- The variable AspMaxRequestEntityAllowed limits the number of bytes in the page request (by default 200KB); change the value to 1073741824 (unlimited) or to a limit of your choice.
- Check whether the same variable shows up in other places in the file and change them too.
For IIS 7:
- Highlight your website, then open the "Advanced Settings..." link in the right-most panel. Set "ConnectionTime-out (seconds)" to a much bigger number. For example: "3600", which is an hour. Close "Advanced Settings...".
- While still highlighting your website, click on the "ASP" tab, then expand "Limits Properties" and set "Maximum Requesting Entity Body Limit" to 1073741824.
- Finally, open a command window as an administrator and run the command "c:\windows\system32\inetsrv\appcmd set config -section:requestFiltering -requestLimits.maxAllowedContentLength:100000000". This tells IIS the largest amount you may upload, in this case, it's 100MB. You may set your number accordingly.
Free ASP Upload will receive the uploaded streams and save them in the server as files. For that to work you must have a directory for which write permissions are granted. Your pages can specify what is the directory to use for saving the uploaded files. In many cases this directory is different from the directory where the ASP pages are stored.
The secret for the speed of this source-based upload is the use of streams. Microsoft added the stream object to ADO years ago, so your server is likely to have it. If, for example, your server runs Windows 2000 or later you should have MDAC 2.5 (which includes ADO 2.5) or later.
If, however, you need to update your system, go to Microsoft's FREE Downloads, Universal Data Access.
The upload code is Object Oriented, therefore it will not work with very old versions of VBScript. In the unlikely event that your server is totally out-of-date, after you install the upload code you will see the error "ActiveX component can't create object: 'Scripting.Dictionary'" or the error "Expected end of statement: Public Property Get Form".
To get an updated version of VBScript, download IE 5.5 or later to your server machine. Microsoft hosts a table of other products and the VBSCript versions they include (top of page).