Solved

Post MOSS 2007 to SP2010 In-Place Upgrade Questions

Posted on 2010-09-07
4
1,096 Views
Last Modified: 2012-05-10
Greetings!

I recently did an upgrade on my MOSS 2007 server farm to SharePoint 2010, and have a question.  I don't claim to understand everything that is going on within SP2010, because it looks very different than what I'm used to (MOSS 2007), but here goes:

I ran the required software checker tool to make sure that I had all of the required software, patches, hotfixes, and service packs for my server farm.  The first thing that failed was that my SQL server was out of date, so I applied the service pack and the farm installation went fine.

So I installed SP2010 on my Application server and Web Front End server.  I set the farm password on the Application server, and chose to do an in-place upgrade and keep the sites the way they were (not to visually change them to SP2010 styles, I guess).  

After the installation was complete, I went to the Upgrade Status page in Central Administration, waited, and it said that the upgrade had failed.  I checked the log, and there were a lot of errors stating that the image library for the site was not found...which is odd, because there IS an images library in the sites in question.

I haven't found anything on google about this...I'm not sure if it's just me, or (more likely) I'm searching with the wrong terms...

The thing that gets me, is that I added my Web Front End server to the farm, and it listed that server as "Upgrade Successful".  

So under "manager servers in farm", SQL server and WFE server are green (finished), but the Application server says "Upgrade Needed".

Are there any post-installation procedures to accomplish other than starting services, etc, that would have this continue to say "Upgrade Needed" on the server that is running Central Administration in the farm?

Thanks, I appreciate any help!
0
Comment
Question by:ThatSharepointGuy
  • 3
4 Comments
 
LVL 15

Expert Comment

by:sharepointguru14
ID: 33628680
What was the actual error that you received? What parts on the application server failed? Many of the components of the application server have changed drastically (such as there is no Shared Service Provider anymore)

Post some more info of the actual error received and where in the upgrade process it failed. Logs with the errors would be great.
0
 
LVL 6

Author Comment

by:ThatSharepointGuy
ID: 33647570
We've done a reinstall, and while I don't have as many errors as before, I still have a few.  here they are:


[OWSTIMER] [BdcO14SharedResourceProvider12Sequence] [ERROR] [9/10/2010 8:36:22 AM]: Action 14.0.4.0 of Microsoft.Office.Server.ApplicationRegistry.Upgrade.BdcO14SharedResourceProvider12Sequence failed.
[OWSTIMER] [BdcO14SharedResourceProvider12Sequence] [ERROR] [9/10/2010 8:36:22 AM]: Exception: The topology service is not available in the farm.
[OWSTIMER] [BdcO14SharedResourceProvider12Sequence] [ERROR] [9/10/2010 8:36:22 AM]:    at Microsoft.SharePoint.SPTopologyWebServiceApplication.GetDynamicUri()
   at Microsoft.SharePoint.SPTopologyWebServiceApplication.get_Uri()
   at Microsoft.SharePoint.Administration.SPLoadBalancedUri..ctor(SPServiceApplication serviceApplication, String serviceEndpointName)
   at Microsoft.SharePoint.Administration.SPIisWebServiceApplication.get_Uri()
   at Microsoft.SharePoint.BusinessData.SharedService.BdcService.CreateProxy(String name, SPServiceApplication serviceApplication, SPServiceProvisioningContext provisioningContext)
   at Microsoft.Office.Server.ApplicationRegistry.Upgrade.CreateSharedServiceApplicationProxy.Upgrade()
   at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()
[OWSTIMER] [CreateSharedServiceApplicationProxy (14.0.4.0)] [DEBUG] [9/10/2010 8:36:22 AM]: Begin Rollback()
[OWSTIMER] [CreateSharedServiceApplicationProxy (14.0.4.0)] [DEBUG] [9/10/2010 8:36:22 AM]: End Rollback()
[OWSTIMER] [CreateSharedServiceApplicationProxy (14.0.4.0)] [DEBUG] [9/10/2010 8:36:22 AM]: Begin Dispose()
[OWSTIMER] [CreateSharedServiceApplicationProxy (14.0.4.0)] [DEBUG] [9/10/2010 8:36:22 AM]: End Dispose()
[OWSTIMER] [CreateSharedServiceApplicationProxy (14.0.4.0)] [DEBUG] [9/10/2010 8:36:22 AM]: SQL Query Count=18
[OWSTIMER] [CreateSharedServiceApplicationProxy (14.0.4.0)] [DEBUG] [9/10/2010 8:36:22 AM]: SPRequest Objects=1
[OWSTIMER] [CreateSharedServiceApplicationProxy (14.0.4.0)] [DEBUG] [9/10/2010 8:36:22 AM]: Execution Time=183.710778883908
[OWSTIMER] [SPUpgradeSession] [ERROR] [9/10/2010 8:36:22 AM]: Upgrade [SharedResourceProvider12 Name=SSP_Dev] failed.
[OWSTIMER] [SPUpgradeSession] [ERROR] [9/10/2010 8:36:22 AM]: Inner Exception: The topology service is not available in the farm.
[OWSTIMER] [SPUpgradeSession] [ERROR] [9/10/2010 8:36:22 AM]:    at Microsoft.SharePoint.SPTopologyWebServiceApplication.GetDynamicUri()
   at Microsoft.SharePoint.SPTopologyWebServiceApplication.get_Uri()
   at Microsoft.SharePoint.Administration.SPLoadBalancedUri..ctor(SPServiceApplication serviceApplication, String serviceEndpointName)
   at Microsoft.SharePoint.Administration.SPIisWebServiceApplication.get_Uri()
   at Microsoft.SharePoint.BusinessData.SharedService.BdcService.CreateProxy(String name, SPServiceApplication serviceApplication, SPServiceProvisioningContext provisioningContext)
   at Microsoft.Office.Server.ApplicationRegistry.Upgrade.CreateSharedServiceApplicationProxy.Upgrade()
   at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()
