Этого мануала вполне достаточно для настройки и запуска службы синхронизации:
http://www.harbar.net/articles/sp2010ups.aspx
Если пробовали запускать службы синхронизации вручную, то лучше начинать с чистой установки Sharepoint.
И еще один нюанс есть. В статье той я не нашел этого. После того как все настроено, перед запуском службы синхронизации нужно будет сделать следующее, чтобы избежать некоторых ошибок с синхронизацией. К сожалению не нашел ссылку, поэтому процитирую здесь
Well it has been a while but this is now resolved. After working with Microsoft, we found
that the OWSTimer.exe service was crashing. All this came down to proxy issues. After running
netsh winhttp show proxy, i saw I had direct access. This however was not the case.
1. You need to create a owstimer.exe.config file with the following
<configuration>
<system.net>
<defaultProxy>
<bypasslist>
<add address="[a-z]+\.yourdomain\.com" />
<add address="192\.168\..*" /> Your internal IP Range
</bypasslist>
</defaultProxy>
</system.net>
</configuration>
This helped us get the User Profile Syncronisation Service running.
At this point the case was closed with Microsoft. But then i ran into an issue creating the
import connection "MOSS MA not found"
2. To resolve this you need to add the proxy bypass to the web.config file for the central
admin web application only the content between the <defaultProxy> tags. You should be able
to see this section in the file.
Now you will have the connection. Close but still not happy, syncing will run but with errors.
I was seeing hundred of event
6801 - FIMSynchronizationService
System.NullReferenceException: Object reference not set to an instance of an object. at
Microsoft.Office.Server.UserProfiles.ManagementAgent.ProfileImportExportExtension.Microsoft.
MetadirectoryServices.IMAExtensibleCallExport.ExportEntry(ModificationType modificationType,
String[] changedAttributes, CSEntry csentry) Forefront Identity Manager
and
6100 - FIMSynchronizationService
MOSS-f43f00de-4210-43b1-a3fe-e7403684bddb
MOSS_EXPORT_d752b66b-e7c7-447b-b782-c4bf69baee10
3. This was fixed by creating another config file.
MIISClient.exe.config in c:\Program Files\Microsoft Office Servers\14.0\Synchronization Service\UIShell
Add the same proxy settings as discussed previously.
We are now very close, but i was still getting errors during the export part of the process
4. One more config file
MIISServer.exe.config in c:\Program Files\Microsoft Office Servers\14.0\Synchronization Service\Bin
Same proxy bypass and done before.
Now i have a full sync running. An ordeal but hopefully this will help someone in the future.
Попробуйте в текущей ситуации, может поможет решить вашу проблему, но вообще говоря, мне кажется, что ваша ошибка из другой оперы. Если нет, при установке с нуля крайне рекомендую это делать. Избавляет от многих проблем.
Sharepoint 2010. User Profile Synchronization Service не стартует
Ваша проблема сохраняется?