Cannot Access a local SharePoint site from server console(WFE)

The fix is to disable the loopback check in the registry.

Method 2: Disable the loopback check
Follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. In Registry Editor, locate and then click the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
  3. Right-click Lsa, point to New, and then click DWORD Value.
  4. Type DisableLoopbackCheck, and then press ENTER.
  5. Right-click DisableLoopbackCheck, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Quit Registry Editor, and if possible then restart your computer (Not compulsory)

Comments

Post a Comment

Popular posts from this blog

SharePoint 2016 and 2019 Ports

http://sharepoint2016server.blogspot.com/2016/10/sharepoint-2016-ports-list.html SharePoint 2019: Distributed Cache : TCP Port 22233, 22236 : UDP Port N/A : Protocols ICMP Type 0 (ping) People Picker : TCP Port 53, 88, 135, 137–139, 389, 445, 636, 749, 750, 3268, 3269 : UDP Port N/A 53, 88, 137–139, 389, 445, 749 : UDP Port N/A : Protocols N/A Sandbox Service : TCP Port 32846 : UDP Port N/A : protocols N/A Search Crawler : TCP Port Web Application Ports Used (e.g., 80, 443) : UDP Port N/A : Protocols N/A Search Index : TCP Ports 16500–16519 : UDP Port N/A : Protocols N/A Service Applications : TCP Port 32843, 32844 : UDP Port N/A : Protocols N/A SQL Server : TCP Port 1433 (default) : UDP Port 1434 (default) : Protocols N/A WCF Services : TCP Port 808 : UDP Port N/A : Protocols N/A User Profile Service : TCP Port 53, 88, 389, 5725, 1025–5000, 49152–65536 : UDP Port 53, 88, 389, 464 : Protocols N/A SMTP : TCP Port 25 (default), 587 (TLS default) : UDP Port N/A : Protocols
Read more

PsConfig step by step /Configuration Wizard. “Upgrade Available” vs “Upgrade required”

Image
The "Upgrade available" simply means that there is a newer patch available at the SharePoint Updates page than the one installed on your SharePoint farm. We checked the Farm version and made sure its the latest available version. Getting "Upgrade Required" error message in SharePoint 2013? Well, Ideally, We have to run the SharePoint Products Configuration Wizard on the server(s) right after installing the service pack/patches. In Windows Server 2012, SharePoint updates are part of Windows Server Update. It installs patches but never runs Products configuration wizard automatically! You still have to run psconfig wizard to complete patching! ----------------------------------------------------  https://www.sharepointdiary.com/2014/02/upgrade-available-server-status-after-sharepoint-patching.html https://www.sharepointdiary.com/2015/03/upgrade-required-status-in-sharepoint-central-admininstration.html https://blog.stefan-gossner.com/2015/08/20/why-i-prefer-psconfigui
Read more

Unlock the SharePoint site using Powershell command

if your SharePoint site locked, then use the below Powershell command to unlock. Note: Lock means your site will be disabled all actions (creating new item, library/list settings, limited site action menu etc.,) even if you are site collection administrator. if you try to add another user as site collection administrator using powershell/central administrator, then will get the following error. this error because of SharePoint Lock. Additions to this Web site have been blocked To avoid above errors. use the below Powershell command Set - SPSite http : //SiteCollectionUrl -LockState Unlock
Read more