.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

MOSS Upgrade

Posted By:      Posted Date: September 29, 2010    Points: 0   Category :SharePoint
 I have project server sitting on MOSS 2007 on a standalone server, which do I upgrade first? Can anyone point me to the upgrade steps?

View Complete Post

More Related Resource Links

What are the Steps Installing Infopath Form Service on WSS 3.0 or do I need to upgrade to MOSS?

I  have configured Extranet Https Portal for our configuration.It includes some custom web-parts features in the site. My WSS 3.0 -Cenrtal Admin version is I have MOSS 2007 - Central Version Now I have designed a Infoapth form and want to publish to a library in the site.We can publish the form to a library but At client side Infopath 2007 sholud be installed in order to submit the form.It is not Browser Enabled. ( You cannot enable InfoPath Forms Services in WSS, because it is not present in WSS. Before you can enable InfoPath Forms Services, you have to install Forms Server or MOSS Enterprise.  It is not Browser enabled.  ) Infopath form services is a component of MOSS not WSS Is there any other way instead of intalling Moss 2007 can I only Install Infoapth Form services on it. Can I upgrade the WSS 3.0 to MOSS 2007 and get the Infoapth form services to the existing site without any loss of data.   I have read that while upgrading wss to moss the central admin version  should be same then only you can upgrade is this true?? what steps I need to consider ?? Guide me Thanks in Advance Harish

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?

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?

Upgrade List from MOSS 2007 to SP2010

Hi, I have a list in MOSS2007 and I want to save it as a template to use it in SharePoint 2010. But, the problem we can't use stp file in SP2010. So, did you have idea about creating wsp package in 2007 for existing List ? I have seen this article but it talk about Discussion List Feature. Thanks 

upgrade standard to enterprise MOSS 2007

When installed MOSS 2007, we provided the key for standard edition. Now we have to Install and configure Excel Calculation Services and full features in MOSS 2007. it is possible? If not support for standard edition how can we upgrade enterprise edition. we have a Enterprise key also.

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?

Failed upgrade from wss 3.0 to moss 2007. Cannot open database "ProjectServer-live_Published" reques


While trying to upgrade from WSS 3.0 to MOSS 2007 the process finished, but it stated that it completed with errors. Those errors seem to be causing problems within the Central Administration site. I will try outline the errors the best I can from the upgrade.log file and with the actions I've been attempting. THANK YOU in advance for any and all assistance.

[SharedResourceProviderSequence] [ERROR] [9/23/2010 11:15:03 AM]: Unable to locate SearchDatabase for the SharedResourceProvider Hyperion_SSP
[SharedResourceProviderSequence] [ERROR] [9/23/2010 11:15:03 AM]: Exception thrown was: System.ArgumentNullException: Value cannot be null.
Parameter name: No search database is associated with the search shared application, Hyperion_SSP
   at Microsoft.Office.Server.Search.Upgrade.SharedResourceProviderSequence.get_SearchDatabase()
   at Microsoft.Office.Server.Search.Upgrade.SharedResourceProviderSequence.AddNextLevelObjects()
[SharedResourceProviderSequence] [INFO] [9/23/2010 11:15:03 AM]: Re-run upgrade using stsadm -o upgrade to ensure the search database gets upgraded appropriately
[SharedResourceProviderSequence] [DEBUG] [9/23/2010 11:15:03 AM]: No search database was found, so skip upgrading it

As advised in the info section for this error I re-ran the upgrade

MOSS 2007 - 64-bit SP2 Upgrade Breaks Central Administration and doesn't complete


I am setting up a test Intranet Farm for a production Intranet. Everything is being installed on one server. SQL 2005 enterprise 64-bit edition is being used and has been upgraded to SP3. MOSS 2007 with SP1 64-bit edition was used to installed SharePoint and the central administration website installs successfully. I then downloaded WSS 3 SP2 64-bit edition and carried out the installation. As it is a Windows 2008 server with SP2, I use the 'run as administrator', just in-case, even though I am logged on as a local administrator.

The SharePoint Configuration wizard is run post-installation and access to the Central admin website is still available. I am restoring the Farm config for the production Intranet to this test Farm using the in-built backup feature of MOSS 2007 and I am using the GUI. As the production farm has MOSS 2007 SP2, I need to also install that update. I download the MOSS 2007 64-bit update and towards the end of the installation (prior to the configuration wizard appearing) an error occurs stating that the Installation of the Package failed, which appears in a prompt box and a box appears in front with regards to whether a report should be sent.

Central admin then has a 'this page cannot be displayed'.


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/

SP2010 inplace upgrade - leaves MOSS 2007 installed


Is it right that MOSS 2007 would remain installed in the Add/Remove programs listing after an in-place upgrade to SharePoint 2010?

I think this is causing issues with my ability to run a command to enable DPM to backup my farm.  (../dpm/bin/configuresharepoint.exe -EnableSharePointProtection)

MOSS 2007 SP 2 upgrade error


Following installation of WSS3 and MOSS2007 SP2 upgrade and during the PSCONFIG tool, at step 8 of 9, I get the below.

Failed to start service SPSearchServiceInstance on this server after completing upgrade. Please start it manual

The search service is set to disabled, so I change it to automatic and the service starts straight away. I let the the PSCONFIG tool sit there and a couple of minutes later, it makes it till the end and states that it failed to upgrade SharePoint Products and Technologies. I have restarted the server and re-run the psconfig. It runs through ok but still reports that it failed to upgrade.

I have another WFE that isn't servicing clients but has the web applications and search role on it, which doesn't currently have the SP2 binaries. Could that be causing the problem?

I get the below section in the upgrade log.

[SPManager] [DEBUG] [10/6/2010 8:44:17 AM]: [Microsoft.SharePoint.Administration.SPIisWebSite] Running 1 of 8 steps
[SPManager] [DEBUG] [10/6/2010 8:44:17 AM]: SPUpgradeJobDefinition progress update event: SPIisWebSiteWssSequence Upgrade Job 12% 1/8
[SPManager] [DEBUG] [10/6/2010 8:44:17 AM]: TotalTime 00:04:44.8593750, RefreshTime00:00:01.2656250
[EnsureRegKeysAndGroup] [] [DEBUG] [10/6/2010 8:44:17 AM]: Begin Initialize()
[EnsureRegKeysAndGroup] [] [DEBUG] [10/6/2010 8:4

Upgrade MOSS 2007 Application to MOSS 2010



i am working in MOSS 2007. Now we are planning to upgrade my applications to MOSS 2010. How to move SSP (user profile properties) in MOSS 2007 to MOSS 2010? becasue in SP2 , there is no SSP.

Could you please explain the steps to upgrade?


Please help me?









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.



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