Asked by:
WARNING: Database [SPContentDatabase Name=intranet_Content] cannot be upgraded.

Question
-
I did a get-spsite, which returend all 15s except for a few sites which were blank.
Tried running upgrade-spcontentdatabase intranet_content, got
WARNING: Database [SPContentDatabase Name=intranet_Content] cannot be upgraded.Checked the CA DB Upgrade Status (no action required) and Schema version, everything looks good, only mismatch between current and max is
Microsoft.SharePoint.Administration.SPContentDatabase Current Schema Version: 16.0.4549.1001, Maximum Schema Version: 16.0.4549.1000
which i think is common and not to be worried over.
I'm having some problems running a script against the db,
"
The following exception occurred while trying to enumerate the collection: "There is a compatibility range mismatch between the Web server and
database "intranet_Content", and connections to the data have been blocked to due to this incompatibility. This can happen when a content
database has not been upgraded to be within the compatibility range of the Web server, or if the database has been upgraded to a higher level than
the web server. The Web server and the database must be upgraded to the same version and build level to return to compatibility range.".
At line:10 char:18"
Any ideas? Thanks.
Thursday, March 8, 2018 10:15 PM
All replies
-
Give the user SHELL ADMIN ACCESS on that content database, then try again.
ADD-SPSHELLADMIN
We had an issue like this one, and this solved our issue. Worth a shot
If this is helpful please mark it so. Also if this solved your problem mark as answer.
- Edited by taylor.l Friday, March 9, 2018 8:48 AM
Friday, March 9, 2018 8:45 AM -
Hi scogordo,
You can try below things for narrowing your issue:
1. run the SharePoint Products Configuration Wizard.
2. Increase the permissions(dbowner) for the App Pool Identity on CONTENT DB and then check if issue solved.
3. Make sure if you are using correct upgrade-spcontentdatabase command:
Upgrade-SPContentDatabase -Identity <<content database name>>
4. Try below cmd commands:
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
Also try to clear the config cache and re-run the upgrade.
Best regards,
Allen Bai
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.- Proposed as answer by Linda ZLMicrosoft contingent staff Tuesday, March 13, 2018 10:18 AM
Friday, March 9, 2018 9:09 AM -
Hi scogordo,
How are things going?
If you think my suggestion is helpful, you could mark it as an answer. It will help others who meet the similar question in this forum.
Best regards,
Allen Bai
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.Monday, March 19, 2018 5:32 AM -
Hi,
How are things going? I'm willing to hear from you.
Best regards,
Allen Bai
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.Tuesday, March 27, 2018 8:52 AM -
Hi,
How are things going?
Best regards,
Allen Bai
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.Monday, April 2, 2018 9:27 AM