FIM 2010 Password Synchronization Error 6025

I am running FIM 2010 to sync passwords between two forests. I think I have everything configured properly, Yet, I am still getting an 6025 error. I've read dozens of articles and forum posts on this error but nothing seems to work. I'll paste the full text of that error at the bottom. There is a two way Forest level trust. The FIM server is running in the target forest and PCNS is running in the source forest. The "Forefront Identity Manager Synchronization Service" is running under the AD account target\FIMSynchronization.

In the target forest AD domain functional and forest level is 2008. PCNS is not installed on any DC in the target forest. I used this setspn command:

setspn.exe -A PCNSCLNT/FIM2010.target.priv target\FIMSynchronization

Open in new window


In the source forest AD domain functional level is 2008 and the forest level is 2003. PCNS is installed on all AD servers. I used the following pcnscfg command which points to the FIM server in the target forest and uses a security group from the source forest:

pcnscfg ADDTARGET /N:FIM2010 /A:FIM2010.target.priv /S:PCNSCLNT:FIM2010.target.priv /FI:"source\PasswordSyncUsers-source" /f:3

Open in new window


In FIM2010 under Tools/Options password sync is enabled. On the AD_Source MA in "Configure Directory Partitions" the "Enable this partition as a password synchronization source" is checked and the target is set to AD_Target MA. On the AD_Target MA under "Configure Extensions" "Enable Password Management" is checked.

I have verified there are no duplicate PCNSCLNT SPNs in the target forest and there are no PCNSCLNT SPNs in the source forest.

I can ping the FIM server in the target forest from a DC in the source. DNS is configured properly on both sides.

In the source forest the pcnscfg -list command yeilds:

Targets
  Target Name...........: FIM2010
  Target GUID...........: B690C791-5C91-4885-A053-279015BF2206
  Server FQDN or Address: FIM2010.target.priv
  Service Principal Name: PCNSCLNT:fim2010.target.priv
  Authentication Service: Kerberos
  Inclusion Group Name..: source\PasswordSyncUsers-source
  Exclusion Group Name..:
  Keep Alive Interval...: 0 seconds
  User Name Format......: 3
  Queue Warning Level...: 0
  Queue Warning Interval: 30 minutes
  Disabled..............: False

Total targets: 1

On the FIM2010 server the command setspn -L target\fimsynchronization yeilds:

Registered ServicePrincipalNames for CN=FIM Synchronization,OU=FIM2010,OU=Service Accounts,DC=target,DC=priv:
        PCNSCLNT/fim2010.target.priv

From the source forest if I run setspn -l target.priv\fimsynchronization I get:

Registered ServicePrincipalNames for CN=FIM Synchronization,OU=FIM2010,OU=Service Accounts,DC=target,DC=priv:
        PCNSCLNT/fim2010.target.priv

If I run the same command but leave off the .priv from the domain as below, I get an ldap error.
setspn -l target\fimsynchronization
Ldap Error(0x51 -- Server Down): ldap_open

Applog Error: Event 6025, PCNSSVC

Password Change Notification Service received an RPC exception attempting to deliver a notification. 

The password change notification target could not be authenticated.

User Action:
This usually happens under the following conditions:
1. The Service Principal Name (SPN) for the target has not been assigned to the Active Directory account used to host the target process.
2. The SPN is assigned to more than one Active Directory account.
3. The SPN is not properly formatted. The SPN must use the fully qualified domain name of the target system.
4. There is more than 5 minutes of time variance between this system and the target system.

Please verify that the SPN configuration and that the clocks on the two systems are synchronized to an authoritative time source.

Additional Details:

Thread ID: 1924 
Tracking ID: fa091d02-cc5a-4de1-98a2-29053b30578b 
User GUID: 78f79eef-3b34-4e28-8010-97b3ee19c894 
User: HCESC\kelley.hccatest 
Target: FIM2010 
Delivery Attempts: 1239 
Queued Notifications: 2 
0x00000721 - A security package specific error occurred.
 
ProcessID is 3684
System Time is: 7/27/2014 21:26:42:740
Generating component is 2
Status is 1825 - A security package specific error occurred.
Detection location is 1710
Flags is 0
NumberOfParameters is 1
Long val: 0

ProcessID is 3684
System Time is: 7/27/2014 21:26:42:740
Generating component is 2
Status is 1825 - A security package specific error occurred.
Detection location is 1461
Flags is 0
NumberOfParameters is 0

ProcessID is 3684
System Time is: 7/27/2014 21:26:42:740
Generating component is 2
Status is 1825 - A security package specific error occurred.
Detection location is 141
Flags is 0
NumberOfParameters is 1
Long val: -2146893053

ProcessID is 3684
System Time is: 7/27/2014 21:26:42:740
Generating component is 3
Status is -2146893053 - The specified target is unknown or unreachable
Detection location is 140
Flags is 0
NumberOfParameters is 4
Long val: 16
Long val: 6
Unicode string: PCNSCLNT:fim2010.hccanet.priv
Long val: 68126

Open in new window

hccaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jamie McKillopIT ManagerCommented:
Hello,

You have an error in command to add the target.

pcnscfg ADDTARGET /N:FIM2010 /A:FIM2010.target.priv /S:PCNSCLNT:FIM2010.target.priv /FI:"source\PasswordSyncUsers-source" /f:3

should be:

pcnscfg ADDTARGET /N:FIM2010 /A:FIM2010.target.priv /S:PCNSCLNT/FIM2010.target.priv /FI:"source\PasswordSyncUsers-source" /f:3
                                 
                                 
-JJ
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
hccaAuthor Commented:
Jamie McKillop you are a Godsend! I'm so ashamed to have missed that detail. I also found that I had two targets configured in the source domain and once these two issues were resolved all password changes are now flowing. I wish I had more points to award!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Applications

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.