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

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

Upgrade/Migrate MOSS 2007 Wiki to SharePoint 2010 Enterprise Wiki

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

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


View Complete Post

More Related Resource Links

Migrate Wiki from SharePoint 2007 to SharePoint 2010

I have a Wiki in SharePoint 2007 that I need to migrate to SharePoint 2010.  I cannot do an in-place upgrade of the 2007 site.  What are your recommendations on how to approach this migration?

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?

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?

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/

SharePoint Wiki pages non editable after in place upgrade to SharePoint 2010



We recently upgraded SharePoint 2007 SP2 farm to SharePoint 2010 farm uisng in-place upgrade. The upgrade was successful execept the Wiki pages library pages showing unusal behavior. 

All the content in Wiki pages library under the SP 2007 site were upgraded to Wiki pages library under the same site after upgrade to SP 2010. But the WIKI tool bar is not showing the Edit button on Wiki pages and hence the Wiki content is non editable. 

We did not receive any error or informtaional message in the pre-upgradecheck on prior to upgrade.

I would highly appreciate if some could help get the issue resolved.



Easy way to migrate site columns and content types from moss 2007 to sharepoint 2010?

Easy way to migrate site columns and content types from moss 2007 to sharepoint 2010?

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


... 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.



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?

Sharepoint 2010 Enterprise Wiki - TOC, Table of Content - Displaying only headers for individual pag


I am currently trying to build a wiki for our users in Sharepoint 2010, but there is one particular item I just can't get right. The table of content...

I am aware of the web part TOC, but this one can't be configured to display headers for an individual page only. Instead it insist on displaying all my navigation links, for all my sites, which is quite unnecessary since they are already displayed in the navigation pane to the left.

Is there a way to create a TOC as you see on any other normal wiki page, so it would end up looking similar to my example below?

[SITE Header Example]

1. Header

1.1 Subject 1

1.2 Subject 2


2. Header 2

2.1 Subject 3 and so on...


Then the TOC should be placed in top and look similar to this.


1. Header

1.1 Subject 1

1.2 Subject 2

2. Header 2

2.1 Subject 3


Can this be done, or would it require any 3rd party plugins?

I'm a bit baffled that the build in web part isn't more configurable, since I would have guessed that MS actually would have looked at other wiki pages to see how it is done, before adding their own templates? But maybe I am missing the obvious

Sharepoint 2007 - Wiki site - New Pages Not Inheriting Custom Master Page


I am working on a SP site (MOSS not WSS) which is heavily customised away from the OOTB layout. I need to create a Wiki site, which was going well - I've created a master page which displays the miniconsole (this was not visible with our customised layout), and made it the default master page for the site. This has been applied to the two standard pages that come with the Wiki site, however when a new page is created, it seems to inherit the default.master, rather than my custom master page - thus not showing the miniconsole.

When I have created a new page, I am able to use SharePoint Designer to attach my custom master page to it, which works perfectly, however this will not be a viable option going forward as end-users create their new wiki pages.

How can I get the new pages to inherit my master page when they are created?


RSS and Wiki SharePoint 2010

Does anyone know if SharePoint 2010 has an out-of-the-box option to subscribe RSS feeds on Wiki pages???

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 ?

Show wiki page library columns on wiki pages- SharePoint 2010

I created a wiki page library in SharePoint 2010 and added a few columns to the library. However, these columns do not show on the actual wiki pages as they did in SharePoint 2007. I looked through the library settings but didn't find anything to turn on this feature. Does anyone know how to do this or if this feature was even included in SharePoint 2010? 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