[OWSTIMER] [SPUpgradeSession] [ERROR] [9/10/2010 8:36:22 AM]: Exception: Action 14.0.4.0 of Microsoft.Office.Server.ApplicationRegistry.Upgrade.BdcO14SharedResourceProvider12Sequence failed.
[OWSTIMER] [SPUpgradeSession] [ERROR] [9/10/2010 8:36:22 AM]:    at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
[OWSTIMER] [SPUpgradeSession] [DEBUG] [9/10/2010 8:36:22 AM]: Elapsed time upgrading [SharedResourceProvider12 Name=SSP_Dev]: 00:00:00.
[OWSTIMER] [SPManager] [INFO] [9/10/2010 8:36:22 AM]: Resetting the status of PersistedUpgradableObject: SharedResourceProvider12 Name=SSP_Dev to Online.
[OWSTIMER] [SPUpgradeSession] [ERROR] [9/10/2010 8:36:22 AM]: Upgrade Timer job is exiting due to exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 14.0.4.0 of Microsoft.Office.Server.ApplicationRegistry.Upgrade.BdcO14SharedResourceProvider12Sequence failed. ---> Microsoft.SharePoint.SPException: The topology service is not available in the farm.
   at Microsoft.SharePoint.SPTopologyWebServiceApplication.GetDynamicUri()
   at Microsoft.SharePoint.SPTopologyWebServiceApplication.get_Uri()
   at Microsoft.SharePoint.Administration.SPLoadBalancedUri..ctor(SPServiceApplication serviceApplication, String serviceEndpointName)
   at Microsoft.SharePoint.Administration.SPIisWebServiceApplication.get_Uri()
   at Microsoft.SharePoint.BusinessData.SharedService.BdcService.CreateProxy(String name, SPServiceApplication serviceApplication, SPServiceProvisioningContext provisioningContext)
   at Microsoft.Office.Server.ApplicationRegistry.Upgrade.CreateSharedServiceApplicationProxy.Upgrade()
   at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()
   --- End of inner exception stack trace ---
   at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Administration.SPUpgradeJobDefinition.Execute(Guid targetInstanceId)






0
 
LVL 6

Author Comment

by:ThatSharepointGuy
ID: 33647578
[OWSTIMER] [SPUpgradeSession] [INFO] [9/10/2010 8:36:22 AM]: ======================================================================================
[OWSTIMER] [SPUpgradeSession] [INFO] [9/10/2010 8:36:22 AM]: Upgrade session failed. 3 errors and 0 warnings encountered.
[OWSTIMER] [SPUpgradeSession] [INFO] [9/10/2010 8:36:22 AM]: Look for possible causes for upgrade issues by searching [ERROR] and [WARNING] strings in the upgrade log file. Refer to "http://go.microsoft.com/fwlink/?LinkId=157732" for more information about how to recover from upgrade failures.
[OWSTIMER] [SPUpgradeSession] [INFO] [9/10/2010 8:36:22 AM]: ======================================================================================
[OWSTIMER] [SPUpgradeSession] [DEBUG] [9/10/2010 8:36:22 AM]: Stop the session maintenance thread.
[OWSTIMER] [SPUpgradeSession] [DEBUG] [9/10/2010 8:36:35 AM]: Setting upgrade session object to offline in configuration database
[OWSTIMER] [SPUpgradeSession] [DEBUG] [9/10/2010 8:36:35 AM]: UPGRADE PERCENTAGE: 100.00000000% done, Total Elapsed Time 00:03:02.9091822.
[OWSTIMER] [SPUpgradeSession] [DEBUG] [9/10/2010 8:36:36 AM]: Releasing upgrade lock from configuration database


0
 
LVL 6

Accepted Solution

by:
ThatSharepointGuy earned 0 total points
ID: 33692903
I figured out what the error was.  The upgrade was failing due to a bad site collection (it had features turned on that weren't native to the template that it was using).
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Possible fixes for Windows 7 and Windows Server 2008 updating problem. Solutions mentioned are from Microsoft themselves. I started a case with them from our Microsoft Silver Partner option to open a case and get direct support from Microsoft. If s…
A safe way to clean winsxs folder from your windows server 2008 R2 editions
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

808 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question