Topology.svc Exception System.InvalidOperationException: The service implementation object was not initialized or is not available.
Ok so this time i will kept it short as much as possible . So i came across an issue where i was trying to publish MetadaServiceApplication and to be used in a different SharePoint Farm . It was working fine on some of the servers but on the rest of the servers i kept getting errors in the ULS logs of this type.
An exception occurred when calling SPTopologyWebServiceApplicationProxy.EnumerateSharedServiceApplications on service https://<<ServerName>>Topology/topology.svc : System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: The service implementation object was not initialized or is not available. (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: System.InvalidOperationException: The service implementation object was not initialized or is not available.
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)).
I added the necessary elements to debug the endpoint . But i didn't find much .
Once i restarted the Application Discovery and Load Balancer Service on the affected it worked like charm.
Get-SPServiceInstance -All | ?{$_.TypeName -eq "Application Discovery and Load Balancer Service"}| Select TypeName,Server,Status,ID
$Service= Get-SPServiceInstance -ID <<ID of the service>>
$Service.Stop()
$Service.Start()
For more details about this service please check the following blog :