3

Recently created a new SharePoint 2016 farm using MinRole for application and WFEwithDC on dedicated boxes, all went well. I create two web applications for content and MySites.

http://portal http://mysite

I made host entry 127.0.0.1 for both URLS on WFE and host file entry on App Server with IP of WFE to point everything to WFE from both boxes.

Question is when I try to access the site from WFE or App server, home page get stuck at “Working on it” for hours and never loads . I try to go to settings page by entering the URL manually and I was able to go to the page. Any idea why it is stuck at working on it ? So after I change the host file entries on app server to 127.0.0.1 to point the URL to the app server itself ( instead of WFE) and site came up fine. I can delete and recreate those 2 web apps but would like to know what is going on here , is this something to do with MinRole ?

Please share your thoughts comments . Thanks

Improve this question
20
  • is loop back check disabled on server? what is the behavior from client machine not from server?
    – Waqas Sarwar MVP ♦
    Commented Apr 24, 2017 at 17:57
  • Thanks for replying , yes , Loopback check is disabled. I am getting the same behavior from the client machine as well. interesting part is if I point the site to the App Server using host files it works. it seems like an issue at the server level but I can be wrong too.
    – Umr
    Commented Apr 24, 2017 at 18:42
  • Did u check uls logs? Is ur Upa is running and connected to web application? Also root site collections are created?
    – Waqas Sarwar MVP ♦
    Commented Apr 24, 2017 at 18:47
  • UPA is running . connected to web application as well. To make sure I just disconnect and reconnect . Root site collection are created, which can be accessed if I point the sit to the server running with MinRole =Application.
    – Umr
    Commented Apr 24, 2017 at 19:16
  • 1
    Another update, after I made app pool DB owner for 4 dbs you mentioned. i just reboot the sql server now and I can access MySite now. Thanks for all your help in this case. I am still curious why this implementation was so messed up with permissions, I never had these issues b4, used autospinstaller this time btw. Next question is how to mark some of these comments as answer as they were very helpful to point me in the right direction.
    – Umr
    Commented Apr 25, 2017 at 13:49

1 Answer 1

Reset to default
2

there are many reasons for this behavior, i would check following things.

  • check the ULS logs and Event Logs...But you said ULS logs empty then check WSS WPG admin account has read and write permission on the Log directory.
  • Check the Status of the servers in the Central admin, if it is compliance with MinRole.
  • Make Sure web Application provisioned on the WFE.
  • No AntiVirus or Firewall Blocking on the server
  • Loop Back Check is disabled
  • UPA is provisioned and connected to the web application.
  • App Pool account should have permission on the UPA DBs.
Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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