none
Load Balancer Error Mesaage

    Question

  • Hi

    I get the following error message in my Application Event Log as below:

    SharePoint Web Services Round Robin Service Load Balancer Event: EndpointFailure

    Process Name: w3wp

    Process ID: 5264

    AppDomain Name: /LM/W3SVC/1510665082/ROOT-1-129396986725543693

    AppDomain ID: 2

    Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:b647394194e047f7ac1efc35a282787c#authority=urn:uuid:aa9be2365d7d46f0bfee23ae7152e0f8&authority=https://spapp01:32844/Topology/topology.svc

    Active Endpoints: 1

    Failed Endpoints:1

    Affected Endpoint: http://spweb01:37843/b647394194e047f7ac1efc35a282787c/MetadataWebService.svc

    It looks like someone has enabled a Load Balancer on our Front-End-Server.

    Thanks for any feedback ;-)

     

    Michael

    Monday, January 17, 2011 2:39 AM

Answers

  • This is related to the internal SharePoint topology service, which channels service application requests to their correct location. if you have more than one server on which that "SharePoint Service" is running (in your case Managed Metadata), the topology service will round-robin the requests.

    In normal circumstances you shouldn't see that problem. SharePoint thinks that the end point is valid, and obviously it is gone.

    You can fix this by stopping and starting the "Managed Metadata Web Service" "SharePoint Service" in Central Administration. Look for this: http://sharepointgeorge.com/wp-content/uploads/2010/05/image57.png (borrowed from http://sharepointgeorge.com/2010/configuring-managed-metadata-service-application-sharepoint-2010-part1/)

    This will recreate the endpoint in IIS, and remind SharePoint that the machine is answering to that service. Do it on all machines in the farm

    Hope this helps!


    SharePoint 2010 MCM. Feel free to contact me http://www.sharepoint.bg/radi
    Friday, January 21, 2011 4:36 PM
  • That's the internal round robin service looking for a service application endpoint on a service machine instance.  I'm guessing at some point you must have enabled a service application on more than 1 server and possibly removed it or not configured it correctly, and 2010 is trying to resolve the end point (the service on a server) - which is not there any more or is simply unreachable perhaps due to running as an account with the wrong permissions.

    Would be good to trace the root cause an resolution though - that'd be fun!

    Spencer Harbar explains some of the complexities around service apps in this really nice posting that might help you understand how to start tracing the error:

    http://www.harbar.net/articles/sp2010sa2.aspx

     

     


    Regards John Timney http://www.johntimney.com
    Friday, January 21, 2011 2:18 PM

