“Databases running in compatibility range, upgrade recommended” when NeedsUpgrade=False

Question

• SharePoint Health Analyzer warning: Databases running in compatibility range, upgrade recommended. Explanation: The following databases have versions that are older than the current SharePoint software, but are within the backwards compatible range: DB_Content
• Ran Upgrade-SPContentDatabase DB_Content and it returned

WARNING: Database [SPContentDatabase Name=DB_Content] does not need to be upgraded.

• Ran Get-SPContentDatabase -Identity DB_Content |select Name, NeedsUpgrade and NeedsUpgrade returned False
• In Central Administration, under Manage Databases Upgrade Status, Status is No action required.
• I checked the logs and Event Id 2138 with the same description as the Health Analyzer explanation is showing up.

Why is the Health Analyzer rule reporting it as needing an upgrade and when I try the upgrade it says it doesn't need it? How can I resolve this?

Answer 1

SOLUTION (thanks to Waqas Sarwar MVP):Issue resolved after detaching and attaching this db from the WebApp. In my case I did it with Powershell in the App Server and running Management Shell as admin while logged as the farm account but for some reason it didn't work properly as it was being reported with Powershell as existing but it was not showing up in Central Administration. I had to detach it with Powershell and then using Central Administration add a content database. This way it worked and warning event 2138 was not showing up anymore, neither the Health Analyzer reporting it as a Warning.

Answer 2

We are seeing the same issue in our environment quite often. it is kind of false positive alarm. couple of things you can do in this case:

• Make sure, you farm account and App pool account have proper permission on this database.
• Try to re-analyze the rule and many times it auto fix.
• If their is any recent upgrade in the farm then run the psconfig wizard.

After consulting with MSFT, they told us apply the latest CU. But still we are seeing this error in a while, surprising couple of times it auto fix.

In case it is bothering you then you can run PSConfig wizard which will clear all these warning.