.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

Simple "planned relocation" upgrade from SP 2007 to SP 2010 question...

Posted By:      Posted Date: October 19, 2010    Points: 0   Category :SharePoint

I would like to migrate our current SP 2007 "wss_content" db (running on a separate SQL 2005 server) to our new SP 2010 server (also with separate SQL 2008 SP1 db server) and I need some help.

On the current SP 2007 server, we are using the default web app set for port 80 with the default content db (wss_content) and would like to simply move/upgrade this db to a new SP 2010 server (content db wss_content and default web app for port 80).  The new SP 2010 server is setup and I have run the Farm and initial site config wizards on it to create the initial web app & content db (wss_content).  I am getting confused on the steps for detaching the db from the old server, detaching the content db on the new server, restoring the old content db to the new server and then re-attaching the content db to the web app on the new server.  Or, can this be done in this manner?

Any help is much appreciated.  I am not a SharePoint expert as you can probably tell so let me know if you need more info/detail.



View Complete Post

More Related Resource Links

Cannot crawl sharepoint site and mysite after database attach upgrade form sharepoint 2007 to 2010.

After database attach upgrade site and mysite from sharepoint 2007 to 2010 , I have full crawl and get "The crawler could not communicate with the server. Check that the server is available and that the firewall access is configured correctly. If the repository was temporarily unavailable, an incremental crawl will fix this error. ( Error from SharePoint site: HttpStatusCode ServiceUnavailable The request failed with HTTP status 503: Service Unavailable. )" for mysite and get "Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled." for sharepoint site. The content access account for search is "db_owner" of both of site and mysite. How do I solved this problem ?

how to Upgrade MOSS 2007 to MOSS 2010 ?

how to Upgrade MOSS 2007 to MOSS 2010

Inplace upgrade from moss 2007 to 2010 fails

Hello experts I have tried without success to do an inplace upgarde of a moss 2007 installation that I would consider very basic. The upgrade process itself seems fine but after you finish the configuration wizard and it attempts to go to the upgrade status page you get The provider 'CurrentNavigation' specified for the defaultProvider does not exist in the providers collection. (C:\inetpub\wwwroot\wss\VirtualDirectories\39291\web.config line 385) When i check the upgrade errors logs im getting the following [OWSTIMER] [SPSiteWssSequence2] [INFO] [8/9/2010 2:18:36 PM]: SPSite Url=http://ehbmossserver/mysite [OWSTIMER] [SPSiteWssSequence2] [ERROR] [8/9/2010 2:18:36 PM]: Feature upgrade failed for Feature 'PremiumSite' (Id: '8581a8a7-cf16-4770-ac54-260265ddb0b2') in Site 'http://ehbmossserver/mysite'. [OWSTIMER] [SPSiteWssSequence2] [INFO] [8/9/2010 2:18:36 PM]: SPSite Url=http://ehbmossserver/mysite [OWSTIMER] [SPSiteWssSequence2] [ERROR] [8/9/2010 2:18:36 PM]: Exception: Dependency feature with id 4c42ab64-55af-4c7c-986a-ac216a6e0c0e for feature 'PremiumSite' (id: 8581a8a7-cf16-4770-ac54-260265ddb0b2) is not installed. [OWSTIMER] [SPSiteWssSequence2] [INFO] [8/9/2010 2:18:36 PM]: SPSite Url=http://ehbmossserver/mysite [OWSTIMER] [SPSiteWssSequence2] [ERROR] [8/9/2010 2:18:36 PM]: at Microsoft.SharePoint.SPFeature.HandleUpgradeException(Exception e, Boolean continue

MOSS 2007 upgrade to Sharepoint 2010 across domains

I recently did an upgrade at a customer site. I migrated their content successfully as well as their Mysites. Their MOSS farm was situated on a domain, let's say "domain 1". Due to a merger, their domain had to change to "Domain 2". The Sharepoint 2010  farm was set up on new domain. We now need to change the existing user logins from the upgraded content db to the new domain. domain1\user to Doamin2\user.  We considered a manual process, but it is simply not a viable option. Furthermore, the migrated mysites works fine, but the problem is, the users need to login with their old login details to view the content. Which is unacceptable. The mysite content now needs to be associated with the users on the new domain. Bear in mind that the users already have logins and permissions as per the previous configuration (domain1\user) I consideredd using the stsadm migrate user command, but that could also be laborious. The other concern is the SID associated to each login. I am not sure if the -ignoresidhistory switch will help, or if this command is even usable in SP 2010. I there possibly another, more effective method to accomplish these tasks, say a Powershell script or a magic wand?   Regards,   Warren  

Upgrade from MOSS 2007 Trial to Sharepoint Server 2010

