Hi everyone!

So in my company we've attached a post Service Pack 2 MOSS 2007 database to a new SharePoint 2010 environment and it works. Unfortunately the buttons under the "Visual Upgrade" section are grayed out.

 

Any pointers as to why?

Hi,

Before you did the upgrade did you do the Upgrade Checker? The upgrade checker validates if the upgrade is going to be successfull or not.

Most of the times it will check if it is possible to do a Visual Upgrade on your content database.

Can you verify this will a second hand database, so that you can verify if there're any problems with the content database?

Regards

Unfortunately, a sys admin who had just taken a Sharepoint training course did it while I was away so I don't know what the outcome of the checker was before they put it into the environment. 

When I check the Upgrade Status in Central Admin, I see 40 errors & 210 warnings

Hi Mike,

Did you ever find a solution to this problem?

Lallo

Unfortunately there isn't any command to enable these buttons.

You may try this method to upgrade the user experience:

1. Go to Site Settings -> Look and Feel -> Select Master page and then select V4.master and apply.

2. Once you apply V4.master, the look n feel of the homepage goes haywire without any css. Try locating a text "Site Actions" it should be somewhere on the left screen.

3. Site Actions does work. Select Visual Upgrade from the site actions menu. Visual Upgrade settings page will let you select one of the three options.

4. Apply the settings and all 2010 look n feel will be restored.

That's it. If you are using a custom master page, then you will need to open up in SPD 2010 and modify accordingly.

In many forums noticed that some users like to do detaching and attaching the databases and repeating the whole process again and again. Not too sure what they are after.

Hope this helps

Hi all,

 

So we never did get it fixed, but I did the whole upgrade & migration myself and the buttons are enabled.

I had a few errors but they were related to the custom master page & page layout being referenced in the database but not being installed in the new farm.

 

I'm not sure what that sys admin did but obviously it wasn't right.

• Marked as answer by Mike Hodge Thursday, June 14, 2012 9:34 PM

Hi all,

 

So we never did get it fixed, but I did the whole upgrade & migration myself and the buttons are enabled.

I had a few errors but they were related to the custom master page & page layout being referenced in the database but not being installed in the new farm.

 

I'm not sure what that sys admin did but obviously it wasn't right.

 

In many cases where the upgrade is not completed for the given site collections, the visual upgrade command is not available.  Since you mentioned there were a ton of errors in the upgrade log, it clearly didn't complete successfully.  Glad you were able to go back through it and have a successfull outcome.

Thank you so much Shafie!

Following your instructions resolved the issue with a site I was having this problem with. It was originally created using SPS#20, if that's relevant.

I had that issue with an imported site collection and this fixed it. Use this short powershell script to change between UI look and feel.

App-PSSnapin Microsoft.SharePoint.Powershell -ErrorAction SilentlyContinue

$SPWeb=Get-SPWeb http://server/sites/collection

$SPWeb.UIVersion=4;$SPWeb.Update();

where UIversion 4 is Sharepoint 2010 and 3 would be MOSS 2007 so, you can switch back and forth.

• Edited by Shilezi Friday, June 01, 2012 5:44 PM
• Proposed as answer by Shilezi Thursday, June 07, 2012 2:48 PM

If you are Mounting the same DB with the same SP Powershell Window, you would see the below errors in the SharePoint logs. Check the below post which solved my problem. Hope this helps.

[powershell] [SPUpgradeSession] [ERROR] [Date Time]: CanUpgrade [SPSite Url=http://webapplication/sitecollection] failed.
[powershell] [SPUpgradeSession] [ERROR] [Date Time]: Exception: Object reference not set to an instance of an object.
[powershell] [SPUpgradeSession] [ERROR] [Date Time]:    at Microsoft.SharePoint.Upgrade.SPSiteSequence.get_CanUpgrade()
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CanUpgrade(Object o)
[powershell] [SPUpgradeSession] [ERROR] [Date Time]: Cannot upgrade [SPSite Url=http://webapplication/sitecollection].

http://blogs.msdn.com/b/jorman/archive/2010/06/09/mount-spcontentdatabase-failing-on-blank-meeting-workspace.aspx

Thanks!

Solution to this was very simple,

Reason why Visual Upgrade was disabled:- V4 MasterPage was not there as Database was not upgraded properly while Mounting this could happen due to several reasons.

Solution:-Open SharePoint Management Shell as admin and run:-
PSCONFIG.EXE -cmd upgrade -inplace b2b -force -cmd applicationcontent -install
-cmd installfeatures

On all servers in your farm.

This will update your Databases and things will be good.