Hi,

I was recently performing some simple DRP tests before going to production and i faced some issues i never encountered before..

(followed http://blogs.msdn.com/b/besidethepoint/archive/2011/02/19/how-i-learned-to-stop-worrying-and-love-the-sharepoint-topology-service.aspx for usefull commands related to enpoints)

My farm:

SP 2013 - CU August 2013

2 WFE (WFE1, WFE2)

2 App (App1, App2) : Most services started on both servers (UPSS on APP1, UPS on both) - Central Admin on Both.

SQL Cluster

At normal state the command : (Get-SPTopologyServiceApplicationProxy).ApplicationProxies | Format-List *

returns > ServiceEndpointUri : https://app1:32844/Topology/topology.svc

(if i'm not wrong, this topology.svc can run on only one server at a time)

I stopped WFE1, no pb, the NBL (appliance) is doing the job.

Then I stopped the App1 and started to have some issues. (most enpoints not balanced to app2)

I run the job "Application Addresses Refresh Job"

Or launch PS command : Start-SPTimerJob job-spconnectedserviceapplication-addressesrefresh

Wait 20 sec.

A few endpoints are now on APP2 (MMS, Search), it seems to work, i reached my web page.

I ask a mate to try and he got the "sorry we encountered and error..." > Can't load user profile.

I refreshed my browser and got the same error.......

ULS review, I can see that some svc request (most about user, profiledbcacheService) are still on APP1 !!

A failure was reported when trying to invoke a service application: EndpointFailure Process Name: w3wp Process ID: 6784 AppDomain Name: /LM/W3SVC/93617642/ROOT-1-130445830237578923 AppDomain ID: 2 Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:e8315f8e5d7d4b1b90876e3b0043a4ae#authority=urn:uuid:164efb17f28c4d2d9702ce3e86f0c0e8&authority=https://app1:32844/Topology/topology.svc Active Endpoints: 1 Failed Endpoints:1 Affected Endpoint: http://app1:32843/e8315f8e5d7d4b1b90876e3b0043a4ae/ProfileService.svc

The command (Get-SPTopologyServiceApplicationProxy).ApplicationProxies | Format-List *

Still return me that my topology.svc is on https://app1:32844/Topology/topology.svc

But App1 is down !!

If my understanding is ok: Normally, the internal round robin loadbalancer (Application Discovery and Load Balancer Service, started on all servers, not configurable) should manage this.

Application Addresses Refresh Job is running each 15 min. and refreshs available endpoints, using the topology.svc

But, the topology.svc called is always on APP1 which is down !

At this time, i haven't found why SharePoint is not detecting that APP1 is down and is not automatically recreating a topology service on another available server.....

If you have any idea...your help is welcome :)

Regards,

O.P

• Edited by O.P Lux Thursday, May 15, 2014 3:21 PM

http://blogs.msdn.com/b/besidethepoint/archive/2011/02/19/how-i-learned-to-stop-worrying-and-love-the-sharepoint-topology-service.aspx