"Sites not completely upgraded" after installing Reporting Services 2012

Question

SharePoint 2010 SP1 - (Mar-Feb 2012 CU)  -  SQL Server Reporting Services 2012

I posted questions about this earlier in the year when installing the preview release of SQL Server Reporting Services 2012 into SharePoint TEST environment.  It looks like the issue is still occuring in the RTM release of SQL Server 2012 Reporting Services.

After provisioning the SQL Server Reporting Service App using powershell.  2 of the reporting service databases are showing the following upgrade status.  Is there any official word from Microsoft on this?  Has anyone else run into this? 

"ReportingServiceDatabase" -  Database is up to date, but some sites are not completely upgraded.
"ReportingServiceAlertingDatabase" -  Database is up to date, but some sites are not completely upgraded.

I'd like to put Reporting Services 2012 into our production environment, but until I'm sure it's working correctly, I'm holding off.

Thanks for any information!

Answer 1

Hi mikea730,

For this issue, after you installed SQL Server Reporting Services 2012, maybe it affects SharePoint 2010. Then you may need to upgrade the admin content database via PowerShell.

Below is the script:

$wa = Get-SPWebApplication -Identity "< Central Administration URL>"
foreach($ContentDB in $wa.ContentDatabases)
{
Upgrade-SPContentDatabase -id $ContentDB
}

More information, please refer to :

http://ianankers.wordpress.com/2011/08/23/sharepoint-2010-database-is-up-to-date-but-some-sites-are-not-completely-upgraded/

http://theblobfarm.wordpress.com/2011/08/30/sharepoint-2010-database-is-up-to-date-but-some-sites-are-not-completely-upgraded/

Best Regards.

Answer 2

I have the same issue in my lab. I clean build farms with SP1 + '12 FEB CU. Same issue. Looks like it was reportined in CTP3. http://connect.microsoft.com/SQLServer/feedback/details/721067/database-is-up-to-date-but-some-sites-are-not-completely-upgraded

I have yet to find a solution.

Answer 3

When I look in the ULS logs I’m also seeing the following 4 errors repeating.  Can you check to see if this is the case for you as well?  If it is, I’m going to call support!  That would save me a ton of work as I was thinking about installing again.  Thought somehow I installed the EVAL version, but I'm 99% sure I didn't.

Thanks!!!

Catalog SQL Server Edition = Evaluation

restricted SKUs: Developer Evaluation Workgroup Express Web  - actual SKU Evaluation

Throwing Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: , Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "The Database Engine instance you selected is not valid for this edition of Reporting Services. The Database Engine does not meet edition requirements for report data sources or the report server database. " is not supported in this edition of Reporting Services.;

Error in timer Database version check : Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "The Database Engine instance you selected is not valid for this edition of Reporting Services. The Database Engine does not meet edition requirements for report data sources or the report server database. " is not supported in this edition of Reporting Services.

Answer 4

When I look in the ULS logs I’m also seeing the following 4 errors repeating.  Can you check to see if this is the case for you as well?  If it is, I’m going to call support!  That would save me a ton of work as I was thinking about installing again.  Thought somehow I installed the EVAL version, but I'm 99% sure I didn't.

Thanks!!!

Catalog SQL Server Edition = Evaluation

restricted SKUs: Developer Evaluation Workgroup Express Web  - actual SKU Evaluation

Throwing Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: , Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "The Database Engine instance you selected is not valid for this edition of Reporting Services. The Database Engine does not meet edition requirements for report data sources or the report server database. " is not supported in this edition of Reporting Services.;

Error in timer Database version check : Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "The Database Engine instance you selected is not valid for this edition of Reporting Services. The Database Engine does not meet edition requirements for report data sources or the report server database. " is not supported in this edition of Reporting Services.

I don't see that in my ULS log. How often is that showing up?

Another interesting note is on another farm I tried deleting the service application while preserving the datbases. When I attempt to create a new SSRS SA connecting to the existing DB it fails.

Answer 5

It's repeating about every couple minutes.

