Support Center > Search Results > SecureKnowledge Details
WebRH 3.0.x install fails on Windows Server 2008 R2 to SQL 2008 Technical Level
Symptoms
  • On a Windows 2008 R2 Server connected to a Windows 2008 R2 server running SQL Server 2008 installation of WebRH 3.0.1 or 3.0.2 fails if you try to install using Windows Authentication for connection to the SQL Server. We have found that WebRH will install correctly if using a properly configured SQL authentication account durring the installation.
Cause

WebRH installation appears to be occurring under Local System account and is not properly impersonating the logged in user when authenticating to SQL. The authentication to SQL occurs under   <domain>\<machine$>  rather than <domain>\<user>. This causes authentication failure within SQL and subsequent failure to create the WebRH database.


Solution

We have found that WebRH will install correctly if using a properly configured SQL authentication account during the installation.

1. Install IIS with ASP.Net, ISAPI extonsion, ASP and IIS6 metabase compatibility.

2. Configure SQL Server in Mixed Mode (Windows and SQL authentication)

3. Create a SQL auth account and assign it dbcreator rights by use SQL Server management studio.

4. Install WebRH using the SQL auth account you created when prompted for SQL server authentication.

5. Install desired modules (FDE/Media Encryption)

6. Log into the WebRH website

7. Use the WebRH Config tool in the 9_Tools directory of the installation package to set the WebRH database connection string to Windows Authentication.

The above steps should complete a successful WebRH installation.

If you run into any issues with creating the database
Verify that the SQL server is properly configured for mixed mode authentication
Verify that the SQL auth account created can authenticate
Verify that the SQL auth account created has dbcreator rights

If you run into any issues loading the website:
Verify that the WebRH component services is running
Verify the IIS Application pools are running

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

Give us Feedback
Please rate this document
[1=Worst,5=Best]
Comment