Our server uses the .NET framework v2.0.50727 to operate. You must be sure to set the proper permissions on your server in order for our component to work properly. Be sure that your website is either in an isolated Application Pool, or in an Application Pool with other .NET 2.0 websites. IIS will not run multiple versions of .NET in the same Application Pool. If you are running Windows 2000, set your website to work in Isolation Mode (HIGH). Finally, be sure to check the ASP.NET tab of your website in IIS to be sure that the version is set to v2.0.50727.

This is a known .NET issue involving .NET COM interop class libraries and a windows update. Try giving the IUSR (or whoever your site is running as) read access to HKEY_USERS\S-1-5-20\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones. This key might change depending on who your app pool is running as (default is Network Service [aka S-1-5-20]).

In every installation beginning with version 1.5.7b, we include a non-.NET version of the DLL. It is installed automatically when you install the component and can be accessed by changing the CREATEOBJECT reference from "sqlinjectionblocker.blocker" to "sqlinjectionblockerclassic.blocker" in the implementation code found within the component documentation. We have found that using that DLL is necessary for servers that have not been properly configured to run .NET for various reasons including permission issues, application isolation limitations, and just time to invest in solving those issues.