0

2 Server Environment:

SharePoint 2013 On Server 2008 R2
SQL 2008 R2

AD is 2 domain servers - primary and secondary - Server 2003 w/ 2003 AD Functional Level

SharePoint User Profile service is configured and I can get the Synchronization service started so I am not "stuck on starting". Also, I have verified with AD tools that I can connect to the AD servers and that All replicate dir permissions are set correctly according to Spence Harbar's setup "Bible" :-)

When I try to run a Full Sync via the SharePoint user profile import (the SP2010 way) I get the following error on the DS_FULLIMPORT step in FIM

The replication operation encountered a database error / error code 8451

When I run the AD Import I get the following Error in the SharePoint ULS logs:

ScanDirSyncChanges: Exception thrown by Dirsync request: page 0, LdapServer 'xxx.xxx.dom, rootDn 'DC=XXX,DC=dom', exception 'System.DirectoryServices.Protocols.DirectoryOperationException: The server cannot handle directory requests.

I can find almost nothing on this anywhere. There was a .Net 2.0 hotfix for the 2nd error but that has been applied in a service pack already.

Help. I have built and rebuilt the User Profile Service multiple time with the same results. I'm at a loss.

1

According to Spence Harbar in his post: http://www.harbar.net/articles/sp2010ups.aspx

If our Domain Controller is running Windows 2003 or earlier functional level we also need to make the DOMAIN\spups account a member of the Pre Windows 2000 Compatible access built in group

Did you do this?

  • Yes the User Profile account is in this group – Chris Jones Jun 13 '14 at 16:05
  • Did you perform the necessary security changed to the containers in AD? – Matthew McDermott Jun 14 '14 at 8:55
  • Yes. Everything is configured EXACTLY per the Harbar UPS 'bible' :-) – Chris Jones Jul 9 '14 at 12:13
  • OK, is it a multiserver environment? Are you configuring the service on the correct server and no other? – Matthew McDermott Jul 9 '14 at 15:37
0

According to the information you give,especially Error Code 8451, this error is more related to Active Directory rather SharePoint Sync.

did you check this technet and try to fix this.

http://technet.microsoft.com/en-us/library/replication-error-8451-the-replication-operation-encountered-a-database-error(v=ws.10).aspx

or this KB.

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

  • Yes. I went through both of these posts before I posted my question. The AD server replicates successfully and syncs with a dozen other applications (not SP2013) – Chris Jones May 16 '14 at 19:23
  • Also, The AD guys ran DCDIAG and all passed so I don't think it is AD. In any case the solutions offered in the above articles are a bit nuclear in that if the syncs are working every where else, why would you rebuild AD for Sharepoint – Chris Jones May 16 '14 at 19:43
  • what level on AD you give the replicate permission to sync account? – Waqas Sarwar MVP May 16 '14 at 20:09
  • The User Profile Account was temporarily given Domain Admin rights so that any and all permissions issues would be eliminated. However, the account was set up initially EXACTLY per Spence's article. That is always my go to reference when setting up the UPS. – Chris Jones Jun 13 '14 at 16:09
  • did that fix the problem? – Waqas Sarwar MVP Jun 13 '14 at 16:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.