All replies

  • Hi - Having the same problem here as well. Getting frequent 8313 errors, followed by 8314 information messages when the endpoint recovers. No other errors are present and the servers are all online during the period in question. No network errors are present; all servers are on the same VLAN and switch.

    I do not recall configuring any Load Balancing services.

    Marc

     

    Tuesday, January 18, 2011 7:05 PM
  • Hi!

    The same error on my multiserver Farm SharePoint 2010 Enterprise any suggestions for us?

     

    Mario Z.

     

    Friday, January 21, 2011 1:19 PM
  • That's the internal round robin service looking for a service application endpoint on a service machine instance.  I'm guessing at some point you must have enabled a service application on more than 1 server and possibly removed it or not configured it correctly, and 2010 is trying to resolve the end point (the service on a server) - which is not there any more or is simply unreachable perhaps due to running as an account with the wrong permissions.

    Would be good to trace the root cause an resolution though - that'd be fun!

    Spencer Harbar explains some of the complexities around service apps in this really nice posting that might help you understand how to start tracing the error:

    http://www.harbar.net/articles/sp2010sa2.aspx

     

     


    Regards John Timney http://www.johntimney.com
    Friday, January 21, 2011 2:18 PM
  • This is related to the internal SharePoint topology service, which channels service application requests to their correct location. if you have more than one server on which that "SharePoint Service" is running (in your case Managed Metadata), the topology service will round-robin the requests.

    In normal circumstances you shouldn't see that problem. SharePoint thinks that the end point is valid, and obviously it is gone.

    You can fix this by stopping and starting the "Managed Metadata Web Service" "SharePoint Service" in Central Administration. Look for this: http://sharepointgeorge.com/wp-content/uploads/2010/05/image57.png (borrowed from http://sharepointgeorge.com/2010/configuring-managed-metadata-service-application-sharepoint-2010-part1/)

    This will recreate the endpoint in IIS, and remind SharePoint that the machine is answering to that service. Do it on all machines in the farm

    Hope this helps!


    SharePoint 2010 MCM. Feel free to contact me http://www.sharepoint.bg/radi
    Friday, January 21, 2011 4:36 PM
  • Thanks Radi - Testing your solution now - will reply with results.

     

    Marc

     

    Sunday, January 23, 2011 3:03 AM
  • Hi Marc,

    Have you already any results?

    Leon


    Kind regards, Leon
    Thursday, January 27, 2011 7:40 AM
  • Hi - no luck I am afraid - restarting the Managed Metadata service did not fix the problem - nor did deleting the Service Application and recreating it. Error in trace logs at the time of the failure:

    Exception returned from back end service. System.ServiceModel.Security.MessageSecurityException: An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail. ---> System.ServiceModel.FaultException: ID3242: The security token could not be authenticated or authorized.     --- End of inner exception stack trace ---

    It is only the managed metadata service that is failing in this manner. Other services that are on multiple servers that participate in the round-robin service are not affected.

     

    Saturday, January 29, 2011 5:29 PM
  • I have started noticing the same error in my test farm, but for the Search Service. It is a multiserver farm with two front end servers. There is actually a second error that logs in the search results too everytime I try to search. Here are the two errors:

    Error 1:

    SharePoint Web Services Round Robin Service Load Balancer Event: EndpointFailure
    Process Name: w3wp
    Process ID: 1576
    AppDomain Name: /LM/W3SVC/1837669832/ROOT-1-129412318724925517
    AppDomain ID: 2
    Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:e590f7f4f762477cb2042e180fbf4c28#authority=urn:uuid:dba2ecc91f184b0a99207f37e078b524&authority=https://wfe1sharepoint:32844/Topology/topology.svc
    Active Endpoints: 2
    Failed Endpoints:1
    Affected Endpoint:
    http://wfe2sharepoint:32843/e590f7f4f762477cb2042e180fbf4c28/SearchService.svc


    Error 2:

    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (74999c55-6447-46b5-adea-a51506eea107).

    Reason: There is no project Portal_Content mounted under gatherer application 29a56323-60cd-496b-8ea5-89e6f36e5899.

    Technical Support Details:
    System.InvalidOperationException: There is no project Portal_Content mounted under gatherer application 29a56323-60cd-496b-8ea5-89e6f36e5899.
       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
       at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

    The problem is in only the Search Service. I deleted the service and recreated it but just like Marc, it did not help. The search was fine before and has worked. I performed three steps on the farm and perhaps one of them caused the error: I installed the December CU, I successfully configured the User Profile Service, I succesfully deployed Office Web Apps. Web apps and UPS both are working fine


    I want to believe
    Friday, February 04, 2011 2:01 PM
  • I tried out the proposed action, with stopping and starting the "managed metadata service", but im still getting the error.
    Any other ideas?

    Friday, February 11, 2011 12:07 PM
  • Were all of these farms a result of upgrades from MOSS, or are they brand new, or some of each? 
    Saturday, February 12, 2011 2:33 PM
  • Mine was a new farm. The error stops if I stop the metadata on one of the two servers hosting the service. Not ideal. MS Premier support is looking into the issue - possibly a problem with WCF.

     

    Sunday, February 13, 2011 2:02 AM
  • Monday, February 14, 2011 5:07 PM
  • Changing the policy and rebooting as described in the post above did NOT solve the issue.

     

    Tuesday, February 15, 2011 12:47 AM
  • What CU are you running on your farm?
    Thursday, February 17, 2011 8:35 PM
  • December CU
    Sunday, February 20, 2011 5:16 PM
  • I'm seeing this EndPoint problem also! I'm running the December CU also on a multi-server farm  2 WFE and 2 APP servers. 

    Getting this daily on the Meta Data Service on random servers.  The MetaData Service is running only on both APP servers.  Any news or resolution from Microsoft.  The December CU is turning out to have several more issues than normal!

    I'm getting the following:

          SharePoint Web Services Round Robin Service Load Balancer Event: EndpointFailure Process Name: OWSTIMER Process ID: 3560 AppDomain Name: DefaultDomain AppDomain ID: 1 Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:92d304085d774b4f9947e7758fbe8537#authority=urn:uuid:dd7be8bbb91a43f099446d8214b7327f&authority=https://twsvl-shpapp-01:32844/Topology/topology.svc Active Endpoints: 1 Failed Endpoints:1 Affected Endpoint: http://twsvl-shpapp-01:32843/92d304085d774b4f9947e7758fbe8537/MetadataWebService.svc

    Sunday, February 27, 2011 6:56 AM
  • Anyone having this problem not running December CU? Kerr-Avon any luck with Microsoft Support in finding a solution for the problem?

     


    I want to believe
    Monday, February 28, 2011 5:30 PM
  • Hi,

    I have the same problem. My configuration : 2 FE, 2 APP + 1 SQL Cluster. Windows Server 2008 R2. SP 2010 Enterprise + CU Dec 2010.

    SharePoint Web Services Round Robin Service Load Balancer Event: EndpointFailure
    Process Name: w3wp
    Process ID: 5364
    AppDomain Name: /LM/W3SVC/1732060096/ROOT-1-129440240695673648
    AppDomain ID: 2
    Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:b3270a4337c14b02aeefc5b225401213#authority=urn:uuid:451a4e437bb94cc98e754d399be0605b&authority=https://server1:32844/Topology/topology.svc
    Active Endpoints: 1
    Failed Endpoints:1
    Affected Endpoint: http://server2:32843/b3270a4337c14b02aeefc5b225401213/MetadataWebService.svc

    The web service is available in the 2 servers when launch in web browser

    Did you check the firewall : is the port 32843 opened ? It is my case.

     


    Pierre Vivier-Merle - MVP SharePoint Server - http://blogs.developpeur.org/pierre
    Tuesday, March 08, 2011 1:51 PM
  • Yeh Firewall port is not the problem in my case as well. It appears everyone having this problem has the December CU applied. I did not have this problem before I applied the December CU.
    I want to believe
    Tuesday, March 08, 2011 8:13 PM
  • I've been trying to build a brand new 2-server farm I was using SP2010 Enterprise with Dec 10 slipstreamed in. I'm getting the error too. I've tried all the things in this thread and I'm still having problems. It's not firewall. Stoping/Starting services hasn't worked. Reboots hasn't worked. 

    Has anyone tried to install the Feb11 CU and does that fix it?

    Wednesday, March 09, 2011 12:42 PM
  • Same error.  Dec CU installed on farm.  I just rebuilt UPA last night and that did not alleviate the issue.
    James Grizzle
    ---
    http://www.linkedin.com/in/jamesgrizzle
    Wednesday, March 16, 2011 2:40 PM
  • We have the same error too. December CU installed. Does anyone know if the february CU solves this error?

    Friday, March 18, 2011 10:24 AM
  • I had the same issue and I installed the February CU this week. Guess What?

    problem solved, no entries in the Application Event log saying:

    SharePoint Web Services Round Robin Service Load Balancer Event: EndpointFailure
    Process Name: w3wp
    Process ID: 5364
    AppDomain Name: /LM/W3SVC/1732060096/ROOT-1-129440240695673648
    AppDomain ID: 2
    Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:b3270a4337c14b02aeefc5b225401213#authority=urn:uuid:451a4e437bb94cc98e754d399be0605b&authority=https://server1:32844/Topology/topology.svc
    Active Endpoints: 1
    Failed Endpoints:1
    Affected Endpoint: http://server2:32843/b3270a4337c14b02aeefc5b225401213/MetadataWebService.svc


    R. van Maurik
    Thursday, March 24, 2011 4:44 PM
  • I have just seen this error after installing the December 2010 CU on my farm.

    I had two app servers running the Managed Metadata Service and two Front End servers. Only one of the Front End servers was getting the 8313 error.

    After taking the advice on here, I restarted the Managed Metadata service on both app servers and performed an IISReset on the Front End server with the error. I have not installed the Feb CU so not sure if this will resolve it too.

    This seems to have resolved it now.

    Thanks for the guidance guys.

    James

    Thursday, March 24, 2011 5:03 PM
  • Were you able to resolve the problem? I am receiving the same error message.

    SharePoint Web Services Round Robin Service Load Balancer Event: EndpointFailure
    Process Name: w3wp
    Process ID: 8272
    AppDomain Name: /LM/W3SVC/1210319438/ROOT-1-129460559367441860
    AppDomain ID: 2
    Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:6372736b7ff449ac996c8b5a81e901cd#authority=urn:uuid:01cfa529f69c4d408d47354cbe1073a2&authority=https://rruspprod-a1:32844/Topology/topology.svc
    Active Endpoints: 1
    Failed Endpoints:1
    Affected Endpoint: http://rruspprod-a1:32843/6372736b7ff449ac996c8b5a81e901cd/SearchService.svc

    Any suggestion on resolving would be greatly appreciated.

    Thursday, March 31, 2011 5:54 PM
  • Installed Feb CU

    Restarted Managed Metadata Service on all servers in farm

    IIS Reset

     

    Error is still present in the farm.


    James Grizzle
    ---
    http://www.linkedin.com/in/jamesgrizzle
    Thursday, April 07, 2011 1:28 PM
  • I installed the Feb update as well. Still seeing the roundrobin error also! any word from Microsoft on this?
    Thursday, April 07, 2011 4:52 PM
  • Hi R. van Maurik

    Could you confirm that february CU solved the problem? It seems it is not the case for the other people.

    Best regards,

    Pierre


    Pierre Vivier-Merle - MVP SharePoint Server - http://blogs.developpeur.org/pierre
    Saturday, April 09, 2011 4:08 AM
  • Hi,

    We have this same problem with October CU.

    Regards

    Pete

    Wednesday, April 20, 2011 9:28 AM
  • Any word from support on this issue?
    Wednesday, April 20, 2011 4:39 PM
  • Same problem with the October CUs. 2 app servers, the error shows up a few times a day.
    Thursday, April 21, 2011 8:19 PM
  • Same Issue exist , does anyone solved this issue.

    I am consuming search service and user profile  from farm A to farm B, user profile service works just fine, search was working initially and its stopped working in the last two days.

    SharePoint Web Services Round Robin Service Load Balancer Event: EndpointFailure

    Process Name: w3wp

    Process ID: 2244

    AppDomain Name: /LM/W3SVC/1860508151/ROOT-1-129493974012662468

    AppDomain ID: 2

    Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:dde4b2b3563c4fcfb8791b3b1aec7b8c#authority=urn:uuid:b229869406d640fdb0bccec332ac998e&authority=https://hsv-spprod:32844/Topology/topology.svc

    Active Endpoints: 2

    Failed Endpoints:1

    Affected Endpoint: http://hsv-spprod:32843/dde4b2b3563c4fcfb8791b3b1aec7b8c/SearchService.svc

    Monday, May 09, 2011 3:35 PM
  • I am working with the Support, they told me to make some group policy change and reboot all the WFE , apparently it didnt work
    Tuesday, May 10, 2011 5:15 PM
  • Please continue to keep us updated as you work with support!  Thanks!!!!
    Tuesday, May 10, 2011 5:49 PM
  • Hi

    Also getting this error, but I am getting it in relation to my backup/restore client. 2 WFE, 2 App servers, 1 SQL cluster with two servers...

     

    We installed Feb CU this morning, but still occurs. Has anyone found a resolution with the APRIL CU?

     

    With regards to the restart of the web service, this was accomplished automatically in our case, with no resolution.

     

    Hope this adds something to this


    Alex

    Thursday, May 26, 2011 7:50 PM
  • Hi,

    We have the same problem and the Feb CU is already installed. Does anyone have experienced the April CU as a solution ?

     


    Fabrice DG, SharePoint Architect at Atos Origin, France

    Wednesday, June 01, 2011 2:43 PM
  • I have just started to experience this on another farm that I am using. This farm had RTM and then I applied April CU. The problem has started showing up in search. same error message. I had deployed the April CU succesfully on two other farms and the problem did not appear there. So perhaps december and later updates have a chance of creating this issue for the farm.

    Jai35805, Please let us know how your progress with MS Support is going.

    thanks


    I want to believe
    Tuesday, June 07, 2011 7:33 PM
  • Hi All,

    Just a couple of observations after attempting to repair tthis on our farm. We have two WFE and two app servers. This error occured frequently on all servers, however we discovered that the MetaData Web Service should have only been running on the WFEs. But removing them from the application servers, this caused a 60% reduction in these errors. We also upgraded all servers to Windows 2008 R2 SP1, which reduced the errors again by half. The remaining errors occured on the WFEs only, and we noticed that if the error occured on one of the WFEs, the second compensated for it immediatly, and the event logs reported a restore of the services immediatly after as well.

    I'm not suggesting that this will work, but we managed to reduce these errors to an inconsiquential amount in our environment.

    Hope this is useful

    Alex R


    -- A. Rodchenko
    Thursday, June 16, 2011 5:45 PM
  • Have a newly built farm 1 App server and 2 WFE servers  Runningthe FEB CU  

    is there no fix for this?

    Wednesday, June 29, 2011 12:30 PM
  • For those of you that are running into the Round Robin Error in relation to Search Service (Such as Jai and Marilla), please try the following to see if it solves the problem:

    Enable the Verbose logging in the farm (the error we are looking for does not show up in normal logging and does not show up with the correlation ID for the error) and perform search until you run into this error. Go through your trace log and you will find an error message that will talk about Access being denied to the system temp directory. Note the service account that is being denied the acccess. You need to explicitly assign access to Windows Temp directory for this account on ALL servers running search services. Once you have assigned the permissions, try to search again and see if the error goes away.

    In fact the permission to temp directory for service accounts is managed by the SharePoint local groups that are created on the servers by SharePoint installation. For some reason, that setup stopped working in two different farms that I worked on after the CU was deployed. When I assigned the permissions explicitly for the service account the problem went away. As I mentioned this happened in more than one farm so I am sure this is related to the CU deployment.

    I am thinking now that MetaData service error is also related to permission assignment on some directory or the issues with local SharePoint groups on the server. Will investigate and report if I have more success


    I want to believe
    Thursday, July 14, 2011 6:16 PM
  • I just received this error message after updating RTM to SP1.

    I have a 2 WFE, 2 APP Server farm.

    Any update on this issue ?

    Tuesday, August 09, 2011 10:37 AM
  • I'm having the same issue with 2x WFE and 1x App server.  

    Log Name:      Application

    Source:        Microsoft-SharePoint Products-SharePoint Foundation

    Date:          08/10/2011 09:26:00 PM

    Event ID:      8313

    Task Category: Topology

    Level:         Error

    Keywords:      

    User:          domain\serviceaccount

    Computer:      appserver.domain.com

    Description:

    SharePoint Web Services Round Robin Service Load Balancer Event: EndpointFailure

    Process Name: OWSTIMER

    Process ID: 5576

    AppDomain Name: DefaultDomain

    AppDomain ID: 1

    Would love to find out if Microsoft has a fix for this.

    Wednesday, August 10, 2011 6:11 PM
  • I am seeing this error for our Search and User Profile Services.  We were running older version and upgraded to SP1, then installed June CU.  I will attempt to follow steps above with regard to temp directory and let this post know how I make out...
    Jonathan Herschel
    Tuesday, September 06, 2011 3:21 PM
  • Jonathan

     

    Any updates, where you able to solve it ?

    Im running June CU & SP1 too.

    Thanks

    Sangeetha


    Sangi
    Tuesday, October 11, 2011 2:41 PM
  • Had exactly same kind of problems with the topology and Load Balancer. Seems that SharePoint Load Balancer does not like singe instance services. Or could be a problem of stale topology map that is not getting updated.

    I've resolved my problems having each service reported in the eventlog on two machines.

    Like in this case the eventlog reported that WebAnalytics is affected, as it was running on just one machine:

    SharePoint Web Services Round Robin Service Load Balancer Event: EndpointFailure

     

    Process Name: OWSTIMER

    Process ID: 6888

    AppDomain Name: DefaultDomain

    AppDomain ID: 1

    Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:aa6bbf6b659842cd802e110b2efaf76c#authority=urn:uuid:489e3af6d98040e188d59aa129d4245d&authority=https://xxxxxx:32844/Topology/topology.svc

    Active Endpoints: 1

    Failed Endpoints:1

    Affected Endpoint: http://xxxxx:32843/xxxxxxxxxxxxxxxxxxxxxxxxxxx/WebAnalyticsService.svc

     

     

    Since I started WebAnalytics on another machine so that I have two instances, I have not got errors anymore.

    Has resolved the LoadBalancer errors with all the services that had trouble.

    HTH.

     


    • Edited by T-L-A Thursday, October 20, 2011 7:00 AM
    Thursday, October 20, 2011 6:42 AM
  • Had the same issue. I was able to resolve it by giving the user mentioned in the event log entry permission to the "Managed Metadata Service application".

    CA > Manage Service Application

    Select "Manage Metadata Service Application" and click on permissions on the ribbon

    Add the user mentioned in the event log entry and check all 3 check boxes

    • Proposed as answer by Ted McLaughlin Tuesday, March 20, 2012 7:57 PM
    Friday, October 21, 2011 2:32 PM
  • I was getting similar error in the search service

     

    Found this in the ULS:

     

    12/05/2011
    08:41:58.67        w3wp.exe
    (0x1534)        0x0420        SharePoint
    Foundation        Topology        8313        Critical        SharePoint
    Web Services Round Robin Service Load Balancer Event: EndpointFailure Process
    Name: w3wp Process ID: 5428 AppDomain Name:
    /LM/W3SVC/1550360228/ROOT-1-129675440405284830 AppDomain ID: 2 Service
    Application Uri:
    urn:schemas-microsoft-com:sharepoint:service:4b043f7eed594e75b8c36fa5edc342f8#authority=urn:uuid:0e3287ef91554f8faf14b934a4b3c7d4&authority=https://CENTRALADMIN:32844/Topology/topology.svc
    Active Endpoints: 1 Failed Endpoints:1 Affected Endpoint: http://QUERYSERVER:32843/4b043f7eed594e75b8c36fa5edc342f8/SearchService.svc        d43f67a3-e23a-4edf-b55f-5f7fa9d703f8


    Turned out that the application pool for the search service was using "LocalSystem" account.

     

    Solution was to create 2 new app pools using a domain account for Search Service and for the Search Query Service.

     

     

    I'm guessing that the same solution can work with other Services as well

     

    Monday, December 05, 2011 4:21 PM
  •                                 Had the same issue. I was able to resolve it by giving the user mentioned in the event

                                   log entry permission to the "Managed Metadata Service application".

                                   CA > Manage Service Application

                                   Select "Manage Metadata Service Application" and click on permissions on the ribbon

                                   Add the user mentioned in the event log entry and check all 3 check boxes

    This fixed the problem for me. 

    Of course I then got a completely different and un-related error message when I did a search :-), but this fixed the Round Robin error message.

    Ted


    • Edited by Ted McLaughlin Tuesday, March 20, 2012 8:00 PM forgot to quote fix
    Tuesday, March 20, 2012 7:59 PM
  • Same thing here. Running FEB 2012 CU, and 2008 R2 SP1.

    Upon suggestion from a PFE, we set the Application Pool for the Topology Site ( under Sharepoint Web Services ) with
      Advanced Settings » Process Model » Load User Profile » True

    It didn't seem to fix it, tho.

    • Proposed as answer by Niteshade Monday, May 07, 2012 5:48 PM
    Thursday, May 03, 2012 3:42 PM
  • So per recommendation from Microsoft Support, we took the plunge and applied the latest April 2012 CU and that seem to resolve the issue for us.  No more errors being recorded.  For the impact to search, we recreated the Web Part for the Search results and it was positive.  We are continuing to monitor however and will provide update should we encounter any issues.

    Config:  2 WFE, 2 App and Clustered SQL

    Monday, May 07, 2012 5:54 PM
  • So per recommendation from Microsoft Support, we took the plunge and applied the latest April 2012 CU and that seem to resolve the issue for us.  No more errors being recorded.  For the impact to search, we recreated the Web Part for the Search results and it was positive.  We are continuing to monitor however and will provide update should we encounter any issues.

    Config:  2 WFE, 2 App and Clustered SQL

    Please let everyone know if the latest April 2012 CU has fixed this issue.


    -Chaotix

    Tuesday, May 22, 2012 10:01 PM
  • Well would be a solution years in the making if it does work! I have switched jobs since :)

    I want to believe

    Wednesday, May 23, 2012 12:27 AM
  • I have applied the April 2012 CU to one of my SP 2010 environment(2WFEs, 2 Apps, and 1 SQL) and April CU did not resolve my issue.

    I am able to see the 8313 error on 2 WFEs and 1 APP.

    Friday, May 25, 2012 1:29 PM
  •  Hi,

    Im getting the same intermittent error with search on multi farm (2 x WFE servers, 2 Apps and SQL cluster) with August 2011 Cumulative updates.  I was wondering if anybody had any more updates on this issue, and if the April 2012 updates had any effect?

    Thanks,

    Tuesday, June 12, 2012 2:38 PM
  • Even with October 2012 CU i have the same issue

    Wednesday, January 09, 2013 11:10 AM
  • Hello,  I was receiving the same error as other appear to be getting.  Only one server in my farm exhibited the problem though.

    My solution:  Application Pools were set to stopped in IIS on the server.  don't ask me why they just were.  This was after applying KB2760408 and then running through the psconfigure to apply the update to all servers in the farm.  The first two servers in the farm completed fine.  The Final server appears to have completed fine but there were some bizzaro messages appearing. 

    I checked out: http://{central Admin URL}/_admin/UpgradeStatus.aspx  to confirm the last message for all your servers is SUCCEEDED with no errors and no warnings.

    Finally I used IIS Manager to inspect the operation of all application pools and sites to ensure all the items were running.  This is where I found the problem with a number of the web services being in the stopped state.  I hit the start button on them and my errors went away.  

    I hope this helps someone else.

    Friday, April 19, 2013 6:56 AM
  • Hi,

    I had the same issue, possibly this article can help somebody to resolve the issue.

    http://sharepointandaspnet.blogspot.com/2014/03/sharepoint-web-services-round-robin.html

    Best regards.

    Wednesday, March 12, 2014 12:26 PM