User profile is not getting started after SP1 on sharepoint 2010 environment?

Question

We are neither able to start or reprovision the user profile application after installing the SP-1 on the sharepoint 2010 enterprise environment. Is it a known issue?

Answer 1

Reference:
http://myspexp.com/2011/04/28/user-profile-synchronization-servicehangs-on-starting-i-fixed-it/
http://www.sharepointblues.com/2010/07/09/provisioning-the-user-profile-service-application/
http://www.harbar.net/articles/sp2010ups2.aspx

Steps:

Stop the User Profile Synchronization Service
Reset the SyncDB.
Open IIS (inetmgr)
Click on the server name and select Authentication
Selected Anonymous Authentication then choose Edit
Click the specific user, then enter “IUSR”
Add the service account to Local Admin group on the server
Add the service account to all the FIM groups
add the service account to the WSS_WSP and WSS_Admin_WPG group
Perform an IISRESET
Reset SharePoint Timer & SharePoint Admin service
clear the MaData-folder
Ensure that "FIM_SynchronizationService" datarole is present on the sync DB.
Remove all of the FIM certificates are on the server.
Ensure that "Network service account" has full control on - C:\Program Files\Microsoft Office Servers\14.0 folder.
Start the User Profile Synchronization Service
Perform an IISRESET
Verify the C:\Program Files\Microsoft Office Servers\14.0\Synchronization Service\Bin\miiserver.exe.config file

Answer 2

I think it is a known side effect when installing June CU.

You can either uninstall .Net 4.0 or force FIM to use .Net Framework v2.0

It is explained here in detail:

http://blogs.technet.com/b/patrick_heyde/archive/2011/07/02/sharepoint-2010-junecu-2011-available-side-effect-info-amp-solution.aspx

Answer 3

http://sharepointinterface.com/2011/07/05/crashing-owstimer-exe-after-sharepoint-2010-sp1-installation/ I had this problem as well when I installed the service pack in my virtual environment. Although I was able to completely blow it away, I still get encryption errors now after installing the service pack and correcting the errors in this article. It is all related to the Forefront Identity Management services.