You are migrating a classic ASP application to a new server and your upload or download pages fail to instantiate the FileUp object with the error "ActiveX component can't create object"

There are usually three possible reasons why the FileUp object cannot be instantiated:

1. The server is a 64-bit OS and you are not running your FileUp application in a 32-bit application pool
2. The dll (safileup.dll) was not properly registered
3. The dll does not have read and execute permissions for the account the app pool is running under

Most common cause - 64 bit process trying to run a 32-bit dll

If the new server is 64-bit, the 1st option above is the most likely cause. Since FileUp is a 32-bit component, it cannot be instantiated from a 64-bit process. The solution is to create an app pool with "Enable 32-Bit Applications" set to "True." If you are also using FileUp in ASP.NET applications, you should also set the Managed Pipeline Mode of the app pool to "Classic".

For more information, see How to run fileUp on a 64-bit Windows Operating System

Other causes - dll not registered or has incorrect permissions

If you determine the issue is not caused by trying to run a 32-bit dll in a 64-bit process, the next step is to find safileup.dll and make sure it is registered and has correct permissions.

• One quick way to determine whether the dll is registered, and if so where it is located, is to use our Whatdll utility. See this KB article: How-To: Determine the location of the registered COM DLL. Download the whatdll.vbs script, run it in a 32-bit command prompt and enter:
  

   whatdll softartisans.fileup

• If you get an error "Cannot open registry for specified ProgID," that means the dll is not registered. Find the dll and manually register it. (Note: If you ran our automated installer it should be in "Program Files (x86)\SoftArtisans\FileUp\com"). In the command prompt, navigate to the directory containing the dll and enter:
  

  regsvr32 safileup.dll

  If your application is using any of the other components bundled with FileUp, register those as well. See the installation instructions in the documentation for more information about the dlls included with FileUp.
• If you have confirmed that the dll is registered and the problem still occurs, make sure the dll has NTFS read and execute permissions for the account your application pool is running under.