I have a client who setup MOSS 2007 Trial and are coming up on the expiration.  Instead of buying a key for MOSS 2007 they purchased Sharepoint 2010.  I'm having some problems upgrading because its the trial.  What are my options for upgrading/migrating over to Sharepoitn 2010?

Move or just upgrade SP 2007 to 2010?

Purpose We have Sharepoint 2007 sp2 running with 1 application server (w2k3, 100gb) 1 index server (w2k3, 200gb) 1 web front end (w2k3, 60gb) 1 sql 2008 x64 We want to migrate to Sharepoint 2010 STD (not beta). Action plan Backup application server, index server and web frontend Reinstall OS Win2008 x64 on app, index and frontend Install SH 2010 on app, index and frontend Put SQL link back in sharepoint 2010 Question Will this plan work and not cause more trouble than solutions?

MOSS 2007 to SharePoint Server 2010 Hybrid Upgrade Approach on Windows Server 2003 x64

There's some guidance circulating about upgrading to 2010 with a mix of In-Place and Database Attach upgrade methods. My Central Admin and SharePoint Web App are on a 64 bit server, but it's running on Windows server 2003 x64 and not on Windows Server 2008 or 2008 R2. SharePoint Team Blog says Server 2008 or 2008 R2 is required for SP2010. If I want to do the hybrid upgrade approach, is it possible to first upgrade the OS to Server 2008 R2 on the server where my Central Admin and SP Web App runs?  Or will this break MOSS 2007?

SharePoint 2007 upgrade to 2010 without UI update masterpage issue

I have a public facing site on a SharePoint 2007 farm that will be upgraded to 2010.  This site has a very customized look and feel that will not initially be updated to the 2010 UI.    I have run into one small issue with 2010's handling of legacy 2007 UIs.In SharePoint 2007,  to have a different master page for the application pages and dialog boxes we utilized an HTTP Module to switch the master page on the fly.    After migrating the SP2007 into our 2010 beta test environment the HTTP Module no longer worked properly.   I did some debugging and found out that SharePoint 2010 is returning a NULL value for MasterPageFile property on the pages in the _layouts folder.   I would have expected to see the URL pointing to the application.master page (or dialog.master).   Any ideas if this is a bug in SP2010 beta and will be fixed in RTM or is this the intended behavior.If it is the intended behavior in SP2010 how could I update my HTTP Module to allow the site to continue functioning as it did on 2007?   

SharePoint 2007 to 2010 Upgrade AND Farm Merge


Hello all,

I'm curious to see if anyone has done this.  Currently, my environment has 3 seperate SharePoint 2007 server farms.  I'm currently evaluating SharePoint 2010 and so far like what I see.  I'm wondering though what would be the steps I would need to go through to actually upgrade and then merge them all to one SharePoint 2010 farm?  The steps I can think of are the following:

1. Make sure all 2007 farms are on the lastest (or at least similar) version

2. Upgrade each farm to SharePoint 2010

3. Create new 2010 farm

4. Copy upgraded farms' site collections to NEW 2010 farm.

OR can I do this:

1. Make sure all 2007 farms are on the same version

2. Create a copy of each current SharePoint 2007 site collection that I want

3. Create NEW 2007 Farm

4. Copy content to new farm

5. Upgrade new farm to 2010


Any and all help would be greatly appreciated, thanks!


How to upgrade MOSS 2007 custom site definitions to SharePoint 2010?

I would like to know how to upgrade custom site definitions of MOSS 2007 to SharePoint 2010 in detail?

No Tabular View / Selection Boxes on Views after upgrade from 2007 to 2010


We upgraded one of our smaller SharePoint instances and after the upgrade and change to the new UI, the tabular / selection box's in the views are not appearing, we have to create a new view and delete the migrated view to get them to appear. This has us very concerned since this would be a major effort on our larger instance.

Has anyone else run into this? Our small instance is pretty out-of-box, we added an image to the master page, choosed an out-of-box color theme and then made a template of a site with version limits setup on the document library that we reuse to build new sites.

Looking for guidance: Integrated SharePoint SSRS migration and upgrade from 2007 to 2010


Our existing prod farm is MOSS 07 with an integrated SSRS instance using SQL Server 2008, both on Windows Server 2003 64bit boxes. SharePoint databases are on a different SQL Server 2008 server.

I have built a new SharePoint 2010 farm on Windows Server 2008 R2 boxes, using a single SQL Server 2008 R2 Enterprise server as the backend for both SharePoint databases and Reporting Services (installed in Integrated mode). We are going to be using the database-attach method of upgrading our SharePoint farm.

