.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

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

Posted By:      Posted Date: September 11, 2010    Points: 0   Category :SharePoint
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

View Complete Post

More Related Resource Links

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

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?

Is there anyway to Sync SharePoint 2010 table to MOSS 2007 table?

Hello, I would like to know what can i use to sync a sharepoint 2010 table to a sharepoint 2007 table? Also could this be done by pulling the webservice for sharepoint 2007 site?

Migration from WSS 3.0 & MOSS 2007 to SharePoint 2010


Hi All,

I am kiran and working on some migration project.

I am stuck with some basic questions,


1. I have got couple of hudred WSS 3.0 sites

2. I have got couple of hundred MOSS 2007 Enterrprise sites

I need to migrate both the above to SharePoint Server 2010 platform.

My Question is,


1. Can I directly migrate WSS 3.0 sites to SharePoint 2010 env? Is there any need to step up to MOSS 2007 and then to SharePoint 2010? Becuase all documentations talk about migrating MOSS 2007 to SS 2010.

Your help is appreiciated.

Also can you link me to some sound help links please?






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/

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.



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?

Migrating from MOSS 2007 to SharePoint 2010

I am asked to give an approach and estimate to migrate 500+ sites from MOSS 2007 to SharePoint 2010. I am planning to use Hybrid approach of db attach and in-place. My challenge is estimating the time that will be taken for the upgrade. How do I create the estimate for the time taken to migrate, what factors do I consider?

How to make Custom SharePoint 2010 Webpart work on MOSS 2007 Environment



I've built a SharePoint WebPart in SharePoint 2010, using SharePoint Assembly version Now i've to make this Webpart such that i should work on SharePoint 2010 and MOSS 2007. The version no for both the versions are different, so do i need to create separate web-part for both version or is there any other way?

My current webpart is built in env, which has

SharePoint 2010, Windows 7 64 Bit, VS 2010.

Reference is added to SharePoint DLL which is in 14 Hive ISAPI.


How can i make this generic, so that i should work on both version, i've not used anything specific which is only in SP2010, its just a simple webpart.


Akhilesh Nirapure
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