Sign in
 
HomeSharePoint Server 2010SharePoint Foundation 2010SharePoint OnlineLibraryForums
SharePoint Products > SharePoint 2010 Forums > SharePoint 2010 - Setup, Upgrade, Administration and Operation > Profile Sync Service wont start up again after restart of server

Locked Profile Sync Service wont start up again after restart of server

Locked

    •  
      Thursday, May 06, 2010 3:44 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I successfully provisioned the user profile service application and also the user profile sync service and sucessfully synced with AD, but upon rebooting my server (Dev Server) the User Profile Synchronization Service is in the stopped state and failed to start again. The Farm Account is in the local administrators group on the server as well.

      The error im getting the the trace log is:

      ILM Configuration: The miissku.exe process exited with error code -2146232060. Error: .

      ILM Configuration: The ValidateMiisEncryptionKey process returned False.

      UserProfileApplication.SynchronizeMIIS: Failed to configure MIIS pre database, will attempt during next rerun. Exception: System.Configuration.ConfigurationErrorsException: Exception of type 'System.Configuration.ConfigurationErrorsException' was thrown.

      at Microsoft.Office.Server.UserProfiles.Synchronization.ILMPostSetupConfiguration.ImportMiisEncryptionKey(String encryptionKeyFileName)

      at Microsoft.Office.Server.Administration.UserProfileApplication.RestoreMiisEncryptionKey(ILMPostSetupConfiguration psc)

      at Microsoft.Office.Server.Administration.UserProfileApplication.SetupSynchronizationService(ProfileSynchronizationServiceInstance profileSyncInstance).

      Ive even deleted the service application and reprovisioned it and it works great until the server is rebooted.

      Im at a dead end as to what this could be, but it seems alot of others are also having similar troubles with the User Profile Synchronization Service hoping someone has an idea and possible solution to this problem

      Thanks,

      Chris L

         

      Answers

      • Wednesday, June 09, 2010 4:41 PM
         
         Answered
        Sign In to Vote
        3
        Sign In to Vote

        I've been getting "ILM Configuration: The ValidateMiisEncryptionKey process returned False." type errors and tried multiple workarounds and checks, but the service still wouldn't run. So, as a last attempt I've traced the entire provisioning sequence with Process Monitor. Surprise! I've have a named instance for SharePoint db (e.g. server\sharepoint), but FIM was trying to connect to default instance!

        @#$%#!&#$.

        User profile server app is configured with correct database server name and databases were actually created correctly. So, used cliconfg to create an alias from default instance to named one (server -> server\share), provisioned again. Now it works :-\

        • Proposed As Answer by Romain KEIRSEBILCK Thursday, June 10, 2010 5:21 PM
        • Marked As Answer by Chrisls Thursday, June 10, 2010 7:48 PM
        •  
           

        All Replies

        • Sunday, May 09, 2010 9:40 PM
           
           
          Sign In to Vote
          0
          Sign In to Vote
          Anyone have an idea of what this could be?
             
          • Sunday, May 09, 2010 9:48 PM
            Moderator
             
             
            Sign In to Vote
            1
            Sign In to Vote

            A lot of people have had trouble with it, but not this kind of trouble.  I have gotten the UPS to work in all 4 builds of SP2010 with lots of pain, but I have never had an issue with it not working after a reboot.  Is your whole farm built on one server?  Which service is not started when you reboot?  Is it the UPS in System Settings > Services on Service or something else?  What is the state of your FIM services when you check the Services console of the Server Manager?

            SharePoint Architect || Microsoft MVP || My Blog
               
            • Sunday, May 09, 2010 10:10 PM
               
               
              Sign In to Vote
              0
              Sign In to Vote

              Its a two server setup with SQL Server 2008 R2 on one box and SharePoint on the other (Both are virtual machines running on VMware workstation). As for which services are started the User Profile Service is started on both the Services on Server page and under the services console in windows while the User Profile Synchronization Service is in the stopped state on both the Services on Server page and the services console. When I attempt to Start it thru the Services on Server page in SharePoint it errors out with error I indicated above

              Thanks for the help so far,

              Chris L

                 
              • Sunday, May 09, 2010 10:20 PM
                Moderator
                 
                 
                Sign In to Vote
                1
                Sign In to Vote
                What about the FIM services in the Services console?  Is everything else in your farm working?
                SharePoint Architect || Microsoft MVP || My Blog
                   
                • Thursday, May 20, 2010 4:42 PM
                   
                   
                  Sign In to Vote
                  0
                  Sign In to Vote

                  Hi,

                  Did you find find a way to solve this? I'm having the same issue :-(

                     
                  • Wednesday, May 26, 2010 8:40 PM
                     
                     
                    Sign In to Vote
                    0
                    Sign In to Vote

                    Having a similar issue, similar errors. We are able to set everything up, and it runs for a while (days), and then eventually the FIM service won't startup again. Usually after a server reboot.
                    At this point, the UPS connection is no longer showing up in the UI. Running MIISclient doesn't start up obviously. And clicking on "Start Profile Synchronization" renders a message: "Please wait for the current synchronization run to finish".
                    The only way we have gotten it to startup again is by re-configuring the sync service with a new user profile service application.
                    When we're having this behavior, and after attempting to start the user profile sync service under "Manage Services on Server", here's what we see in the logs:

                    -- end of 1 iteration

                    05/26/2010 14:42:48.23  High      ILM Configuration: The miissku.exe process exited with error code -2146232060. Error: . 80e870c3-647d-4bee-99b6-3c9475594ee7
                    05/26/2010 14:42:48.23  High      UserProfileApplication.SynchronizeMIIS: Failed to configure MIIS pre database, will attempt during next rerun. Exception: System.Configuration.ConfigurationErrorsException: Exception of type 'System.Configuration.ConfigurationErrorsException' was thrown.     at Microsoft.Office.Server.UserProfiles.Synchronization.ILMPostSetupConfiguration.ImportMiisEncryptionKey(String encryptionKeyFileName)     at Microsoft.Office.Server.Administration.UserProfileApplication.RestoreMiisEncryptionKey(ILMPostSetupConfiguration psc)     at Microsoft.Office.Server.Administration.UserProfileApplication.SetupSynchronizationService(ProfileSynchronizationServiceInstance profileSyncInstance).  80e870c3-647d-4bee-99b6-3c9475594ee7
                    05/26/2010 14:42:48.25  Medium    UserProfileApplication.SynchronizeMIIS: End setup for 'User Profile Service Application 2'. 80e870c3-647d-4bee-99b6-3c9475594ee7

                    -- start of a new iteration attempt

                    05/26/2010 14:43:16.49  Medium    UserProfileApplication.SynchronizeMIIS: Begin setup for 'User Profile Service Application 2'. 609cf33d-a841-44ac-9ee3-44a7898e9df6

                    05/26/2010 14:43:32.14  High      ILM Configuration: The miissku.exe process exited with error code -2146232060. Error: . 609cf33d-a841-44ac-9ee3-44a7898e9df6
                    05/26/2010 14:43:32.14  High      ILM Configuration: The ValidateMiisEncryptionKey process returned False.  609cf33d-a841-44ac-9ee3-44a7898e9df6
                    05/26/2010 14:43:32.14  High      Synchronization database is already initialized. Importing the encryption key for the database into the registry  609cf33d-a841-44ac-9ee3-44a7898e9df6


                    05/26/2010 14:43:47.72  High      ILM Configuration: The miissku.exe process exited with error code -2146232060. Error: . 609cf33d-a841-44ac-9ee3-44a7898e9df6
                    05/26/2010 14:43:47.72  High      UserProfileApplication.SynchronizeMIIS: Failed to configure MIIS pre database, will attempt during next rerun. Exception: System.Configuration.ConfigurationErrorsException: Exception of type 'System.Configuration.ConfigurationErrorsException' was thrown.     at Microsoft.Office.Server.UserProfiles.Synchronization.ILMPostSetupConfiguration.ImportMiisEncryptionKey(String encryptionKeyFileName)     at Microsoft.Office.Server.Administration.UserProfileApplication.RestoreMiisEncryptionKey(ILMPostSetupConfiguration psc)     at Microsoft.Office.Server.Administration.UserProfileApplication.SetupSynchronizationService(ProfileSynchronizationServiceInstance profileSyncInstance).  609cf33d-a841-44ac-9ee3-44a7898e9df6
                    05/26/2010 14:43:47.72  Medium    UserProfileApplication.SynchronizeMIIS: End setup for 'User Profile Service Application 2'. 609cf33d-a841-44ac-9ee3-44a7898e9df6

                    -- eventually, too many retries

                    05/26/2010 14:44:00.51  Unexpected  Maximum number of retries done for starting FIM SpService. Please look at ULS logs and event viewer to look for the root cause of the failure.  b291ce96-e74b-4e21-86fc-8641a0a7984c

                    -- service stops

                    05/26/2010 14:44:16.61  Medium    Unprovisioning service instance User Profile Synchronization Service. 2cb78f25-6b30-45a7-a3f3-52bc6977755a

                    Any ideas?

                    mc
                       
                    • Thursday, May 27, 2010 4:05 AM
                       
                       
                      Sign In to Vote
                      0
                      Sign In to Vote

                      Exactly the the same errors and in my case it also runs fine for a few days and then stops working which is usually after a server restart. Have rebuilt the server twice and the same issue keeps coming up.

                         
                      • Thursday, May 27, 2010 10:56 AM
                         
                         
                        Sign In to Vote
                        0
                        Sign In to Vote
                        I have the same error on windows 7, my sharepoint 2010 version is RTM. Does anyone have solution about it? 
                           
                        • Wednesday, June 09, 2010 4:41 PM
                           
                           Answered
                          Sign In to Vote
                          3
                          Sign In to Vote

                          I've been getting "ILM Configuration: The ValidateMiisEncryptionKey process returned False." type errors and tried multiple workarounds and checks, but the service still wouldn't run. So, as a last attempt I've traced the entire provisioning sequence with Process Monitor. Surprise! I've have a named instance for SharePoint db (e.g. server\sharepoint), but FIM was trying to connect to default instance!

                          @#$%#!&#$.

                          User profile server app is configured with correct database server name and databases were actually created correctly. So, used cliconfg to create an alias from default instance to named one (server -> server\share), provisioned again. Now it works :-\

                          • Proposed As Answer by Romain KEIRSEBILCK Thursday, June 10, 2010 5:21 PM
                          • Marked As Answer by Chrisls Thursday, June 10, 2010 7:48 PM
                          •  
                             
                          • Thursday, June 10, 2010 5:21 PM
                             
                             
                            Sign In to Vote
                            0
                            Sign In to Vote

                            Great WorkAround !!

                            It worked for me. While waiting for a patch from microsoft, I wrote a post on our blog: http://www.sosp.fr/blog/Lists/Billets/Post.aspx?ID=33

                            Hope it will help.

                            Romain K

                             

                               
                            • Thursday, June 10, 2010 7:48 PM
                               
                               
                              Sign In to Vote
                              0
                              Sign In to Vote

                              Wow great work, thanks for the info, this one was really bugging me.

                              Chris L

                                 
                              • Tuesday, June 22, 2010 4:28 PM
                                 
                                 
                                Sign In to Vote
                                0
                                Sign In to Vote
                                Thanks a ton for doing the research on this. This workaround really saves the day.
                                mc
                                   
                                • Tuesday, August 03, 2010 3:33 AM
                                   
                                   
                                  Sign In to Vote
                                  0
                                  Sign In to Vote

                                  Registry Key:
                                  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\FIMSynchronizationService\Parameters\SQLInstance

                                  There's a hotfix now.
                                  http://support.microsoft.com/kb/983497

                                  http://support.microsoft.com/kb/2281364