Post New Web Links

In Place Upgrade from SharePoint 2007 to SharePoint 2010

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

I have a client that is trying to do an In place upgrade 2007 to 2010 and has received a failed report. Any suggestions?

[psconfigui] [SPConfigurationDatabaseSequence2] [INFO] [7/12/2010 1:27:17 PM]: SPConfigurationDatabase Name=SharePoint_Config
[psconfigui] [SPConfigurationDatabaseSequence2] [WARNING] [7/12/2010 1:27:17 PM]: Object with Id 72e2b269-2d72-4c93-bfc2-93682d55c361 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] [7/12/2010 1:27:23 PM]: SPConfigurationDatabase Name=SharePoint_Config
[psconfigui] [SPConfigurationDatabaseSequence2] [WARNING] [7/12/2010 1:27:23 PM]: Object with Id 7632ab71-7414-4b79-a305-2ad5cd3496d1 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] [7/12/2010 1:27:26 PM]: SPConfigurationDatabase Name=SharePoint_Config
[psconfigui] [SPConfigurationDatabaseSequence2] [WARNING] [7/12/2010 1:27:26 PM]: Object with Id 81793d13-fa7a-4d48-bf43-0457a79cd714 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] [SPConfi

View Complete Post

More Related Resource Links

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

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 in place upgrade "Cannot complete the action"

I currently did an inplace upgrade to SharePoint 2010 Standard in a medium farm deployment with one WFE and a remote SQL server with one site collection. The upgrade process was marked as finished in CA. The problem now is with the root site in the site collection is throwing the error "Cannot complete the action". I've narrowed it down to the "Pages" library in the the root site. The root site is using site template id = 20 template name = SPS#0, and template title = SharePoint Portal Server Site. If I hard code the URL in IE address bar I can get everywhere on the root site including the settings page of the "Pages" library. The error is thrown when I try to access the "Manage Permissions" link of the "Pages" library or when I try to browse to http://<rootsite>/pages/default.aspx. I believe the default.aspx page was customized by the customer when they were on SharePoint 2007 Standard.

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?

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!

SharePoint 2010 in-place upgrade fails

Hello,

I have tried the in-place upgrade in a test site and its fails. When I remove the SSP the upgrade was succesfull.

In the error log there is a backup device reference 'C:\DATA\slq_Backup\INT_SharedServices_DB_backup.dat'. This file is missing now. Maybe this is a previous config, but I can't remember it. In the SQL Server 2008 I have not found any backup device. We use third partly backup solution. I don't know where the corresponding backup file is configured.

Error log:

[psconfigui] [SPConfigurationDatabaseSequence2] [INFO] [2010.09.22. 12:12:55]: SPConfigurationDatabase Name=INT_ConfigDB
[psconfigui] [SPConfigurationDatabaseSequence2] [WARNING] [2010.09.22. 12:12:55]: Object with Id 3db7b513-5995-460e-8eee-c9e9bb67cc7f 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] [2010.09.22. 12:12:57]: SPConfigurationDatabase Name=INT_ConfigDB
[psconfigui] [SPConfigurationDatabaseSequence2] [WARNING] [2010.09.22. 12:12:57]: Object with Id a7966ae0-4cea-464e-8076-d0b44a9acd38 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] [IN

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?

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.

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.

http://soerennielsen.wordpress.com/2007/08/22/find-the-needle-in-the-sql-database/

[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

Hi,

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.

Thanks

Sandip

After SharePoint 2007 upgrade to SharePoint 2010 issue with custom site(s)

With our 2007 site(s) we had a custom module (we developed) to swap out the application.master with our own master page which resembled the site default.master. This worked great.

After the upgrade, out site's main pages looked fine however when navigating to the admin type pages (settings/viewlists etc.) pages the module stopped working.

1.) I have figured out something things with respect to what is going on but am still at a loss to how best resolve. We want the layouts/admin pages to have the same master page as the main user pages. I have read in 2010 this is now possible. How can I achieve this?

2.) Currently, when navigating to the sites/settings page the site is using template/layouts/layoutsv3.master as the master page. The settings.aspx page has DynamicMasterPageFile="~masterurl/default.master" . It was my understanding that when DynamicMasterPageFile was set to default.master it would use the master page from the site. So, with that said I am confused why it is using layoutsv3.master

any help would be appreciated

-dave
dave

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.

Thanks.

Will


Categories:

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