MSDN has been updated on the 12-Dec-2009 with some guidance close to what is documented below in text
There are further here on the SharePoint blog as there are issues with following least priviledge install e.g. having separate Active Directory Domain User Accounts for each role in farm. To get as far as I did I used Active Directory Domain Administrator user account for everything. Full credit goes to @givenscj for his help getting through this!
There are some IE8 bugs in the current UI...so push F12
Click "Browser Mode: IE8 Compat View" and select "Internet Explorer 7".
Click "start" on "User Profile Synchronization Service"
Click "OK"
Click on "monitoring" on left hand side and then click on "Review Job Definitions"
Click on "Running Jobs" on left hand side
You should now see ProfileSynchronizationSetupJob running
Keep refreshing until it disappears and then you'll notice it'll disappear. Click on "Job History" on left hand side, you should see the job with status of Successful.
In Windows Services you should now see Forefront Services both started and running under your administrator account.
Click on "Application Management" then click on "Manage service applications"
Scroll down and click on "User Profile Service Application"
Click on "Configure Synchronization Connections"
NOTE: you may see the below error, if you do simply do an IISRESET
Click Create New Connection
Fill in details
Click "Populate Containers" button then expand tree and select "Users" OU tree node and then click "OK".
NOTE: Clicking "Select All" does not work in this build!
You should now see a connection in this list.
NOTE: if you get to next screen and nothing shows, please ensure both Forefront Windows Services are started.
Go back to "User Profile Service Application" page from "Manage Service Applications"
Click "Start Profile Synchronization"
Select "Start Full Synchronization" then click "OK".
NOTE: this will take a few minutes as a job is scheduled to do this.
Now if you click "Manage User Profiles" you'll see the User Profiles coming through
In Beta 2 it is normal to see these warning errors in the Event Log.
Also note that you cannot edit the connections because of a JavaScript error.
For more information on the User Profile imports go to:
C:\Program Files\Microsoft Office Servers\14.0\Synchronization Service\UIShell\ and run MSIISClient.exe
If you get this error:
"Cannot navigate to the requested page while User Profile Synchronization is running. Please wait for the current Sychronization run to finish."
You will need to restart the machine (you can most likely just restart the services too)
If you face the error as shown in last screenshot "Cannot navigate to the reques...
If you face the error as shown in last screenshot "Cannot navigate to the requested page while User Profile Synchronization is running. Please wait for the current Sychronization run to finish", you don't need to restart machine. Wait for sometime, most probably the job still running. It will disappear itself.
You need to go and make sure the ForeFront Identity Management Service is starte...
You need to go and make sure the ForeFront Identity Management Service is started in Windows Services. On a reboot of my VMs it isn't even though it is set to Automatic That seems to fix it.
You should not be doing that manually as it's started by SharePoint when you sta...
You should not be doing that manually as it's started by SharePoint when you start from services section in CA and I guess this info is stored in DB and registry also. So if you do it manually, then it might get out of sync. I will try to do it on a very clean install if things not working. I am sure by RTM, they will make it very stable.
In my case I was not able to start the "Forefront Identity Manager Synchronizati...
In my case I was not able to start the "Forefront Identity Manager Synchronization Service" service with the local admin account. I had to use the AD SQL account I used and add it to the Enterprise admins group. When I "Create New Connection" no errors but it nevers shows on the list, instead I use MSIISClient.exe.
I finally managed to get my profile synchronization working, combining the infor...
I finally managed to get my profile synchronization working, combining the information in this guide with a few others.
I ran the User Profile Service as the Sharepoint Farm account, and gave this account local admin on the web frontend as well as the "Replicating Directory Changes" permission on my domain. However, it still did not work and the synchronization service got stuck on starting in CA as always.
So, I went home for the day and made the tough decision to come back the next morning and run everyting as a domin admin. I really hate to do that, but I figured trying to fix the synchronization issue the real way was not worth the time spent.
But lo and behold! When I cam back to my desk at 9am the synchronization service was running. Judging by the created timestamp of the folders in 14.0\Synchronization Service\MaData the service kicked off at 06.15, a full 12 hours after I told it to start!
Interestingly, I whole bunch of errors popped up in my event log at around that time.
06:11: Asp.NetError 1334, System.Security.CryptographicException, KeySet does not exist
06:11: CRITICAL, Failure to synch web application <GUID>, ContentDB <GUID>, No User Profile Application available to servie the request
06:12: FIMSynchronizationService information 6201, The server encryption keys have been successfully created
06:12: FIMSynchronizationService informaiton 2001, The Service was started successfully
06:14: 2x Microsoft.ReousrceManagement.ServiceHealthSource Error 22, The forefront identity manager cannot connect to the SQL Server database + long description
06:14: Microsoft.Resource management Service, service was started successfully
After this, new types of errors started to appear, but now the service was not stuck at starting anymore and I could go on to actually configure the synchronization data source.
After having a closer look at the 14\logs - files, I found that the trigger that...
After having a closer look at the 14\logs - files, I found that the trigger that started the synch service provisioning was a Timer Job Recycle. It is scheduled at 6AM every day. So maybe I would have been equally lucky if I waited for 10 minutes and then ran the "Timer Service Recycle" job manually from Central Admin - Job Definitions.
I'm not gonna gamble and recreate the synch service again just to find out. But if anyone is still out of luck getting the service to start - leave your laptop running over the night. You never know...
I manually ran the "Timer Service Recyle" job as hinted at by Markus above and w...
I manually ran the "Timer Service Recyle" job as hinted at by Markus above and was able to clear the "Cannot navigate to the requested page while User Profile Synchronization is running. Please wait for the current Sychronization run to finish" error. Its scheduled to run daily but can be run under Central Administration->Monitoring option "Check Job Status". On the left choose "Scheduled Jobs and find "Timer Service Recycle" in the list, click it, and click "run now" at the bottom.
Comments (11)
Nov 22
Anonymous says:
If you face the error as shown in last screenshot "Cannot navigate to the reques...If you face the error as shown in last screenshot "Cannot navigate to the requested page while User Profile Synchronization is running. Please wait for the current Sychronization run to finish", you don't need to restart machine. Wait for sometime, most probably the job still running. It will disappear itself.
Dec 02
Anonymous says:
I personally am still getting this message after 12 hours of wait and a server r...I personally am still getting this message after 12 hours of wait and a server restart any idea or do I need to just wipe and rebuild?
Error
"Cannot navigate to the requested page while User Profile Synchronization is running. Please wait for the current Sychronization run to finish"
Nov 22
Anonymous says:
Issue with Synchronisation of users. AD connection seems to work so I can selec...Issue with Synchronisation of users.
AD connection seems to work so I can select to user bin and all components within.
Click on OK and the result is "The query returns nothing"
Any thoughts?
@adrian_edgar
Nov 23
Jeremy Thake says:
You need to go and make sure the ForeFront Identity Management Service is starte...You need to go and make sure the ForeFront Identity Management Service is started in Windows Services. On a reboot of my VMs it isn't even though it is set to Automatic
That seems to fix it.
Nov 23
Anonymous says:
You should not be doing that manually as it's started by SharePoint when you sta...You should not be doing that manually as it's started by SharePoint when you start from services section in CA and I guess this info is stored in DB and registry also. So if you do it manually, then it might get out of sync. I will try to do it on a very clean install if things not working. I am sure by RTM, they will make it very stable.
@Tajeshwar
Dec 07
Anonymous says:
creative recreation shoes cheaply!creative recreation
shoes cheaply!
Nov 23
Jeremy Thake says:
There is also more information around User Profiles on TechNet although I would ...There is also more information around User Profiles on TechNet
although I would recommend following the above to the letter.
Nov 23
eddy mitchell blanco says:
In my case I was not able to start the "Forefront Identity Manager Synchronizati...In my case I was not able to start the "Forefront Identity Manager Synchronization Service" service with the local admin account. I had to use the AD SQL account I used and add it to the Enterprise admins group. When I "Create New Connection" no errors but it nevers shows on the list, instead I use MSIISClient.exe.
Nov 27
Markus Larsson says:
I finally managed to get my profile synchronization working, combining the infor...I finally managed to get my profile synchronization working, combining the information in this guide with a few others.
I ran the User Profile Service as the Sharepoint Farm account, and gave this account local admin on the web frontend as well as the "Replicating Directory Changes" permission on my domain. However, it still did not work and the synchronization service got stuck on starting in CA as always.
So, I went home for the day and made the tough decision to come back the next morning and run everyting as a domin admin. I really hate to do that, but I figured trying to fix the synchronization issue the real way was not worth the time spent.
But lo and behold! When I cam back to my desk at 9am the synchronization service was running. Judging by the created timestamp of the folders in 14.0\Synchronization Service\MaData the service kicked off at 06.15, a full 12 hours after I told it to start!
Interestingly, I whole bunch of errors popped up in my event log at around that time.
06:11: Asp.NetError 1334, System.Security.CryptographicException, KeySet does not exist
06:11: CRITICAL, Failure to synch web application <GUID>, ContentDB <GUID>, No User Profile Application available to servie the request
06:12: FIMSynchronizationService information 6201, The server encryption keys have been successfully created
06:12: FIMSynchronizationService informaiton 2001, The Service was started successfully
06:14: 2x Microsoft.ReousrceManagement.ServiceHealthSource Error 22, The forefront identity manager cannot connect to the SQL Server database + long description
06:14: Microsoft.Resource management Service, service was started successfully
After this, new types of errors started to appear, but now the service was not stuck at starting anymore and I could go on to actually configure the synchronization data source.
Nov 27
Markus Larsson says:
After having a closer look at the 14\logs - files, I found that the trigger that...After having a closer look at the 14\logs - files, I found that the trigger that started the synch service provisioning was a Timer Job Recycle. It is scheduled at 6AM every day. So maybe I would have been equally lucky if I waited for 10 minutes and then ran the "Timer Service Recycle" job manually from Central Admin - Job Definitions.
I'm not gonna gamble and recreate the synch service again just to find out. But if anyone is still out of luck getting the service to start - leave your laptop running over the night. You never know...
Dec 09
Anonymous says:
I manually ran the "Timer Service Recyle" job as hinted at by Markus above and w...I manually ran the "Timer Service Recyle" job as hinted at by Markus above and was able to clear the "Cannot navigate to the requested page while User Profile Synchronization is running. Please wait for the current Sychronization run to finish" error. Its scheduled to run daily but can be run under Central Administration->Monitoring option "Check Job Status". On the left choose "Scheduled Jobs and find "Timer Service Recycle" in the list, click it, and click "run now" at the bottom.