IIS - Enable 32-bit ODBC Driver to work on Windows 2008 R2

IIS - Enable 32-bit ODBC Driver to work on Windows 2008 R2 

References:

• http://forums.iis.net/t/1149768.aspx
• http://forums.devarticles.com/microsoft-sql-server-5/data-source-name-not-found-and-no-default-driver-specified-8346.html
• http://stackoverflow.com/questions/13811179/where-how-can-i-download-and-install-the-microsoft-jet-oledb-4-0-for-windows-8

Requirements:

• Download Microsoft Access Database Engine 2010 (32-bit)
• http://www.microsoft.com/en-us/download/details.aspx?id=13255

PROCEDURE:

1. Copy the Folder to new site on the new server. 
2. In an Windows Server 2008 R2 Environment there are two ODBC control versions a 64-bit and a 32-bit. The default Data Sources (ODBC) launches the 64-bit version. The website is a 32-bit application.
3. After moving the folder create a 32-bit ODBC link by going to 
a. 32-bit ODBC = C:\Windows\SysWOW64\odbcad32.exe
b. 64-bit ODBC = %windir%\system32\odbcad32.exe
Note: Don’t be mislead by the hitchhikers guide to the galaxy “32”.
4.  Download and install the Microsoft Access database engine 2010 (English) 32-bit version. 
Note: It is not possible to have the 32-bit and the 64-bit version of the Microsoft Access Database engine installed.
a. After installing the Microsoft Access database engine 2010 create an ODBC System DSN to the database.
b. Click Add and select the Microsoft Access Driver (*.mdb, *.accdb) Point the System DSN to the appropriate database. 
5. Test the ODBC 32-bit Connection 
a. Start the 32 bits UDL wizard by going to the run box and typing in the following command: C:\Windows\syswow64\rundll32.exe "C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll",OpenDSLFile C:\path\to\your.udl.

b. Select the data source name "somesorce) (can alternatively use the connection string “dsn=somesource;” which is what the asp code uses.

Enable 32-bit for the Application Pool

a.     Click Application Pools on the upper left hand side.

b.   a.     Under Advanced Settings change the second column Enable 32-bit Applications from False to True.

                                  i.    Enable 32-bit Applications = True

                                 ii.    Managed Pipeline Mode = Classic

a.     If WSUS is running on the same server that is hosting the 32-bit IIS website, you will need to uninstall the WSUS compression stream. Disabling the WSUS compression stream will not break WSUS, but will slow it down as its responses will not be compressed. It might be best to run WSUS on a separate server so as not to conflict with anything else.

                                  i.    Compression schemes are registered globally - to get rid of the scheme altogether, run the following command as an administrator…

                                 ii.    Disable the WSUS compression stream :

%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']

a.     To view the current streams on the IIS server run the following commands…

%windir%\system32\inetsrv\appcmd.exe list config -section:system.webServer/httpCompression

dir %windir%\syswow64\inetsrv\gzip.dll

Note: If you ever want to Enable the compression stream again run the following command:

%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /+[name='xpress',doStaticCompression='false',dll='%windir%\system32\inetsrv\suscomp.dll']\

1.     Lastly ensure permissions are setup accordingly on the folder.

a.     IIS_USRS = read & execute, List folder contents, Read

b.    USERS = read & execute, List folder contents, Read

c.     DOMAIN USERS = Modify, Read & execute, List folder contents, Read, Write

d.    ASP.NET = Read & execute, List folder contents, Read

e.     IUSR = Read & execute, List folder contents, Read

1.     Ensure registry permissions are set accordingly for the 32-bit ODBC.INI file.( http://support.microsoft.com/kb/306345)

a.     Do this for both 64-bit and WOWSYS key