Melick's Blog

AutoSPInstaller Online is one of a great project that facilitate Automated SharePoint installation including Sharepoint 2010, 2013 and 2016. Auto SP Installer provides a powerful way to deploy and configure a single-server development environment to multiple-server SharePoint farm. Reference: https://autospinstaller.com/ Before doing anything we will set up the environment for SharePoint three server Farm. Will name these servers as SPWFE - Share Point Front End Server SPAPP - Share Point App server SPDB - DB server Please find the reference for SharePoint minimum requirement and practices from https://docs.microsoft.com/en-us/SharePoint/install/install-sharepoint-server-2016-across-multiple-servers For the the medium segregation, we have to create below list of service accounts. Service Accounts for Active Directory Service Account name : spadmin Rights : Local Admin All Servers (DB,WFE,APP) SQL DB Rights: SQL DB Creator and Security Admin Rights Domain Privileges: Service ...

  When you debuging your Sharepoint Search you might have come a cross that there is a error in crawl log in sharepoint farm. The URL of the item could not be resolved. The repository might be unavailable, or the crawler proxy settings are not configured. To configure the crawler proxy settings, use Search Administration page This is because your search can not be resolved to a perticular address ; most probably youy coperate proxy blocking it domain name resolution is not happening inside the sharepoint crawl Easiest way to resolve the error is First clear any proxy settings you have specified in the search settings. You can go to the Crawling Proxy settings and make sure you didint specify the proxy for content crawling. Then goto each server in your farm and add the doman name entry resolution in the HOST file. C:\Windows\System32\drivers\etc\hosts Now you can run the crawler again and you will see there are no top level erros in your crawl log. 

There are some common SharePoint Search Service Application erros which you might encountered when you are wokring with the service. Administrative status     Paused for:Index reset Administrative status     Paused for:External request, Index reset Administrative status     Paused for:External request You may find these erros when you navigate to Central Administration and Manage service applications then Search Service Application you can find service error details in the Search Service Application: Search Administration page Common Resolution for Those problems If you see those erros first you can do a quick workround and see whether its resolved. Stop following services in all nodes in the farm. (actually this is needed for notes which search components are running , but if you couldnt find those do it for all servers) You can goto servics by type services.msc in run window (Windows + R) Stop “SharePoi...