Configuring SQL Report Server 2008 SP1

When configuring a SQL 2008 SP1 reporting server I got this error, “The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel”  when I trying to view the http://servername/Reports url. This appeared a bit odd as I wasn’t trying to connect via SSL to the site.



Luckily the fix here was an easy one, I simply had to alter the “rsreportserver.config” file and make the following change.


<Add Key="SecureConnectionLevel" Value="2"/>


<Add Key="SecureConnectionLevel" Value="0"/>

Which resolved the issue and displayed the page.



There is more detail on this here. This basically means that this will need to be revisited again when it comes time to enable reporting services out to the web via an SSL.

Slipstreaming SQL 2008 Sp1

If you try installing SQL 2008 RTM on either Windows 7, Vista Sp2 or XP Sp3 you will find that install fails. There is a really easy fix for this by simply slipstreaming Sp1 with the RTM image by following these instructions here.

In terms of the actual problem I’m not sure of what the exact cause is here although I suspect it’s related to this issue with MSXML.

Reporting Services on Server 2008 64 bit

I was recently configuring Reporting Services for SQL 2005 on Windows Server 2008 64bit to get a System Center Essentials 2007 going. Each time we ran the installer we kept getting a message that Report Server wasn’t configured but the Reporting Services Configuration Manager wasn’t reporting any issues.

When connecting to the report server directly from Internet Explorer (http://localhost/Reports) we got the following error :-

Attempted to load a 64-bit assembly on a 32-bit platform. Use ReflectionOnlyLoad() instead if trying to load for reflect”

Not sure the exact cause of this but if you run the following command in the “\Inetpub\AdminScripts” it fixes everything.

cscript.exe adsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 false

MOSS on Server 2003 SP2 with SQL 2000

It appears that SQL 2000, MOSS and Windows Server 2003 Service Pack 2 don’t play too nicely together. During the config the MOSS Shared Service provider there are Authentication issue’s in SQL. The good news is by dropping Windows Server 2003 Service Pack 1 appears to be tolerant in this configuration with a couple of caveats.

  1. Make all the MOSS Service Accounts Administrators on the SQL Box. These privileges should be able to pruned at a later date, but there does seem to be issues with the installation and configuration of MOSS.
  2. The MOSS configuration tool that is usually run from Start Menu will not complete the installation. To get around this run the tool from the command line using “psconfig.exe” located under the “%COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\bin” folder.
  3. After running the MOSS Hotfixes following re-run the config tool after each upgrades completes, using the “psconfig.exe” command line tool. Again the Start Menu Option will not work. Here are the hotfixes :-
    • Windows SharePoint Services 3.0 hotfix package: May 8, 2007 – KB936867
    • SharePoint Server 2007 hotfix package for SharePoint Server 2007 and for SharePoint Server
      2007 for Search: May 8, 2007 – KB936877
    • SharePoint Server 2007 hotfix package: May 15, 2007 – KB937207

I’d be interested to work out what in SP2 actually stops SQL 2000 from working with MOSS, but then again I’m not in a rush to do another MOSS job with SQL 2000.

Remote Connections to SQL Server 2005

It appears that SQL 2005 doesn’t allow remote connections by default any more. When trying to connect to a remote SQL 2005 server with Management Studio, I got a “SQL Error 1326”. The fix is pretty easy using the “Surface Area Configuration” and is found in the KB article here