I'm going back through the installation again just to be sure I installed everything correctly before calling Microsoft.

Answer 6

Did anyone find a fix to this issue? we are now experiancing the same problem.

thanks  Paul

Answer 7

See http://sharepoint.nauplius.net/2012/08/reporting-services-2012-some-sites-are.html.  You can ignore this message safely.

---

SharePoint - Nauplius Applications
Microsoft SharePoint Server MVP
MCITP: SharePoint Administrator 2010

Answer 8

I think I figured out the sequence of events to avoid this.   Install the base RTM Reporting Services 2012 with no maintenance, then provision the services which creates the databases, then install SQL Server SP1.  When I use this sequence the 2 reporting services databases do not show this upgrade status.

One additional question I do have,  I noticed that most of the "content" database show the same message "Database is up to date, but some sites are not completely upgraded".  Anyone have any idea what Reporting Service installation is doing to the content databases?  When I check the detail upgrade status of the databases  the "current" and "maximum" versions match.  So I'm not sure why it's wanting an upgrade.  Simply running the "pgrade-SPContentDatabase" fixes it, but I'm wondering why the installation of Reporting Services is touching the content databases.

Also, does anyone have experience with Reporting Services in a multi server (2 WFE, 2 APP servers) production environment?  if so, when you installed it, did you install and provision with the production farm active?  Or did you schedule downtime.  The reporting add-in will be installed on the WFEs and the Reporting Services on the APP servers.  I need to install Reporting Services and PowerPivot into production and I'm wondering whether I should do this while users are active or not.  

Thanks!!

Answer 9

I think I figured out the sequence of events to avoid this.   Install the base RTM Reporting Services 2012 with no maintenance, then provision the services which creates the databases, then install SQL Server SP1.  When I use this sequence the 2 reporting services databases do not show this upgrade status.

One additional question I do have,  I noticed that most of the "content" database show the same message "Database is up to date, but some sites are not completely upgraded".  Anyone have any idea what Reporting Service installation is doing to the content databases?  When I check the detail upgrade status of the databases  the "current" and "maximum" versions match.  So I'm not sure why it's wanting an upgrade.  Simply running the "pgrade-SPContentDatabase" fixes it, but I'm wondering why the installation of Reporting Services is touching the content databases.

Also, does anyone have experience with Reporting Services in a multi server (2 WFE, 2 APP servers) production environment?  if so, when you installed it, did you install and provision with the production farm active?  Or did you schedule downtime.  The reporting add-in will be installed on the WFEs and the Reporting Services on the APP servers.  I need to install Reporting Services and PowerPivot into production and I'm wondering whether I should do this while users are active or not.  

Thanks!!

Those steps work on a clean SSRS install? What about the upgrade? Part of the upgrade process while its upgrading SSRS is it upgrades the RS DB's and creates a SA.

I wouldn't do the upgrade with users online. If the pwoerpivoit install is as complicated as it was on 2008 r2 there no way i would do it online.

Answer 10

See http://sharepoint.nauplius.net/2012/08/reporting-services-2012-some-sites-are.html.  You can ignore this message safely.

---

SharePoint - Nauplius Applications
Microsoft SharePoint Server MVP
MCITP: SharePoint Administrator 2010

Thats nice taht he says that but it not truie in my case. Sure it didn't seem to imapct the services, but where I ran into a serious issue si when i deleted the SA and tried to create a new one and use the existing DB's. It would error out trying to upgrade the DB everytime. That doesn't exactly leave me in a comfortable sport not being able to recreate the SA.

Answer 11

With regards to your comment on a "clean SSRS install".  Do you mean an existing farm that does "not" have SSRS installed?  If so, that's what I'm doing.   Here is the sequence:

- Install SSRS 2012 RTM on the 1st application server

- Provision Service Applications with PowerShell (this creates databases also).

- Install SQL Server 2012 SP1 on the 1st application server

- Install SSRS 2012 RTM on the 2nd application server

- Install SQL Server 2012 SP1 on the 2nd application server

