Home     Products      Support      Corporate     Sign In 
Support Knowledge Base, Article 1318
5.0.14 and earlier
FileUp hangs after installing a .NET update
After installing a .NET update, typically .NET 3.5 SP1, instantiating FileUp version 5.0.14 or earlier in classic ASP causes IIS to hang. After IIS hangs like this, no other scripts (either classic ASP or ASP.NET) can run until IIS is reset.
FileUp ships with two sets of dlls, a COM-only set and a mixed-mode set. The mixed-mode set contain both managed and unmanaged code. For convienence, FileUp installers prior to version 5.1.1 registered the mixed-mode dlls so that you would only have to deal with one set of dlls whether you were using COM or .NET.

Proper functioning of the mixed-mode dlls relies on the interop, a Microsoft technology that handles communication between managed and unmanaged code. The .NET 3.5 SP1 update included some breaking changes to the interop, causing our mixed-mode dlls to start hanging when a FileUp object was created in ASP. This error is commonly referred to as a "loader lock" error. Interested readers can find more information about these errors in this MSDN article.

The solution to all this is to register the COM dlls instead of the mixed-mode ones. There are two ways to do this:

  1. Upgrade to the latest version of FileUp with the automatic installer. In versions 5.1.1 and later, FileUp's automatic installer registers the COM dlls instead of the mixed-mode ones. Minor version upgrades are free, so as long as you've purchased a copy of any 5.x version of FileUp, you can upgrade to the latest 5.x version at our product upgrade page. If you don't own version 5, you can contact our sales department to purchase a license. After uninstalling your old version of FileUp and installing the new one, the loader lock problem should go away.
  2. Manually register the COM dlls. To manually register the COM dlls, open a command prompt and navigate to the folder containing your COM dlls. By default, the dlls are installed to C:\Program Files\SoftArtisans\FileUp\com\. Then use the regsvr32 command to register the dlls listed in the manual installation section. After registering the dlls, reset IIS with the iisreset command to ensure that no references to the mixed-mode dlls remain.
Old versions of the FileUp installer (4.x and earlier) did not unpack the COM dlls if .NET was installed on the machine. If you have an old version of FileUp without a COM folder and do not wish to upgrade to the current version of FileUp, there are two ways to get the COM dlls so you can register them:
  1. If you have a machine handy that doesn't have .NET installed, you can run the installer you already have on that machine. In the absence of .NET, the old installer will unpack the COM dlls. Then you can copy those dlls to the target machine and perform a manual installation.
  2. If you don't have a machine available without .NET installed, contact SoftArtisans support. Please include your order number, a short description of the problem and a reference to this article. A technical services representative will contact you shortly with the correct version of the COM dlls. If you don't have your order number, please include as much information as you can about your order, and we'll work with you to verify your purchase.
Created : 9/1/2009 11:12:06 AM (last modified : 9/1/2009 11:12:05 AM)
Rate this article!