Saturday, April 14, 2012 2:38 AM
My install is on a set of SP servers with the December 2011 CU installed.
I am unable to connect to the Topology service and so none of my service application proxies can connect. All trusts and permissions are marked appropriately (including in the App Discovery & Load Balancer service on the publishing farm). All services are published.
If I run the Receive-SPServiceApplicationConnectionInfo command on the consuming farm using the publishing farm topology URL, I get an ObjectNullReferenceException. However, I can navigate via browser to the topology service url (of course, I get the IE certificate invalid error, but that is expected).
I am unable to create a service proxy via the UI--I suppose this is because the topology service is used to determine what URI is used for what service application type. I am able to create the service proxy via powershell (I have to select the appropriate type to add the new proxy in advance, so, this makes sense).
So, if I could only figure out how to troubleshoot the topology service, I think I'd be in better territory.
Suman Chakrabarti [MSFT]
Tuesday, April 24, 2012 4:37 PM
I would enable logging on the farm to verbose and then follow the correlation ID in the ULS log. That should give a good starting point on where to go next.
Regards, Savoeurn Va Microsoft Online Community Support
Thursday, January 10, 2013 1:56 PM
We are facing more or less the same problem (Addresses for this application have not yet been fetched), trying to establish a federated search among two farms. Did you ever solve your problem? have you any hint/suggestion?
Thursday, January 17, 2013 4:44 PM
Execute the script from Spencer to resolve your problem: