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_baff9356d1f0419dab84dfa75021397a,
Secure_Store_Service_DB_d163a3c581194f50b0f964d9df7b045e,
User Profile Service Application_SocialDB_5ea4657e15714c86bc0615ab3bff3090,
Search_Service_Application_AnalyticsReportingStoreDB_1fcaae8aac0943edb2790d401c8f0e5b,
Search_Service_Application_CrawlStoreDB_d1edfb4356b14256bb7477ba3ad909c5,
Search_Service_Application_DB_d5c19b3ca3a6454da0c4ee18653eaac6,
Managed Metadata Service_beed8e2703194561a43c3c8f52f046aa,
User Profile Service Application_ProfileDB_c7632a7c880a4be79fdd205f7770c909,
Search_Service_Application_LinksStoreDB_2e0dbed4194a429388f81c41ecc8a41e.

 

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".
MarcVisteAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
MarcVisteConnect With a Mentor Author Commented:
The upgrading sharepoint products phase never finishes in the GUi, but it seems that the process did finish anyhow. After a reboot it all worked.
0
 
Justin SmithSr. System EngineerCommented:
Analytics and Linkstore databases are deffinately 2013.

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.
0
 
MarcVisteAuthor Commented:
Ok and how to I go about fixing my DB errors? If these are 2013 DB why are they saying outdated?
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
Justin SmithSr. System EngineerCommented:
Can you post a screenshot of what you are seeing?
0
 
MarcVisteAuthor Commented:
I literally copied the text from the error in central administration. Is that not enough? What would you like a screen shot of?
0
 
MarcVisteAuthor Commented:
I'm thinking I need to do some major updating. I am on build:

15.0.4420.1017

Seems super old.
0
 
Justin SmithSr. System EngineerCommented:
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?
0
 
MarcVisteAuthor Commented:
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
0
 
MarcVisteAuthor Commented:
Because it was what happened and no other user had the input to be considered an answer.
0
All Courses

From novice to tech pro — start learning today.