Is there any specific guidance out there on exactly how to migrate/upgrade Reporting Services in this scenario? I've read through some of the MSDN content (How To: Migrate a Reporting Services Installation) but nothing seems to deal specifically with doing this when in Integrated mode with SharePoint. Our business heavily relies on SSRS reports in SharePoint and also shared and custom report subscriptions via email.

We do have a dev SharePoint 2010 farm in a similar configuration that I can test migration/upgrade steps. Thanks.

Share point upgrade from 2007 to 2010


Hi I am new to share point administration i have new project which is

1) Share point 2007 windows 2033 32 bit

2) SQL 2005 windows 2003 32 bit

3) Windows 2003 AD 32 bit 

i what to upgrade to new servers with windows 2008 64 bit which best option



MOSS 2007 to SharePoint 2010 Upgrade Fails - Object with Id 57bdacb5-31fe-4f4c-bdb3-3caf048474bd and


Ok apart from deleting these Classes and Objects what else can be done. Any one know a way around. Just to help you find them if you have a similar error look in the Classes and Objects Tables in the Offending database listed in the error message. In this error message below it is SharePoint_Config. How I found them,  yes its like looking for a needle in a hey stack see this post, very handly sql query.

I have a copy of a VM I can create again so I am going to try deleting these and if this works I will Answer my own post. This of course is unsupported and purely a hack hence why I am posting searching for enlightenment. Of course I have other errors so this may merely negate the first one.



[psconfigui] [SPConfigurationDatabaseSequence2] [INFO] [9/30/2010 3:44:42 PM]: SPConfigurationDatabase Name=SharePoint_Config
[psconfigui] [SPConfigurationDatabaseSequence2] [WARNING] [9/30/2010 3:44:42 PM]: Object with Id 57bdacb5-31fe-4f4c-bdb3-3caf048474bd and class id 92e1ba91-03dc-4d85-8978-8c6224d84d5e could not be deserialized. Most likely its type is no longer a sub class of SPPersistedObject.
[OWSTIMER] [UserProfileApplicationSequence] [INFO] [9/30/20

MOSS 2007 to SharePoint 2010 Upgrade Fails - Exception: The user or group 'wsaarole:wsaa administra


Ok the top part of the error I have tracked down to some entries in the SharePoint_Config database (Classes, Objects, TimerRunningJobs) and since I have a VM I am going to study them and try deleting them probably, if it dies I will delete this VM and roll up another VM in my case its a timer job that I am guessing the farm can live without.

The other error further down is more of a concern to me which is the one I listed above. The Group exists and it is in the farm and appears to be healthy no errors in preugrade check or the like or in the Farm. When upgrading the show stopper for me is that the content databases will not upgrade (assuming they upgrade FBA I can configure) the chicken and egg issue for me is this is an FBA farm, so is it the case that b/c FBA is missing not configured yet on the other side of the upgrade in 2010 that these content dbs connected to FBA (by FBA users in the content dbs) will upgrade affter FBA is configured ( I haven't tried this yet sorting my error log one error at a time). The Particular content dbs with an issue are shared services and the main site collection db which includes my sites site collections also.

[psconfigui] [SPConfigurationDatabaseSequence2] [INFO] [9/30/2010 3:44:42 PM]: SPConfigurationDatabase Name=SharePoint_Config
[psconfigui] [SPConfigurationDatabaseSequence2] [WARNING] [9/

Custom Content Types Missing after 2007 Upgrade to 2010


Hello everyone - 

We have a portal solution leveraging custom publishing content types and page layouts in 2007. The database was backed up, and the upgrade was done via dbattach on a 2010 environment. The site works seemingly fine - though there is some strange behavior we noticed where a few content types are missing.

The Content Type Gallery lists only say 10 of the 15 content types we should have. Loading the Master Page and Page Layout Gallery we see the inheriting content type, though clicking on it yields in an error as though it cannot find the content type. These are all custom content types, though they are not very different from each other.

Has anyone experienced this problem and devised a solution? - I tried to iterate through the site collection via a console application to see if I could somehow update or intercept the issue with the missing content types to no avail. I'll be open to suggestions / tools recommended...

All the best,


Alex Talarico

Upgrade 2007-2010 Database Attach


Hi all,

Having read many of the articles abot upgrading 2007-2010, I wanted to see if a simple approach would work.

  1. Ran the pre-upgrade checker
  2. Simply detached the DB in SQL (SQL Manager only), forcing the connections to close
  3. Copied the DB to the new server
  4. Re-attached the original DB to the 2007 server
  5. Attached the copied DB to the 2010 box
  6. Ran the shell command to attach to a web application
  • All seems to work

The content databases in question are quite simple and test units, and we are moving from the staging server to production, is this a valid approach?

Also, before I try wih a 'real' db, is there any harm done in detaching/re-attaching on the original 2007 server?




ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend