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
KB960267 - Does not appear to be necessary on Server 2008 x64.
This is good because it does not install!
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."
Install AuthentiX on a 32bit Windows computer.
On the 64 bit computer, create the installation directory.
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 syswow64 directory
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,
then register the OCX files authxocx.ocx and AXSupport.ocx using regsvr32.
On the 32bit machine, use regedt32 and go to
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:
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.
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.
If you are able to run and test an automated installer for the above steps, please let me know.
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 ASP.net 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 ASP.net 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
This sets IIS to run in 32-bit mode.
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
Register the authxocx.ocx, AXSupport.ocx and FlicksIISInstall.dll in C:\Program Files (x86)\Flicks Software\Authentix
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
"Path"="C:\\Program Files (x86)\\Flicks Software\\AuthentiX\\"
"Permitted Alternate Methods"=hex(7):4e,00,54,00,4c,00,4d,00,00,00,00,00
Restart IIS and better yet, reboot the server if possible.
It is unlikely we will be investing in a 64bit machine ourselves solely for this purpose.
I had an expensive and fruitless experience with the Dec Alpha platform a while ago
Back to the top of the FAQ