MarcViste
asked on
Sharepoint 2013 Database too old
I need to figur eout how to identify if these databases are just leftover crap from a 2010 to 2013 migration or if they are being used and if they are needed how to I rectify this issue. I have tried both commands listed in the remedy section, I get no errors and I get 100% successful on both commands, yet this status doesn't change. I get the following error:
The following databases require upgrade because their versions are older than the backwards compatible range:
StateService_baff9356d1f04 19dab84dfa 75021397a,
Secure_Store_Service_DB_d1 63a3c58119 4f50b0f964 d9df7b045e ,
User Profile Service Application_SocialDB_5ea46 57e15714c8 6bc0615ab3 bff3090,
Search_Service_Application _Analytics ReportingS toreDB_1fc aae8aac094 3edb2790d4 01c8f0e5b,
Search_Service_Application _CrawlStor eDB_d1edfb 4356b14256 bb7477ba3a d909c5,
Search_Service_Application _DB_d5c19b 3ca3a6454d a0c4ee1865 3eaac6,
Managed Metadata Service_beed8e2703194561a4 3c3c8f52f0 46aa,
User Profile Service Application_ProfileDB_c763 2a7c880a4b e79fdd205f 7770c909,
Search_Service_Application _LinksStor eDB_2e0dbe d4194a4293 88f81c41ec c8a41e.
Remedy
Use Upgrade-SPContentDatabase to upgrade Content databases, or psconfig.exe to upgrade other databases. If some databases are too new, check the Patch Status page to find out if the current server are missing SharePoint software patches. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142697".
The following databases require upgrade because their versions are older than the backwards compatible range:
StateService_baff9356d1f04
Secure_Store_Service_DB_d1
User Profile Service Application_SocialDB_5ea46
Search_Service_Application
Search_Service_Application
Search_Service_Application
Managed Metadata Service_beed8e2703194561a4
User Profile Service Application_ProfileDB_c763
Search_Service_Application
Remedy
Use Upgrade-SPContentDatabase to upgrade Content databases, or psconfig.exe to upgrade other databases. If some databases are too new, check the Patch Status page to find out if the current server are missing SharePoint software patches. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142697".
ASKER
Ok and how to I go about fixing my DB errors? If these are 2013 DB why are they saying outdated?
Can you post a screenshot of what you are seeing?
ASKER
I literally copied the text from the error in central administration. Is that not enough? What would you like a screen shot of?
ASKER
I'm thinking I need to do some major updating. I am on build:
15.0.4420.1017
Seems super old.
15.0.4420.1017
Seems super old.
SP1 was just released, so I'd go with that.
What happens when you run the SharePoint config wizard? What was the build version of your 2010 environment?
What happens when you run the SharePoint config wizard? What was the build version of your 2010 environment?
ASKER
I ran the configuration wizard in order to finish the upgrade after installing SP1 and it gets to step 9 and gets stuck forever. I let it go all of Friday and over the weekend just to be safe and it just never moves from "upgrading sharepoint products" at step 9.
old build was: 14.0.7015.1000 2010 SP2
old build was: 14.0.7015.1000 2010 SP2
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Because it was what happened and no other user had the input to be considered an answer.
I find the best way to list all databases in your farm is click Perform a Backup in Central Admin. On the selection screen you can see all databases in your farm.