- Run "Upgrade-SPContentDatabase" on the content databases that show the "not all sites upgraded" message.

- Install the SSRS Add-in on the WFEs

Does this sound reasonable?  This is what I've done our TEST farm.

Thanks!

Answer 12

See http://sharepoint.nauplius.net/2012/08/reporting-services-2012-some-sites-are.html.  You can ignore this message safely.

---

SharePoint - Nauplius Applications
Microsoft SharePoint Server MVP
MCITP: SharePoint Administrator 2010

Thats nice taht he says that but it not truie in my case. Sure it didn't seem to imapct the services, but where I ran into a serious issue si when i deleted the SA and tried to create a new one and use the existing DB's. It would error out trying to upgrade the DB everytime. That doesn't exactly leave me in a comfortable sport not being able to recreate the SA.

I've done exactly this without any errors (but you need to make sure to export the encryption key).  Again, per the code, these databases are not "upgradable", but SharePoint thinks they are which is why we see the status message in "Review database status".

---

SharePoint - Nauplius Applications
Microsoft SharePoint Server MVP
MCITP: SharePoint Administrator 2010

Answer 13

Trevor,

Did you install SSRS while the Farm was active with users?  Or did you schedule downtime and block access via the load balancers or something similar?

Thanks!

Answer 14

We did the installation after-hours, but did not specifically schedule downtime.  Given there should be no downtime (you're not recycling Web Application App Pools with this work), I don't see why this couldn't be configured during working hours.

However, test, test, test!

---

SharePoint - Nauplius Applications
Microsoft SharePoint Server MVP
MCITP: SharePoint Administrator 2010

Answer 15

Trevor,

I’m also planning to deploy PowerPivot 2012.  I’m doing the provisioning using PowerShell.  Have you deployed PowerPivot to production as well?  If so, did you schedule downtime for that?

Thanks!

Answer 16

PowerPivot deploys two WSPs which will cause outages during the deployment of those solutions.  Yes, we planned for downtime during the PowerPivot installation/deployment process.

---

SharePoint - Nauplius Applications
Microsoft SharePoint Server MVP
MCITP: SharePoint Administrator 2010

Answer 17

Did you lock the users out, or did you just schedule downtime and let users know that the solution deployment would cause an IISRESET, but still allow users access.    I'm trying to determine if we should schedule downtime for the whole time (SSRS and PowerPivot deployment).  Basically disable the WFE load balancer to stop traffic (adding local host entries on each farm member pointing back to one of the WFEs).   Shutdown the farm, snapshot the VMs (all farm members are VMs) and backup the databases for a recovery point if needed.  or do you think that's overkill?

Thanks for the information!!

Answer 18

For our downtime, we simply tell the users when it will be unavailable.  If they're doing something and we're forced to do a restore (or they're kicked off due to web app resets, etc.), they're out of luck by our policy.

Snapshotting SharePoint and their associated SQL Server VMs is not supported and will put you in an unsupported configuration state with Microsoft.

---

SharePoint - Nauplius Applications
Microsoft SharePoint Server MVP
MCITP: SharePoint Administrator 2010

Answer 19

Sorry, I know we're getting way off topic here!

I didn't realize MS doesn't support snapshoting before maintenance.  I've not done this in production, but in test I shutdown the farm, snapshot the 4 farm members and then do SQL Server 2012 database level snapshots with the farm still down (no VM snapshots on the database).  I do this to try different scenarios and it works great.  Never had a problem restoring the snapshots as long as the farm is shutdown during the snapshot as well as the restore of the snapshots.

So under a restore scenario in production, restoring the content database is very easy, my concern with doing SharePoint maintenance has always  been the farm config or some other unrecoverable issue with the farm.  It would make for a long night to have to rebuild the farm and remount the restored databases.  I'm reasonably new with SharePoint, but it sounds like you have a lot of experience.  Have you ever run into any issues with maintenance or the installation of new features like SSRS or PowerPivot where you had to recover?

Sorry for all the questions, but sometimes with SharePoint I feel like I'm deserted island when it comes to figuring out the best practices for this kind of thing.  :)

Thanks!

Answer 20

Microsoft doesn't support snapshotting on two fronts: Performance due to using a differencing disk as well as due to timing issues (since the VMs, including the SQL Server, cannot be snapshotting within the same ms, the timer job timing would be off if the snapshot were restored).

As far as maintenance, I honestly wouldn't worry about it to terribly much.  Custom code and upgrades concern me the most -- pretty much everything else is recoverable one way or another.  If all else fails, call PSS with a Sev A :-)

I've run into *many* issues with the PowerPivot installation, but those are all resolved now with the help of PSS (Kerberos issues, as well as SharePoint not assigning rights appropriately - see http://blogs.msdn.com/b/psssql/archive/2012/12/05/filenotfoundexception-with-microsoft-analysisservices-xmla.aspx, which is a case I initiated that Adam helped me with).

I've never had any "dead farm" issues with PowerPivot.  Always resolved them and never have had to do any sort of restore of the farm.

SSRS, not so much.  More because I know SSRS much, much better than I do PowerPivot, and also because SSRS configuration is quite a bit less complex.

---

SharePoint - Nauplius Applications
Microsoft SharePoint Server MVP
MCITP: SharePoint Administrator 2010

Answer 21

I'm going back through the installation again just to be sure I installed everything correctly before calling Microsoft. 

Answer 22

Gull,

I would be interested in knowing if after you install SSRS 2012 but before you provision, whether the content databases show "Database is up to date, but some sites are not completely upgraded".  In Central Admin, "Upgrade and Migration-->"Review Database Status". 

I also found that if you provision SSRS before you install any maintenance (SP!, etc...) you might avoid the services applications database showing needing upgrade.

Thanks!

Answer 23

SSRS does not impact the content databases.  If you're seeing this on the content databases, then running an Update-SPContentDatabase should resolve the issue, or you'll have to further investigate in the ULS logs.

---

SharePoint - Nauplius Applications
Microsoft SharePoint Server MVP
MCITP: SharePoint Administrator 2010

Answer 24

Trevor,

Yes, the Update-SPContentDatabase does clear the upgrade flag on the content databases.  But I'm wondering why the SSRS installation is causing this.  Wondering if anyone else has seen this.

By the way, thanks for all your information and help with this.  It's greatly apprecaited!

Thanks,

Mike

Answer 25

It isn't.  I've done dozens of SSRS integrated installs and have never seen this in any environment.

---

SharePoint - Nauplius Applications
Microsoft SharePoint Server MVP
MCITP: SharePoint Administrator 2010

Answer 26

Do you provision with PowerShell or with the psconfig?  It might be that psconfig is taking care of the upgrade duing the provisioning.

Thanks!

Answer 27

SSRS isn't provisioned with psconfig.

---

SharePoint - Nauplius Applications
Microsoft SharePoint Server MVP
MCITP: SharePoint Administrator 2010

Answer 28

I'm using PowerShell rather than provisioning from SPCA.  But in my case the database is set to upgrade status as a result of running the SSRS installation.  The other strange thing is the SSRS installation takes a ver long time (45 minutes) and seems to hang occasionally.   Guess I need to open a case with Microsoft.

Answer 29

I opened a case with Microsoft regarding the content databases showing "Database is up to date, but some sites are not completely upgraded" after installing SSRS 2012.  The support rep was able to duplicate this in his test environment and then escalated it to engineering.  

Looks like this is by design and expected.  After installing SSRS 2012 the content databases will need to be upgraded using the "Upgrade-SPContentDatabase" applet.  The support rep said they would be updating the documentation to include the "Upgrade-SPContentDatabase" step after SSRS has been installed.

Additionally the case where the following SSRS service application databases are showing this message is also a known issue and is fixed in SQL Server SP1

"ReportingServiceDatabase" -  Database is up to date, but some sites are not completely upgraded.
"ReportingServiceAlertingDatabase" -  Database is up to date, but some sites are not completely upgraded.

Thanks,

Mike