QPR
asked on
Databases running in compatibility range, upgrade recommended.
I've applied SP1, run psconfigure (which passed 4/4) and applied the june update.
I get this message in health analyser so using powershell I run upgrade-spcontentdatabase on each of the DBs listed below and each one comes back as not needing upgrading. Who to believe?!
The following databases have versions that are older than the current SharePoint software, but are within the backwards compatible range:
User Profile Service Application_SocialDB_632f7 9a7b5d7474 6b2e20d890 69b2d72,
WebAnalyticsServiceApplica tion_Stagi ngDB_4f9c9 74c-ac3b-4 092-80df-6 e48c37d751 7,
Search_Service_Application _CrawlStor eDB_27971e 2eb0524dc1 8536f35f29 9fc2fc,
Search_Service_Application _PropertyS toreDB_8b2 df94ec1ab4 611bd3b4df 8646cc269,
Search_Service_Application _DB_a3b5a0 388c9f4a22 ba2deb9982 062195,
Managed Metadata Service_8e01e221d51c4dcea1 906c06b3ec fdb5,
User Profile Service Application_ProfileDB_c6de dfc062bc4c 5090390ca8 e690b01b,
WebAnalyticsServiceApplica tion_Repor tingDB_110 ef732-c8e8 -4bb0-9da4 -9a1a8556e bad.
I get this message in health analyser so using powershell I run upgrade-spcontentdatabase on each of the DBs listed below and each one comes back as not needing upgrading. Who to believe?!
The following databases have versions that are older than the current SharePoint software, but are within the backwards compatible range:
User Profile Service Application_SocialDB_632f7
WebAnalyticsServiceApplica
Search_Service_Application
Search_Service_Application
Search_Service_Application
Managed Metadata Service_8e01e221d51c4dcea1
User Profile Service Application_ProfileDB_c6de
WebAnalyticsServiceApplica
ASKER
yep a couple of times
Also, did you apply all the correct updates?
You are actually supposed to apply the SharePoint Foundation updates, then the SharePoint server updates.
I had trouble until I applied all the appropriate updates in the proper order.
You are actually supposed to apply the SharePoint Foundation updates, then the SharePoint server updates.
I had trouble until I applied all the appropriate updates in the proper order.
ASKER
I d/l and installed SP1 and then the june 2011 cumulative update (which was said to be compulsory) after that.
I just followed a whitepaper for installing SP1
I just followed a whitepaper for installing SP1
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanks, I'll go through it when back in the office tomorrow. I really hope the admin side of SP get's less complex and more trustworthy in future updates!
The amount of time I have spent recently on fixing stuff or chasing cascading errors is huge
The amount of time I have spent recently on fixing stuff or chasing cascading errors is huge
Agreed. Generally it has been better but this last update definitely had a few issues. The one thing I can say is that even with some of these errors, at least the farm is still running and usable. With SharePoint 2007 if there were any errors in the update process the farm was down.
ASKER
I won't be putting SP1 and/or updates any where near the production server until I nail this - I don't have enough SP admin skills yet to resucitate it should it die.
psconfig.exe -cmd upgrade -inplace b2b -force
Or if required:
psconfig.exe -cmd upgrade -inplace b2b -passphrase <insert-passphrase-here> -force
That is what I did on my server