SharePoint 2016: 16 Hive and other important directories default location

Folder Location :

The 16 Hive folder is located at the following path

C:\Program Files\Common files\Microsoft Shared\Web Server Extensions\16

16 Hive and other important directories location SharePoint2016

16 Hive and other important directories location SharePoint 2016

Folder Structure :

The 16 Hive has a definite folder structure which holds the core SharePoint server files.

ADMISAPI:- It contains soap services for Central Administration. If this directory is altered, remote site creation and other methods exposed in the service will not function correctly.

Bin:- The directory contains all the core binary files, utilities which used by SharePoint Services. command line tools such as STSADM.EXE also present in this folder.

Client:- This directory contains files that are used for creating office apps.

Config:- This directory contains files used to extend IIS Web sites with SharePoint Server. If this directory or its contents are altered, Web application will not function correctly.

GAC:- This folder contains Microsoft.SharePoint.Client.Runtime.Portable.Resources.dll and Microsoft.SharePoint.Client.Runtime.Resources.DLL.

HCCab:- This directory has a set of cab files which has content information used by the SharePoint help system.

Help:- The folder contains html help file (.chm) used by the configuration wizard.

ISAPI:- This directory contains all the standard Web Services for SharePoint and resources and configuration files that the web services use.

Logs:- This is the folder where we can have all the SharePoint related logs will see. This is important when any problem or error occur in SharePoint you have to trace the logs files in this folder to get the error messages.

Policy:- This directory contains SharePoint 2016 Server policy files.

Resources:- This directory contains the core.resx file used for creating language packs for SharePoint. by which different SharePoint sites with different languages and cultures can be create.

Template:- It contains the core web site functionality like the features, templates, configurations, resources of a web site.

UserCode:- This directory contains files used to support sandbox solution.

Web Clients:- This directory contains files related to Client Object Model.

Web Services:- This directory is the root directory where SharePoint back-end Web services are hosted, for example, Excel and Search.

Other Directories In SharePoint 2016 :

C:\Inetpub\wwwroot\wss – This directory (or the corresponding directory under the Inetpub root on the server) is used as the default location for IIS Web sites.

C:\ProgramFiles\Microsoft Office Servers\16.0 – This directory is the installation location for SharePoint Server 2016 binaries and data. The directory can be changed during installation.

C:\ProgramFiles\Microsoft Office Servers\16.0\WebServices – This directory is the root directory where SharePoint back-end Web services are hosted, for example, Excel and Search.

C:\ProgramFiles\Microsoft Office Servers\16.0\Data – This directory is the root location where local data is stored, including search indexes.

C:\ProgramFiles\Microsoft Office Servers\16.0\Logs – This directory is the location where the run-time diagnostic logging is generated.

Activate site Features create APP in Site Contents SharePoint2016

Today I successfully installed SharePoint Server 2016 on-premises overcoming few errors related to prerequisite as per my previous posts.

You can see below previous posts :

  1. Windows Server Appfabric: Installation error SharePoint 2016
  2. Cannot connect to database master at SQL Server at server_name. The database might not exist, or the current user does not have permission to connect to it Error SharePoint 2016
  3. Failed to create configuration database. An exception of type Microsoft.SharePoint.Upgrade. SPUpgrade Exception was thrown. Additional exception information: One or more types failed to load. Please refer to the upgrade log for more details Error SharePoint 2016
  4. Program can’t start because api-ms-win-crt-heap-l1-1-0.dll is missing SharePoint2016
  5. Unable to install Microsoft Information Protection and control Client 2.1 error SharePoint 2016

Here I am very excited to let you know the “SharePoint APP” created in “Site Contents” by activating the “site feature“.

you may take it very easy but its not as simple as to resolve issues sometimes, that time it will help you a lot.

a. “Default APP” once site is created, before activating any feature.

Default APP in Site Contents with no feature activate

Default APP in Site Contents with no feature activate, once site is created

b. New APPs  added in Site Contents  after “Publishing Feature” is activated

New APPs added in Site Contents after

New APPs added in Site Contents after “Publishing Feature” is activated

c. New APPs  added in Site Contents  after “Content Organizer” feature is activated.

New APPs added in Site Contents after

New APPs added in Site Contents after “Content Organizer” feature is activated.

d. New APPs  added in Site Contents  after “Community Site” feature is activated.

Site-Contents-Community-Site-Feature-activate

Site-Contents-Community-Site-Feature-activate

e. New APPs  added in Site Contents  after “Site Feed” feature is activated.

New APPs added in Site Contents after

New APPs added in Site Contents after “Site Feed” feature is activated.

f. New APPs  added in Site Contents  after “Project Functionality” feature is activated.

New APP created once

New APP created once “Project Functionality” feature is activated.

amazon     amazonsp2016  amazonsp2016_2

Windows Server Appfabric: Installation error SharePoint 2016

If you are installing SharePoint 2016 Prerequisites manually downloading the files and after that run the “Install Software Prerequisites” from SharePoint 2016 installation file to verify everything installed manually is correct, you may face error like this “Windows Server Appfabric: Installation error“. sp2016

This is a generic MSI error message and does not give any indication about how to get the issue fixed. Uninstall or reinstalling only makes it worse.

Resolution :

The reason being the prerequisites installs the file and configure it automatically. If we install manually, then we are trying to bypass the configuration, so that error will be received. The issue can be caused due to the following: *  The path to the PowerShell executable that is needed for the AppFabric installation is incorrect. *  In some scenarios, repeated uninstallation and re-installation does not fix the issue. This is because the installer does not remove the PSModulePath entry in Environment *  Variables during uninstallation and the installation fails because the entry already exists. If you are trying to install all the prerequisites manually as the server does not have a connection to internet. Note: Appfabric installation and configuration has to be done by the prerequisite installer ONLY and not in a stand-alone manner.You should follow the manual process of installation  if there is error in automatic process by following Install Prerequisite (prerequisiteinstaller.exe) . You can implement any one of the two solutions listed below Solution 1 Append the following path to PSModulePath entry in the environment variables – %SYSTEMROOT%\System32\WindowsPowerShell\v1.0

  • Go to My Computer, right-click Properties
  • On the System page click Advanced System Settings on the left-side pane.
  • If you receive a UAC prompt, click on Yes to launch the System Properties dialog box
  • From the Advanced tab, click Environment Variables
  • Within the System Variables section in the lower half, select PSModulePath and click on Edit (or double-click PSModulePath‘)
  • Append the following path to PSModulePath entry in the environment variables %SYSTEMROOT%\System32\WindowsPowerShell\v1.0\
  • Ensure that the PSModulePath entry looks like this: C:\Windows\system32\WindowsPowerShell\v1.0\Modules\;c:\Program Files\AppFabric 1.1 for Windows Server\PowershellModules

Solution 2

  • There are chances that other applications might be referencing the same variable and may fail if it is deleted. This is what we can do if solution 1 does not help.
  • Remove the PSModulePath entry from the ‘Environment Variables’ and re-run the installer. Once it completes successfully, ensure that the PSModulePath entry looks the same as mentioned in solution 1.

Reference : https://msdn.microsoft.com/en-us/library/dd878326(v=vs.85).aspx