I just completed an in place upgrade of SharePoint 2007 to SharePoint 2010. What a crazy experience! Just when you think the upgrade was successful, you run into lots of errors! It took me quite a few days to iron out all of the issues and spent countless hours searching the Internet to find solutions. Here are just a few of the issues that I ran into, in no particular order. Maybe this can be helpful for others.

Application Event log error: “Load control template file /_controltemplates/TaxonomyPicker.ascx failed”

• Solution: Rename the 14\templates\controltemplates\taxonomypicker.ascx file. It is no longer used and shouldn’t even be there.
• See: Help Wanted: Taxonomy Picker

SharePoint error: Some or all identity references could not be translated

• Don’t use an account name longer than 20 characters
  • See SharePoint 2010: Some or all identity references could not be translated
• Don’t delete an account without being sure it’s no longer in use somewhere in SharePoint
  • If you need to re-create an account run “stsadm –o migrateuser –oldlogin domain\serviceaccount –newlogin domain\serviceaccount -ignoresidhistory” in order to reconnect the account in SharePoint.
  • See Trying to access Configure Service Account in SharePoint 2010

Application Event log error: VSS error

Volume Shadow Copy Service error: Unexpected error calling routine RegOpenKeyExW(-2147483646,SYSTEM\CurrentControlSet\Services\VSS\Diag,…)

• Look at the details tab of the event and see which user account is failing. In my case it was my search service account. Give this user Full control on the SYSTEM\CurrentControlSet\Services\VSS registry key.
• See Unexpected Error has occurred when starting SharePoint Search Service
• Also Fixing the Volume Shadow Copy service

Application Event log warning: Windows cannot find the local profile

Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off.

• IIS 7+ seems to want your application pool accounts to have a user profile. You can resolve this by logging on locally with the application pool credentials once to create the profile, or follow these instructions: Give your Application Pool Accounts A Profile

Application Event log error: “Load control template file /_controltemplates/SearchArea.ascx failed”

• Same solution as the Taxonomy picker. It also shouldn’t be there.
• See: http://blogs.architectingconnectedsystems.com/blogs/cjg/archive/2010/05/08/Load-control-template-file-_2F005F00_controltemplates_2F00_SearchArea.ascx-failed.aspx

Open Question: Manage User Profiles Displays No Results

• Why doesn’t the Manage User Profiles feature list all of the user profiles? It forces you to search and there is no wildcard search option to display all profiles. Is this a bug?
• See Manage User Profiles Not Displaying Any Results in RTM (I’m not the only one asking this question!)

Site Directory not updated after upgrade

• The Site Directory has mostly been removed from SharePoint 2010. It is disabled on purpose, but it can be manually enabled. I would recommend removing the old site directory first.
• See: Activate Site Directory in Sharepoint Server 2010
• Also: Site Directory in SharePoint Server 2010

DCOM errors

• You will need to use Component Services/dcomcnfg to grant the Farm account local activation rights to 000C101C-0000-0000-C000-000000000046 (MSIServer)
• This is reminiscent of SharePoint 2007. See Fixing those pesky DCOM event log error 10016 in a SharePoint farm environment
• If you are running on Windows Server 2008 R2, you may need to modify registry permissions in order to change settings in Component Services. See: Fix the SharePoint DCOM 10016 error on Windows Server 2008 R2

Application Event log warning: Configure Object Cache Accounts

Object Cache: The super user account utilized by the cache is not configured. This can increase the number of cache misses, which causes the page requests to consume unneccesary system resources.

• You will see warnings in the application log about object cache super user and super reader accounts not being configured. You should create accounts just for this purpose (i.e. SPCacheSuperUser and SPCacheSuperReader). Follow these directions to configure: Configure object cache user accounts

User Profile Synchronization

• The User Profile Synchronization service in SharePoint 2010 is significantly more complex and complicated than SharePoint 2007. Behind the scenes it uses Forefront Identity Manager, but it is extremely finicky to configure and get working properly. Be sure to read as much as possible before attempting this configuration or you will find yourself re-doing it several times.
• The best guide to follow to set up the User Profile Synchronization service is Rational Guide to implementing SharePoint Server 2010 User Profile Synchronization. This guide also shows you the architecture diagram, giving you an idea of how complex the whole thing actually is.
• Key items:
  • Ensure you have granted the correct Active Directory permissions to your User Profile service account (i.e. Replicating Directory Changes, membership in Pre-Windows 2000 Compatible Access group)
  • Make sure your Farm service account is a local admin on the SharePoint server. This is required during provisioning so that local groups can be created, among other things.
  • If the first portion of your FQDN does NOT match your NetBIOS domain name, follow the directions in this blog post to turn on the NetBiosDomainNamesEnabled property: SharePoint 2010 – Provisioning User Profile Synchronization Search for “Permission requirements: Domain netbios name is different than the FQDN of the domain”
• See also Provisioning The User Profile Service Application
• See also SP 2010 cannot start user profile synchronization service

Missing components reported in SharePoint Health Analyzer

• Delete the site collection, application (and website), and content database that was used for the SharePoint 2007 shared service provider. This is no longer needed and it’s presence with old references to SharePoint 2007 web parts is causing this error.

Windows installer errors after setting up User Profile Synchronization

Detection of product ‘{90140000-104C-0000-1000-0000000FF1CE}’, feature ‘PeopleILM’, component ‘{1C12B6E6-898C-4D58-9774-AAAFBDFE273C}’ failed. The resource ‘C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe’ does not exist.

• Grant Network Service account Read & Execute permissions to the C:\Program Files\Microsoft Office Services\14.0\ directory
• See You have any problems with the FIM services and profile sync?

Configuring User Profile Synchronization Connections: “The query returns nothing”

• Log in as your service account to configure the connection and/or make sure the account is in the local admin group when doing the configuration.
• See Configuring new SharePoint 2010 beta Synchronization Connection returns “The query returns nothing.”

MOSS MA Not Found

• Make sure both the Forefront Identity Manager Service and ForeFront Identity Manager Synchronization Service are running. I ran into this error a few times after rebooting. Until I resolved all of the event log issues, the services were sometimes not starting correctly after a reboot.

“Unable to Process Create Message” when creating a User Profile Synchronization Connection

• Make sure to use the username format DOMAIN\Username
• SSL connections seem to cause this problem if you specify the correct port (636). Leave it alone on the default port or else it will fail.
• See SharePoint 2010 “Unable to process Create message” Error When Creating User Profile Synchronization Connection

People Search returns no results

• Double check that your crawl account has permissions to retrieve people data
• See: How to set up People Search in SharePoint 2010

I feel like I missed a few errors that I encountered, but this is a good list of common things that can be seen. I have a feeling in the coming weeks I’ll run into a few more.

Follow

Related posts: