BPC RiskManager V6 on 64 bit Windows

From RiskWiki

Jump to: navigation, search

Contents

Introduction

BPC RiskManager is a 32 bit application, but it will work just fine on 64 bit Windows. In most scenarios (particularly W2008 and above and Windows 7), the supplied BPC Riskamanger auto installer will correctly install the RiskManager system on a 64bit computer with no manual intervention. The optional SurveyManager library will require some manual steps in IIS and you should consider the notes lower down this page concerning that. If you are installing the W2003 64bit you may have to do some manual steps.


If you wish to pursue this solution on Windows 2003 for 64 bit or Windows 2008 for 64 bit you will need to do the following things:


  • Install on the application server machine the 32bit ADO drivers for the target database (eg the MDAC 2.8 driver set. The RiskManager Installer will automatically cheeck for these and install them for you, so you can just run the installer for this step if you wish. For standard MS databases these should already be present, but you may need to download the appropriate 32 bit MDAC driver set from Microsoft. (A 64bit DB server will still require a 32bit driver for BPC RM to connect to it, but these should already be present.).
  • Install BPC RiskManager as you would on a 32 bit operating system accepting the defaults. The installer will automatically put the 32but components in the x86 directory as required.
  • Run the 32bit SocketServer, BPC RiskManager, BPC RiskManager DataServer and BPC RiskMailManager in 32 bit compatible mode i.e. using WOW (Windows-32 bit on Windows-64 bit) on your server. The auto installer will automatically do this for you, so you should not need to do anything unless you are doing a manual install (ie. copying and pasting the components).
  • Move the 32 bit Midas.dll into the 32 bit system directory and register it manually. Again the installer will do this automatically and you should not have to do anything unless you are doing a manual install.
  • Enable IIS to run 32 bit ISAPI dll's (if using the web components like surveymanager). This, you will have to do even if using the installer.
  • Move the 32 bit ISAPI libraries into the 32 bit ISAPI directory. This you may have to do even if using the installer.


If you are installing on Windows 2008 or above, Windows 7 or above the 32 bit and 64 bit MDAC drivers should already be present, or if you are using the installer they should be installed automatically by the installer.


So, the simple solution to setting up RiskManager on 64Bit windows? - Just run the RiskManager Installer and let it do all the work.


Setting Up the Database drivers on WOW64

If you are using the insatller to install Riskanager, the installer will check for the MDAC (ADO) drivers and install the correct ones if missing.


There are multiple scenarios that you could be facing - all have essentially the same solution:

  1. . Locally installed 64 bit database server : You will need the appropriate 32 bit drivers. These have probably been installed with your database installation, but you may have to download the appropriate 32bit MDAC from Microsoft and install. MDAC 2.8+ will be ok.
  2. . Externally installed database server on 64 bit OS : You will need the appropriate 32 bit drivers. You may have to download the appropriate 32bit MDAC from Microsoft and install. MDAC 2.8+ will be ok.
  3. . Externally installed database server on 32 bit OS : You will need the appropriate 32 bit drivers. You may have to download the appropriate 32bit MDAC from Microsoft and install. MDAC 2.8+ will be ok.


In other words, the key "gotcha" in setting up the 64 bit OS version is making sure you have the 32 bit drivers loaded and registered appropriately. Most of the time you will already have the ADO drivers avaiable, or the RiskManager installer will have installed them for you, and you need do nothing in this step. If, however, you install and can not connect from the app server to the database, or if the installer fails to make databases when instructed, you probably have something wrong with your ADO drivers. In the early releases of 64bit OS's the existance of the 32Bit MDAC drivers were a particular issue. From Windows 2008 this does not seem to have been a problem any longer.


The second most common event we have noted is that if you are using SQLExpress and, depending on the options you chose, when you installed SQLServer your SQL Instance may be the default instance (ie. no instance name) OR SQLEXPRESS. If you can't connect check this first, then look to see if the 32 bit drivers are present.


Enable the application components to use WOW64

Windows-32 on Windows-64 (WoW64) is already part of you Windows 64 bit OS. All you have to do to use it is to enable the 32 bit applications to run in that mode. If you are running the RiskManager installer, it will do all these steps automatically for you.


  • Install on the application server machine the 32bit ADO drivers for the target database (eg the MDAC 2.8 driver set. For standard MS databases these should already be present, but you may need to download the appropriate 32 bit MDAC driver set from Microsoft. (A 64bit DB server will still require a 32bit driver for BPC RM to connect to it).
  • Install the RiskManager application normally (see the instructions for installing BPC RiskManager)
  • Run the application server components and socketserver component in W2003/W2008 32 bit compatible mode:
    • Right clicking on the icons after installation and selecting properties.
    • From the properties screen set the executable compatibility mode to be “Windows 2003 sp1”.
    • Open a command prompt and navigate to the "Program Files\common files\borlan\socketserver" directory and type "socketserver.exe -install" to install the socket server as a service after enabling it to run in 32 bit compatible mode.


Register the 32 bit Midas.dll on the application server

If you are running the RiskManager installer you will not have to do anything here.


If you are installing manually (ie. copying and pasting the files), you must register the Midas.dll manually by performing the following steps to enable 32 bit MIDAS.DLL to run on 64-bit Windows:

1. Copy the midas.dll from the system32 directory (if present) or the system files
   directory of the BPC RiskManager install directory to:
   %systemdrive%\windows\SysWOW64\

2. Open a command prompt and navigate to the %systemdrive%\windows\SysWOW64 directory.

3. Type the following command:
   Regsvr32 midas.dll

4. Press ENTER.


Enable the IIS server to run 32 bit ISAPI dlls

Depending on your version of IIS you will need to do different things. The primary issue is to make sure that IIS sees the components as 32bit apps.


Enable the IIS server to run 32 bit ISAPI dlls by perfoming the following steps:

  • To enable IIS 6.0+ to run 32-bit applications on 64-bit Windows
1. Open a command prompt and navigate to the 
   %systemdrive%\Inetpub\AdminScripts directory.

2. Type the following command:
   cscript.exe adsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 “true”

3. Press ENTER.

  • Copy the surveymanager dll’s generated during configuration to the IIS server to run 32 bit ISAPI dlls to the special 32 bit ISAPI directory:
%windir%\system32\inetsrv.




BackLinks




CopyRight Bishop Phillips Consulting Pty Ltd 1997-2012 ( BPC RiskManager V6 on 64 bit Windows )
Personal tools