.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

Upgrade from MOSS 2007 to SharePoint Server 2010 but with a catch...

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

... and the catch is that the MOSS 2007 Site Collection is contained in the SharePoint Central Administration v3 Web Application and therefore the SharePoint_AdminContent_... database which is used by Central Administration (not my doing btw).  Please let me know how to copy it to a new 2010 server farm and then upgrade just our sites and content while removing all of the 2007 Central Administration stuff.



View Complete Post

More Related Resource Links

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?

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?

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  

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?

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/

Upgrade/Migrate MOSS 2007 Wiki to SharePoint 2010 Enterprise Wiki


We've been running MOSS 2007 for a few years now and have built up a Wiki.


I am now investigating the migration to SharePoint 2010, I've used the database attach method to copy across our Intranet site collection to a development SharePoint 2010 install (this includes our Wiki).


This works except for an error under the "Recent Changes" heading and the new 2010 Enterprise Wiki features are not available.


What I'm trying to find out is if there is a way to either upgrade the Wiki sub-site or migrate the Wiki data into a new 2010 Wiki sub-site that I can swap for the live one.


I've tried to just copy the items from the "Wiki Pages" list of the imported sub-site to the "Pages" list of a new 2010 Wiki sub-site, but they then just appear as "ASP.Net pages" and don't display the Wiki content.

I've also tried a couple of the commercial migration tools but these also just seem to copy the aspx files and leave them not viewable.


Thanks in advance


In place upgrade from Moss 2007 to SharePoint 2010


Having successfully run through stsadm -o preupgradecheck without having any issues highlighted to me, I believed I was now in a position to upgrade my Development Farm (single server Farm)......WRONG! From blogging, I have seen others suffer the same fate as me, has anyone got any advice/fixes for the following error log:


[psconfigui] [SPConfigurationDatabaseSequence2] [INFO] [8/4/2010 12:29:23 PM]: SPConfigurationDatabase Name=SP2010_SharePoint_Config
[psconfigui] [SPConfigurationDatabaseSequence2] [WARNING] [8/4/2010 12:29:23 PM]: Object with Id 873adcc7-97b6-4f40-a2d6-25e7ab360a53 and class id 92e1ba91-03dc-4d85-8978-8c6224d84d5e could not be deserialized. Most likely its type is no longer a sub class of SPPersistedObject.
[psconfigui] [SPConfigurationDatabaseSequence2] [INFO] [8/4/2010 12:29:26 PM]: SPConfigurationDatabase Name=SP2010_SharePoint_Config
[psconfigui] [SPConfigurationDatabaseSequence2] [WARNING] [8/4/2010 12:29:26 PM]: Object with Id 524b79a8-8e70-4066-9975-2a94617dda64 and class id 92e1ba91-03dc-4d85-8978-8c6224d84d5e could not be deserialized. Most likely its type is no longer a sub class of SPPersistedObject.
[psconfigui] [SPConfigurationDatabaseSequence2] [INFO] [8/4/2010 12:29:51 PM]: SPConfigurationDatabase Name=SP2010_SharePoint_Config
[psconfigui] [SPConfigurationDatabaseSequence2] [WARNING] [8/4/201

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?

HTTP Error 500.19 - Internal Server Error after SharePoint 2010 In-place upgrade

Hello We have done an SharePoint 2010 In-Place Upgrade. After the upgrade, we can access the Central Administration page without problems. However, when accessing the standard http port 80 site, the following error appears: Error Summary HTTP Error 500.19 - Internal Server Error The requested page cannot be accessed because the related configuration data for the page is invalid.   <fieldset><legend>Detailed Error Information</legend> Module IIS Web Core Notification Unknown Handler Not yet determined Error Code 0x80070032 Config Error The configuration section 'system.web.extensions' cannot be read because it is missing a section declaration Config File \\?\C:\inetpub\wwwroot\wss\VirtualDirectories\80\web.config Requested URL http://coolsharepoint:80/ Physical Path   Logon Method Not yet determined Logon User Not yet determined </fieldset> <fieldset><legend>Config Source</legend> 534: </location> 535: <system.web.extensions> 536: <scripting> </fieldset>

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 ?

SharePoint 2010 Server: Cannot manage all user profiles from upgraded MOSS SSP database

I have upgraded an SSP database to SharePoint 2010 and successfully performed User Profile Synchronization with Active Directory, however I cannot manage ALL of the user profiles in the database. I go to "Manage User Profiles" in Central Administration and perform a filtered search (i.e. I want all DOMAIN accounts beginning with "j" so I search for "DOMAIN\j" in Manage User Profiles), but I don't receive ALL the user profiles back. I receive about 8 in return when I know there are about 20 starting with "j". If I create a new AD account beginning with "j" it is successfully synched with SharePoint 2010 and I see it in the Manage User Profiles. I ran an stsadm -o sync to clear any old synchronization information, and the Forefront Synchronization Service appeared to pull in many changes to existing accounts (including ones I can't currently manage), but I still cannot manage them using "Manage User Profiles". I really need to be able to manage all the profiles so I can manually edit some fields. Can anyone please help? Thanks in advance.

how to Upgrade MOSS 2007 to MOSS 2010 ?

how to Upgrade MOSS 2007 to MOSS 2010

Best Way to Convert MOSS 2007 Site Templates to SharePoint 2010 Templates

Ok, I just treid to do something that I didn't really think would work, but now that I've seen it fail, I get to ask the question. Is there a best practice on converting site templates built for MOSS 2007 to SharePoint 2010. We have several projects that used the Visual Studio Extensions (v1.3) and the SharePoint Solution Generator to build custom site templates and the .wsp packages. I can add and deploy the solution packages using the STSADM tool, but when I try to create a sub-site based on that template, I get an Object Not Set to an Oject Reference Error. In case anyone is wondering, it works fine in MOSS 2007. I have not tried Visual Studio 2010 yet (it's downloading in the background). I'm just wondering if anyone has run into this and what they did to fix it. TIA, John.

Reg deployment of solution packages in SharePoint 2010 from MOSS 2007

Hi, Earlier we have developed some custom web parts,features and deployed into the site through solution package(wsp files) when customer was using MOSS 2007.Now customer is migrating all sites into SharePoint 2010.Now my query is can i use the same solution to deploy into the site through Central Admin of SharePoint 2010 or is there any seperate process for that? Thanks & Regards, Sudheer

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

Can we have both moss 2007 and sharepoint 2010 using a share SQL cluster?

Hello, I want to consolidate some server by using both SharePoint 2007 and SharePoint 2010 to use the same SQL 2008 R2 cluster. Is there any technical reason that should prevent to have both application to share same SQL server using different sql DB? Thanks
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