Renaming SQL Server and Reporting Services

Renaming SQL Server & Reporting Services

If you change the name of a Windows Server which hosts a SQL Server instance then there a few steps you’ll need to take…

Rename SQL Server:

In SQL Server Management Studio check the name SQL has for itself:

print @@servername -- shows old name

If this isn’t your new server name then:

sp_dropserver @@servername -- drop old name
sp_addserver new_name, local -- add new machine name

Now restart SQL Server and:

print @@servername -- first time will give a transport error,
 the second should show the new name

Reporting Services 2005:

  • Delete 2 IIS virtual directories for Reports and ReportServer
  • Open Reporting Services Configuration Manager from start menu:
    • Create 2 new Virtual Directories for Report Server and Report Manager
    • Database setup – choose the new server
    • Web Service Identity – choose the RS app pool
    • Encryption Keys – delete or restore if you have a backup

The process for Reporting Services 2008 should be simpler as it doesn’t use IIS.


Further Information on Report Viewer Client Print Control bug

A while back I wrote a post about the “Unable to load client print control” error that Report Manager (and RSinteract) was throwing after Microsoft’s auto update KB956391.

I also asked a question over at StackOverflow which I ended up answering myself. Yesterday follow up information was added, which may be of use if you have trouble with the fix.

EY Kalman says:

I have had the same problem (on several different servers). Applying SP3 and Report Viewer SP1 has helped on some of the servers, allowing the client machines to connect and download the control with no problem. However, I have had one server that, even after applying the updates, when accessing the report viewer using a client machine, it was still giving me the error. On looking into the exact URL GET request that is being sent, I discovered that it is possible to force the client machine to connect directly to the Report Server to download the control.

The user would need to enter the following url:


This should then pop up the required download/install prompt.

dotnettrio added (which is probably more relevant to RSinteract):


I got this working with out removing any patches. The above patch was not working too. Finally what I did was on the IIS server install the following patch and reset / restart the IIS server. This is not for report manager application. This is for any ASP.NET Web application developed in .net3.5 using VS2008

I hope this helps anyone else with this problem.

Could not load file or assembly 'Microsoft.ReportingServices.Interfaces'

In the last week we’ve had three clients report a problem with our December release when running on Windows Server 2003 64 bit.

Server Error in ‘/RSinteract’ Application.

Could not load file or assembly ‘Microsoft.ReportingServices.Interfaces’ or one of its dependencies. An attempt was made to load a program with an incorrect format.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.BadImageFormatException: Could not load file or assembly ‘Microsoft.ReportingServices.Interfaces’ or one of its dependencies. An attempt was made to load a program with an incorrect format.

It seems Microsoft.ReportingServices.Interfaces.dll version 9.0.1399.0 won’t load on a 64 bit server, the hotfix is to replace it with this version:
The default location is C:\Program Files (x86)\ICS\RSinteract\Website\bin\
IIS should be reset afterwards.

This issue will be resolved in the next big release in February 2009

The Double Hop Problem

Let me start by apologising for the lack of a post in the last week or so, I have been really busy with the new, improved version of RSinteract (sneak preview in the next couple of weeks, watch this space).

One of the issues we have experienced time and again with RSinteract is a scenario where the ReportServer/Database or Analysis services is on a different machine from RSinteract as demonstrated in the following diagram. The problem manifests itself as an authentication issue when Reporting Services tries to retreive information from the Database or Analysis server because Active Directory credentials expire after the first hop, in this case from RSinteract to Reporting Services.

double hop diagram

Microsoft are calling this the “Double Hop” problem. The reason for Reporting Services’ and Analysis Services’ lack of integration out of the box is “in the interest of security”. Active Directory uses Kerberos under the hood which can be configured to pass credentials between web apps or not. To get this working with RSinteract or indeed any ASP.NET application you need to correctly configure Kerberos delegation.

I’m having trouble tracking down the steps for Reporting Services, the link I had has gone dead since I began writing this post

So here’s the steps to configure your Analysis Services (from Business Intelligence and Agile Development Blog):

  1. Download and install the SetSPN utility (Either from the Windows Resource kit, or from
  2. SETSPN is used to configure a “Service Principal Name”, which is required by Kerberos
  3. Create a Service Principal Name (SPN) for the Analysis Services Instance (on the AS server)
  4. (If AS is running as a domain account) setspn.exe –A MSOLAPSvc.3/
  5. Configure Active Directory Settings
  6. All users that are connecting to Analysis Services through the intermediate host need to be allowed to use Kerberos Delegation (“Account is sensitive and cannot be delegated” must be unchecked)
  7. The “Account is trusted for delegation” setting must be checked for each user and each service account used in the process.
  8. The “Trust computer for delegation” setting must be checked for each computer used in the process
  9. Configure IIS Settings for the Virtual Directory hosting the application (or SharePoint site)
  10. The Authentication must be set to “Integrated Windows Authentication” or “Basic Authentication”
  11. The application protection level must be set to “High (Isolated)”
  12. The impersonation level for COM+ must be set to “Delegate”
  13. The COM+ application identity must be set to an account where “Account is trusted for delegation” is checked.
  14. Connection strings must include SSPI=Kerberos
  15. Connection strings CANNOT use IP Addresses

Here’s some more information pertaining to the bug:

I’ll update this post as soon as I find the information for configuring SSRS.