I have two User Profile Service Applications (UPSA) and two proxies. But since SharePoint doesn’t allow two proxies, I have to figure out which of the two proxies is the one that is working and which one creates the error 6398 in the Event Viewer every minute. I need to delete the proxy that shouldn’t be there.
It all started when I migrated the UPSA from a 2010 environment and I also needed a second UPSA (on a different app server) pointing to another Active Directory which doesn’t have ADFS between the production AD and the test AD. I don’t need to synchronize against the production AD, but I want the profiles still in my farm for reference in test. This setup is OK according to Spence Harbar.
In Central Admin it looks like the following:
I’m currently running a full sync against the test AD. It shows both on my new Manage Profile Service: UPSA page (from the 2013 UPSA)
... and in the Synchronization Service Manager (C:\Program Files\Microsoft Office Servers\15.0\Synchronization Service\UIShell\miisclient.exe)
In the timer job history, the incremental synchronization is failing, but I’m actually running a full sync now, so it may be working when the full sync has finished. The 2013 proxy incremental synchronization isn’t running at all – which may indicate that it isn’t in use.
I’ve managed to get the different proxies using these commands:
$saproxy2010 = Get-SPServiceApplicationProxy -Identity 86138300-a350-437b-b045-4f596ea08efb $saproxy2013 = Get-SPServiceApplicationProxy -Identity ae44bbc8-03cd-417c-8367-99892874a3e8
I also found the property
.IsSynchronizationRunning to run on my created instances. I’m guessing, but I’m not sure that it is actually the 2010 proxy that is running (since it’s the one created first) and not the 2013 proxy. Is this true or are there other ways I can check which proxy is running and which is failing?