If you’ve read my blog one or twice or heard me speak at a conference you know how much developers pick on me. It’s like junior high all over again, but I am getting stuffed in fewer trash cans, so that’s nice. This week the vast developer conspiracy found a new way to stick it to me.
I was just minding my own business, installing the SQL 2008 R2 version of SQL Server Reporting Services (SSRS) for a customer. After I got the bits installed I started configuring SSRS and I got this lovely message:
For the benefit of search engines here’s the text of the message:
The feature: “Using other editions of SQL Server for report data sources and/or report server database” is not supported in this edition of Reporting Services.
I was installing SSRS on a server running SharePoint, and the SQL backend database server was a different machine. This error seems pretty straight forward. The edition of SSRS I’m installing doesn’t support having its databases on another server. This was news to me. I had done this a dozen times (some of them even worked) and it’s supported. Just to be sure I double-checked the version of SQL I had installed from and it was the Enterprise Edition. All should be good. But yet, it wasn’t.
Despite the error being very clear that this was a problem with SSRS, I decided to look at the backend database server I was trying to use. Here was the problem:
The backend server was running the Developer Edition of SQL 2008 R2. The Developer Edition of SQL server is available to MSDN subscribers. It has the same functionality (except SSRS, apparently) as the Enterprise Edition of SQL Server, but it licensed for use by developers in development and test environments. When I was writing my Installing SSRS 2012 without upgrading your database server blog post I encountered the same problem. The VM I was using to test that blog post was also running the Developer Edition of SQL Server and I got similar issues. Could I be having the same problem on this server? On a hunch, I pointed the SSRS install at an instance of SQL server that was running the Enterprise Edition. Surprise, surprise, it worked just fine.
Once again, developers and poor error messages conspire against me. Fortunately I was able to defeat them.