Installing ProClarity Analytics Server on 64-bit Windows Server 2003

There are some considerations that need to be taken into account when installing ProClarity Analytics Server on 64-bit Windows Server 2003. The most important factor to consider in your deployment is that PAS is a 32-bit web application. In order to run PAS on 64-bit Windows, it will be necessary to run IIS in 32-bit mode. IIS will not run both 32-bit and 64-bit applications simultaneously, so if you were planning on running 64-bit Reporting Services on this machine, you may want to find a 32-bit server to install PAS on. The 6.3 ProClarity Analytics Server install will switch IIS to run in 32-bit mode, and should warn you before it does so. What follows is a list of steps that we recommend for installing PAS in a 64-bit environment, should you choose to do so:

1. Log in with the local administrator account. It is imperative that the logged in credentials be that of the local administrator, not a domain account that is a member of the local administrators group, but the local admin account for the server.

2. Install PAS. You should be able to run through the PAS install without experiencing any issues.

3. Stop the IIS service. Access the Services snap in via Administrative Tools, stop the “IIS Admin Service”.

4. Navigate to PInitx64.bat and run it. This batch file is located at \Inetpub\wwwroot\PAS\x64Extra\ by default.

5. Reboot the server.

6. Log back in with the local administrator account. Again, a domain account belonging to the local administrators group will not work. Logging in with the local admin account is the only way that the ProClarity com objects will be created.

After following these steps, verify that the ProClarity Admin Tool can be accessed using the local administrator account credentials, at which time you can add domain accounts to the ProClarity Administrator role.

Also, verify that the PAS website can be accessed by opening a browser and navigating to http://<machinename>/PAS. If the page renders correctly, you know that the install was successful.

If, however, you are unable to perform the installation by logging in as the machine's local Administrator you may also try adding the domain admin performing the install to the IIS_WPG Group (IIS 6).

Another option is to give explicit rights in the IIS metabase for the domain admin performing the installation. Run the below script:

c:\Inetpub\Adminscripts>cscript metaacl.vbs IIS://LOCALHOST/W3SVC mydomain\mydomainaccount RWSEUD

The only requirement is RWUE, however if the first suggestion does not solve the problem you will need to add RWSUED rights.

R - Read
W - Write
S - Restricted Write
U - Unsecure Properties Read
E - Enumerate Keys
D - Write DACL (permissions)