0

Just a qucik one, what could be the possible cause of error, or where to look for fixing this error.

We got multiple front-ends, and everything is working fine. BUT, on the third WFE users cannot access a sitecollection Y. This sitecollection Y, can be accessed from all the other WFEs, and on the failing WFE users can acccess all other sitecollections besides sitecollection Y.

My logic is not enough to solve this.

  • Are you using alternate access mappings? Using a load balancer for the wfe's? – Phil Greer Apr 30 '14 at 14:51
  • Yes, there is a LB and there is also AAM. The odd thing is that everything else can be accessed through the WFE except for this one sitecollection. I tried a iisreset on the Wfe, but that didnt help. – emo Apr 30 '14 at 17:02
0

Verify that your AAM settings are correct. Then, add the third wfe as an "Internal URL" in AAM.

Also, verify that the hosts files on your all wfe's are correct. Test further, by adding/removing references to that troublesome wfe.

Have you checked out this post? It may also be helpful.

If that doesn't resolve your problem, browse to the offending site collection on wfe #3 and see what happens in the IIS logs. Post your findings as a reply to this answer and I'll dig in further.

  • Hey, Phil, i was away for a while. We tried AAM but it was already set up correctly. The IIS logs gave some errors, but we decided to remove the WFE from the environment, will maybe try to create it again on a sooner time, and do the configuraton again. Thanks for your advices. /emo – emo May 7 '14 at 14:13
  • Review this post and links contained within before you try adding the wfe again. Hope it works better next time! – Phil Greer May 7 '14 at 14:19

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.