Pricing/Purchase Info
Learn ASP Express
Tech Support
Bug Report

Peace - Now and Forever
ASP Express
The WEB Professional's Choice
Here's what I recommend first of all, before installation:
  1. If you have a current version of ASP Express installed
    • Backup the files in the ASP Directory to keep your .mdb file (Code Librarian snippets) and your .aop file (FTP Profiles)
    • Run uninstall program
    • Make sure ASP Express directory is fully deleted
  2. Delete all .tmp files from the Windows (or WinNt) directory
  3. Delete all files from your Windows\Temp Directory (or TEMP for WinNt, or Documents and Settings/Yourusername/Localsettings/Temp directory for Win2k).
  4. If you have Norton Utilities - run WinDoctor or chkdsk /f on your Hard Drive, to make sure it's in the best shape....
  5. Get latest updates from Microsoft for your operating system
  6. Temporarily turn off your virus protection while doing any Windows Installation
  7. If you want to get the great direct-access SQL Server benefits of ASP Experss, you must have either SQL Server, SQL Server Tools, or SQLDMO installed. If you have none of these, make sure you check out this FAQ on how to get SQLDMO installed.

Be sure to check out our 'HOW-TO' page
for How-To-Do everal commonly used ASP tasks, using ASP Express


  1. Setup cannot continue because some system files are out of date on your system. -- then, after Windows restarts and you begin the installation again, the error message appears again
  2. When using the ADO Assistant, and then the SQL Assistant with an Access Database, I get the error Number 3265 - Item Not found in this Collection
  3. Error 68 - Device Unavailable
  4. Norton Anti-Virus Malicious Script Error
  5. Dialog boxes or Installer screen cropped too small to work with
  6. Activex Object Can't create component


Setup cannot continue because some system files are out of date on your system.
There are a number of reasons why this can happen, but the two most common are as follows:

  • The .tmp files are being deleted.

  • The Temp folder is on a different drive or partition from the operating system. By default, the operating system is installed to either the Windows or Winnt folder.

The following are resolutions to this problem:
  1. Copy the TEMP and TMP environment variables to a folder that is in the same drive partition as the Windows system files. To do this, open a command prompt window and type the following at the prompt:
    Set TMP=C:\TEMP
    Set TEMP=C:\TEMP
    This will save the TEMP and TMP environment variables to a folder named "Temp" that resides on the C: drive.

    NOTE: The folder must exist prior to carrying out these steps.

    Once these environment variables are set, the application should then install and continue past the message on reboot.

  2. If your Autoexec.bat file contains the following line (or similar):
    If exists c:\temp\*.tmp del c:\temp\*.tmp
    comment it out by placing "REM" in front of it.

  3. Disable any Anti-virus software (or other memory resident programs) and try running Setup again. Often the best way to accomplish this is to run setup in Safe Mode. It may also be necessary to copy all of the setup files to a temporary folder on the hard drive disk and run Setup.exe from there.

  4. Leftover files from a failed Setup attempt can also cause this problem. If found, delete the msftqws.pdw subfolder and its contents from the Temp folder. Also look in the Windows or Winnt folder for Setup1.exe and any *.CAB files from previous installs, and delete them. This should be done after each failed install.

  5. Some logon scripts can cause this problem, so try to run Setup before logging on to the network.

When using the ADO Assistant, and then the SQL Assistant with an Access Database, I get the error Number 3265 - Item Not found in this Collection
When using an Access Database, you must have a Primary Key in the table. Merely go in and create a primary key in the table you are creating the ASP document for.
Error 68 - Device Unavailable
Check your preferences - make sure your default directory is accessible/online and designated in preferences.
Norton Anti-Virus Malicious Script Error
ASP Express is writing a temp file to the hard disk - then, when closing the application, it's using the FilesystemObject to delete the files.....Norton SystemWorks incorrectly sees that as a malicious script. If you go into Options/Script Blocking - then un-check the box to Enable Script Blocking - that will take care of this problem. Or, just rest assured nothing malicious is happening and check the radio button to prompt you whenever it's happening - then when ASP Express is doing its thing, you can tell Norton's that it's OK.
Dialog boxes or Installer screen cropped too small to work with
Some users who have a Matrox Millennium G400 display adaptor with dual head (spanning the display over two monitors) could possibly experience behavior such as this. Either the Installer Screen will be severely cropped, too small to work with and install the application, or, once installed, the dialog boxes in ASP Express will be cropped and unuseable. To fix this, disable the "Use center popup" and "Save / Restore windows positions" from the adaptor's control panel.
Activex Object Can't create component
Installing SQL DMO for Direct-Access to SQL Server:
If you get this message when you try to add a SQL Server connection to the DataServer window, or when you try to access a SQL Server directly, this means you do not have the necessary infrastructure for the SQL Server tools (SQLDMO) installed anywhere on your computer.
To remedy this, first, you must have MDAC installed on your system with a version of at LEAST 2.6. If you are not sure, you can download a version checker here.

If you don't have a version greater than 2.6, the link for version 2.8 (the current version at the time of this faq), is available for download here.

Next, when, and ONLY when you have made sure your MDAC version is 2.6 or above, you must install the SQLDMO infrastructure. The link for downloading the setup file for this is here.

Instructions and Sequence:
(the order is very important here)

  1. Uninstall ASP Express
  2. If MDAC is not greater than v2.6, install MDAC
  3. Install the SQL DMO Infrastructure setup.exe (dmosetup.exe)
  4. Then - and only then - reinstall ASPExpress

Send your comments, questions or suggestions via E-Mail to : (suggestions@aspexpress.com)