Back to the top of the FAQ

The installation program, InstallShield, is a 16 bit application, and as yet, Microsoft does not support 16 bit software on its 64 bit machines.

KB960267 - Does not appear to be necessary on Server 2008 x64. This is good because it does not install!

Newsflash Oct/2015 Windows Server 2008 32 bit is available:
See MS instructions

Manual Installation for 64 bit Windows.

First, see here.

Daniel of WEP mentions
"You don't need to enable IIS7 to run 32bit ISAPI filters like AuthentiX using the steps for II6, but you will need to set Enable 32-bit Applications = True in Advanced settings for the App Pool for your particular site. So you cannot use Authentix to secure a 64-bit app, but IIS7 can run 32 bit and 64 bit app-pools simultaneously I believe."
Thanks Daniel!

Andy of Stella says:
If you ever get someone with an Amazon AWS instance and your software, I took notes... registering the DLL's inside the C:\WINDOWS\SysWoW64 folder, and then creating the ISAPI inside IIS7 were the two main steps I needed to do.
Thanks Andy!
Install AuthentiX on a 32bit Windows computer.

On the 64 bit computer, create the installation directory, eg c:\flicks\authx.

Copy all files and subdirectories from the original AuthentiX installation directory to the new directory.

Copy the files authxdb.dll and axodbc.dll in the system32 directory to the new C:\WINDOWS\syswow64 directory. You may need Administrator permissions for this.

Make sure the OS allows 32 bit application to run (I am a bit hazy on how to do this, if you have details, please let me know).

Open a command line window and go to the new installation directory.
You may need Administrator permissions for this, otherwise you may get an 0x80040200 error.
Then register the OCX files authxocx.ocx and AXSupport.ocx using regsvr32.

On the 32bit machine, use regedt32 and go to
/Flicks Software

right click, and Export this to a .reg file. Move the reg file to the new computer, and import to the same location.

You will likely need to place it in the node starting at:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Flicks Software\AuthentiX\1.0\AuthentiXConfig
You can use notepad or wordpad on the .reg file to change
[HKEY_LOCAL_MACHINE\SOFTWARE\Flicks Software\AuthentiX\1.0\AuthentixConfig]
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Flicks Software\AuthentiX\1.0\AuthentiXConfig]

Regsvr32 flicksiisinstall.dll
in the installation directory.

Run Internet Services Manager (Start-AdminTools-IIS). Open the machine name, right click on Websites - Properties, ISAPI Filters tab and add AuthXflt.dll in the installation directory.

Double check your serial number and registration code by pressing Alt-P in the About Box.

Restart IIS.

To enable IIS6 to run 32bit ISAPI filters like AuthentiX, see here: 32Bit ISAPI Filters.
If this doesn't work, see here: Setting up IIS.
Metabase editing.

If you are able to run and test an automated installer for the above steps, please let me know.

Merrick's approach:.

I've reverted IIS back to 32 bit operation and AuthentiX is now working again.

Following are the procedures I did in order to get it functional to the current point:

  • Set to run in 32-bit mode.
    Open CMD window and navigate to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
    Run aspnet_regiis.exe -i
    This will install the 32bit edition of 2 (will work with ASP.1 as well and I haven’t tested with .3 yet)
  • Set IIS to run in 32-bit mode.
    Run cscript c:\inetpub\adminscripts\adsutil.vbs SET /w3svc/AppPools/Enable32BitAppOnWin64 true
    (Setting up extra scripts)
    This sets IIS to run in 32-bit mode.

    Or use IIS Manager to set the Application Pool Defaults to Enable 32-bit Applications,
    like so

  • Unpack the AuthentiX files into C:\Program Files (x86)\Flicks Software\Authentix.
    However, if you are going to use the .adb database file then don't install in Program Files (x86) because it won't be able to read/write the file.
    Use something like c:\flicks\authentix
  • Copy the axodbc.dll and authxdb.dll to the C:\WINDOWS\SysWOW64 directory. You may need Administrator permissions for this.
  • Open a command line window. You may need Administrator permissions for this, otherwise you may get an 0x80040200 error. Register the authxocx.ocx, AXSupport.ocx and FlicksIISInstall.dll in C:\Program Files (x86)\Flicks Software\Authentix. 0x80040200
  • Add AuthentiX to IIS's Web Service Extension library and set to allow
  • Add the ISAPI filter to the Web Site Properties making sure to name it "Membership Protection Software" (I'm not sure if this is critical or not but I couldn't get it to work until I found this buried in the Flicks FAQ section)
  • Import the following registry key.

    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Flicks Software]
    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Flicks Software\AuthentiX]
    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Flicks Software\AuthentiX\1.0]
    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Flicks Software\AuthentiX\1.0\AuthentixConfig]
    "Path"="C:\\Program Files (x86)\\Flicks Software\\AuthentiX\\"
    "Name"="Butch Fleischer"
    "Company"="Merrick Towle"
    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Flicks Software\AuthentiX\1.0\Security]
    "Permitted Alternate Methods"=hex(7):4e,00,54,00,4c,00,4d,00,00,00,00,00
    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Flicks Software\AuthentiX\1.0\Settings]
    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Flicks Software\AuthentiX_ISP]
    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Flicks Software\AuthentiX_ISP\1.0]
    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Flicks Software
    <END KEY>

  • Restart IIS and better yet, reboot the server if possible.

I just get:
'The AuthentiX Filter is not installed'
shown on the GUI when I run WebQuota

Also, when I click About I get the following:
Error: invalid IP address
Make sure you use a Static IP address and not DCHP!
The version of WebQuota is 7.01c and supports IIS 7.
Any ideas what the problem may be? The server is new and a clean install?
Best Regards

Reply to Mike
Could you try protecting a directory as usual, and see if AuthentiX is actually working.
Often the error messages themselves are the error, because IIS8 has moved the registry locations AuthentiX is looking for, to somewhere else.

Hi Kevin
It works!

Back to the top of the FAQ