Thursday, April 26, 2012

SQL Server 2012 Reporting Services Upgrade Error


During the In-Place upgrade from SQL Server 2008 R2 to SQL Server 2012, sometimes the Reporting Services component upgrade would error out with  different types of error messages:

Specifically, the errors would be something like:

  • A Secure Sockets Layer (SSL) certificate is not configured on the Web site
  • An SSL binding already exists for the specified IP address and port combination. The existing binding uses a different certificate from the current requests. Only one certificate can be used for each IP address and port combination. To correct the problem, either use the same certificate as the existing binding, or remove the existing SSL binding and create a new binding using the certificate of the current request.

To resolve this issue, it is important to understand the workflow of the Reporting Services upgrade path. Your best friend in this case is MSDN. I could not find anyone else having the same problem.

Going to MSDN: (Upgrade and Migrate Reporting Services), the first thing you will notice here is :

  • Run the upgrade advisor before you do the upgrade
  • Remove invalid SSL certificates.  This includes certificates that are expired and you do not plan to update prior to upgrading Reporting Services.  Invalid certificates will cause upgrade to fail and an error message similar to the following will be written to the Reporting Services Log file: Microsoft.ReportingServices.WmiProvider.WMIProviderException: A Secure Sockets Layer (SSL) certificate is not configured on the Web site.

I ran the upgrade advisor and not find any issues.  The SSL Certificates on the server were still valid and not expired.

So, I took a snapshot of the VM and ran the upgrade. It failed giving me the second reporting services error. I reverted back the snapshot and then opened up reporting services configuration manager. In here, I made the below two changes before the upgrade was restarted:

  • Under Web Service URL
    • IP Address –> Changed it to “All Unassigned”
    • Under Advanced –> Removed the SSL Certificates
  • Under Report Manager URL
    • Click Advanced –>  change the IP Address to Unassigned and Remove the SSL bindings.

Both the above steps are necessary. Even if you don’t do one piece, the Upgrade fails.

Once the above steps were done, the upgrade was very smooth and successful.


Anonymous said...


Thanks for the article, any idea how to get round it on a 2005 to 2008R2 upgrade - the options in reporting services configuration manger don't seem to exist in 2005 and I need to do this on 170 servers :-(


Mark Aggleton

Anonymous said...

This saved my day, thank you very much. worked for a 2008 to 2008R2 upgrade

Anonymous said...

This helped me overcome this problem ... thank you for your post!

Post a Comment