Category Archives: Default

logging-1920x1080

log management open source

log management open source

In this article we will discuss about log management open source. How to manage log using powershell. Below are points we will check using powershell.

  • Check what are the diagnostic provider
  • How to disable or enable event log provider
  • ULS log settings or sharepoint 2016 logs location
  • Change ULS log settings or sharepoint 2016 logs location
  • How to find ULS logging level
  • Set ULS log verbose
Advertisements
Advertisements

Check what are the diagnostic provider

we can use the powershell cmdlet “Get-SPDiagnosticsProvider” to check what are the diagnostic provider.

log-management_1589x611

How to disable or enable event log provider

We can run the below to command to disable event log provider that is “job-diagnostics-event-log-provider” provider.

Get-SPDiagnosticsProvider job-diagnostics-event-log-provider | Set-SPDiagnosticsProvider -Enable:$false
Get-SPDiagnosticsProvider job-diagnostics-event-log-provider
job-diagnostics-event-log-provider-1581x277

We can run the below to command to enable event log provider that is “job-diagnostics-event-log-provider” provider

Get-SPDiagnosticsProvider job-diagnostics-event-log-provider | Set-SPDiagnosticsProvider -Enable:$true
Get-SPDiagnosticsProvider job-diagnostics-event-log-provider
enable-job-diagnostics-event-log-provider-1577x268
Advertisements
Advertisements

ULS log settings or sharepoint 2016 logs location

We can run the command “Get-SPDiagnosticConfig” to get ULS  logging settings

Get-SPDiagnosticConfig
Get-SPDiagnosticConfig-1315x687

Change ULS log settings or sharepoint 2016 logs location

we can run the command “Set-SPDiagnosticConfig” to Change ULS log settings or sharepoint 2016 logs location.

PS C:\> Set-SPDiagnosticConfig -DaysToKeepLogs 7 -LogLocation "E:\Logs" -EventLogFloodProtectionEnabled
PS C:\> Get-SPDiagnosticConfig
change-sharepoint-2016-logs-location-1317x712
diagnostic-logging-1255x665
Advertisements
Advertisements

How to find ULS logging level

We can run the command “Get-SPLogLevel” to find ULS logging level.

Get-SPLogLevel -identity "eApproval:*", General, audit, "Business Data"
Get-SPLogLevel-1314x534

Set ULS log verbose

we can set ULS log Verbose and categories by using “Set-SPLogLevel

Set-SPLogLevel -TraceSeverity verbose -EventSeverity verbose -Identity "eApproval:*", General, audit, "Business Data"
Get-SPLogLevel -identity "eApproval:*", General, audit, "Business Data"
Set-SPLogLevel-1317x625

Create new log file

we can create a new log file by running the command below.

New-SPLogFile
new-splogfile-1316x108
Advertisements
Advertisements
Advertisements
SharePoint search crawl properties storage locations

SharePoint search crawl properties storage locations

Advertisements

Advertisements

SharePoint search crawl properties storage locations

Here we will discuss about SharePoint search crawl properties storage locations. When gathering files from a content source, the SharePoint 2013 Crawl Component can be very I/O intensive process – locally writing all of the files it gathers from content repositories to its to temporary file paths and having them read by the Content Processing Component during document parsing. This post can help you understand where the Crawl Components write temporary files, which can help in planning and performance troubleshooting (e.g. Why does disk performance of my C:\ drive get so bad – or worse, fill up – when I start a large crawl?)

By default, all Search data files will be written within the Installation Path

  • The Data Directory (by default, a sub-directory of the Installation Path) specifies the path for all Search data files including those used by I/O intensive components (Crawl, Analytics, and Index Components)
    • The Data Directory can only be configured at the time of Installation (e.g. it can only be changed if uninstalling/re-installing SharePoint on the given server)
      • From the Installation Wizard, choose the “File Location” tab as seen below
      • IMPORTANT: Before uninstalling SharePoint, first modify your Search topology by removing any Search components from the applicable server. Once SharePoint is re-installed, you can once again deploy the components back to this server.
    • The defined path can be viewed in the registry:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\15.0\Search\Setup\DataDirectory

    • Advanced Note: The Index files (by default, written to the Data Directory) path can be configured separately when provisioning an Index Component via PowerShell using the “RootDirectory” parameter

3175.installAndDataPath
(As a side note: the graphic is only intended to display the default locations specified at install time. It is recommended to change these to a file path other than C:\ drive)

For the Crawl Component:

  • When crawling [gathering] an item, the filter daemon (mssdmn.exe – a child process of the Crawl Component that actually interfaces with an end content repository using a Search Connector/Protocol Handler) will download any applicable file blobs to the SSA’s “TempPath” (e.g. an HTML file, a Word document, a PowerPoint presentation, etc)
    • In the graphic below, this is step 2a
    • The defined path can be viewed either:
      • In the registry (of a Crawl server)

        HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\15.0\Search\Global\Gathering Manager\TempPath

      • Or as a property of the SSA:

        $SSA = Get-SPEnterpriseSearchServiceApplication

        $SSA.TempPath

  • When the filter daemon completes the gathering of an item, it is returned to the Gathering Manager (mssearch.exe – responsible for orchestrating a crawl of a given item) and the applicable blob is moved to the “GathererDataPath“, which is a path relative to the DataDirectory mentioned above.
    • In the graphic below, this occurs in step 2b
    • The defined path can be viewed in the registry (of a Crawl server):

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\15.0\Search\Components\-GUID-of-theSSA-crawl-0\GathererDataPath

  • The GathererDataPath is mapped as a network share (used by the Content Processing Components)
    • The shared path can be viewed in the registry (of a Crawl server):

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\15.0\Search\Components\-GUID-of-theSSA-crawl-0\GathererDataShare

8233.crawlFlow
Usage by the Content Processing Components:

  • When the item is fed from the Crawler to the Content Processing Component (step 3 above), the item is only logically submitted to the CPC in a serialized payload of properties that represent that particular item – any related blob would remain on the Crawler and retrieved by a later stage in the processing flow
    • For SharePoint list items, there would typically not be a blob (unless the list item had an attachment)
    • For a document in a SharePoint library, the blob would represent the item’s associated file (such as a Word document)
  • During the Document Parsing stage in the processing flow (e.g. during step 4 above), the item’s blob will be retrieved from the Crawl Component via the GathererDataShare
  • When the Crawl Component receives a callback (success or failure) from the CPC (e.g. in step 6b above after an item has been processed), the temporary blob is then deleted from the GathererDataPath

1373.gathererDataShare
An example path to an item with DocID 933112 would look like the following:

file://crawlSrv/gthrsvc_7ecdbb10-3c86-4298-ab09-04f61aaeb636-crawl-0//f8/0xe3cf8_1.aspx   

#0xe3cf8 hex = 933112 decimal

Where:

  • crawlerSrv is a server running a crawl component
  • gthrsvc_-GUID-of-theSearchAdminWebServiceApp--crawl-0 is the name of the crawl component
    • This GUID can be identified using the following PowerShell:

      $SSA = Get-SPEnterpriseSearchServiceApplication

      $searchAdminWeb = Get-SPServiceApplication –Name $SSA.id

      $searchAdminWeb.id

      7ecdbb10-3c86-4298-ab09-04f61aaeb636

  • And the file name is actually re-named to the hex value of the docID
    • For example: 0xe3cf8 hex = 933112 decimal
    • Which we can see in ULS, such as:
      • From the Crawl Component (in this case, running on server “faceman”):

        mssearch.exe     SharePoint Server Search Crawler:Content Plugin      af7zf VerboseEx

        CTSDocument: FeedingDocument: properties : strDocID = ssic://933112 key = path values =\\FACEMAN\gthrsvc_7ecdbb10-3c86-4298-ab09-04f61aaeb636-crawl-0\\f8\0xe3cf8.aspx 

      • From the Content Processing Component:

        NodeRunnerContent2-834ebb1f-009    Search    Document Parsing      ai3ef VerboseEx

        AttachDocParser – Parsing: ‘file://faceman/gthrsvc_7ecdbb10-3c86-4298-ab09-04f61aaeb636-crawl-0//f8/0xe3cf8.aspx’

Advertisements

Advertisements

SharePoint shortcut URL and hidden list 1920X1080

SharePoint shortcut URL and hidden list

Advertisements

Advertisements

SharePoint shortcut URL and hidden list

Users and Permissions:
People and Groups: _layouts/people.aspx
Site Collection Admins: _layouts/mngsiteadmin.aspx
Advanced Permissions: _layouts/user.aspx
Master Pages: _Layouts/ChangeSiteMasterPage.aspx
Look and Feel:
Quick Launch settings page: /_layouts/quiklnch.aspx
Title, Desc, and Icon: _layouts/prjsetng.aspx
Navigation: _layouts/AreaNavigationSettings.aspx
Page Layout and Ste Templates: _Layouts/AreaTemplateSettings.aspx
Welcome Page: _Layouts/AreaWelcomePage.aspx
Tree View: _layouts/navoptions.aspx
Top Nav Bar: _layouts/topnav.aspx
Site Theme: _layouts/themeweb.aspx
Reset to Site Definition: _layouts/reghost.aspx
Searchable Columns: _Layouts/NoCrawlSettings.aspx
Site Content Types: _layouts/mngctype.aspx
Galleries
Site Columns: _layouts/mngfield.aspx
Site Templates: _catalogs/wt/Forms/Common.aspx
List Templates: _catalogs/lt/Forms/AllItems.aspx
Filter toolbar for Lists and libraries: ?Filter=1
Web Parts: _catalogs/wp/Forms/AllItems.aspx
Workflows: _layouts/wrkmng.aspx
Workflow history hidden list: /lists/Workflow History
Master Pages and Page Layouts: _catalogs/masterpage/Forms/AllItems.aspx
Regoinal Settings: _layouts/regionalsetng.aspx
Site Administration
Recreate default site sp groups: _layouts/15/permsetup.aspx
recycle bin: _layouts/RecycleBin.aspx
Site Libraries and Lists: _layouts/mcontent.aspx
Site Usage Report: _layouts/usageDetails.aspx
User Alerts: _layouts/sitesubs.aspx
RSS: _layouts/siterss.aspx
Search Visibility: _layouts/srchvis.aspx
Sites and Workspaces: _layouts/mngsubwebs.aspx
Site Features: _layouts/ManageFeatures.aspx
Delete This Site: _layouts/deleteweb.aspx
Site Output Cache: _Layouts/areacachesettings.aspx
Content and Structure: _Layouts/sitemanager.aspx
Content and Structure Logs: _Layouts/SiteManager.aspx?lro=all
Search Settings: _layouts/enhancedSearch.aspx
Site Collection Administration
Search Scopes: _layouts/viewscopes.aspx?mode=site
Search Keywords: _layouts/listkeywords.aspx
Recycle Bin: _layouts/AdminRecycleBin.aspx
Site Collection Features: _layouts/ManageFeatures.aspx?Scope=Site
Site Hierachy: _layouts/vsubwebs.aspx
Site hierarchy page (lists of sub sites): /_layouts/1033/vsubwebs.aspx
Portal Site Connection: _layouts/portal.aspx
Site Collection Audit Settings: _layouts/AuditSettings.aspx
Site Collection Policies: _layouts/Policylist.aspx
Site Collection Cache Profiles: Cache%20Profiles/AllItems.aspx
Site Collection Output Cache: _Layouts/sitecachesettings.aspx
Site Collection Object Cache: _Layouts/objectcachesettings.aspx
Variations: _Layouts/VariationSettings.aspx
Variation Labels: _Layouts/VariationLabels.aspx
Translatable Columns: _Layouts/TranslatableSettings.aspx
Variation Logs: _Layouts/VariationLogs.aspx
Site Settings: _layouts/settings.aspx
Delete user from Site collection (on-premises): /_layouts/15/people.aspx?MembershipGroupId=0

Load document tab initial
?InitialTabId=Ribbon.Document

Delete user from Site collection (on-premises):
/_layouts/15/people.aspx?MembershipGroupId=0

Display list in grid view. ‘True’ is case sensitive:
?ShowInGrid=True

Sandboxed Solution Gallery:
/_catalogs/solutions/Forms/AllItems.aspx

Filter toolbar for Lists and libraries:
?Filter=1

Site usage page:
/_layouts/usage.aspx

View all site content page (Site content):
/_layouts/viewlsts.aspx

Get the version of the SharePoint server (Patch level):
/_vti_pvt/Service.cnf

Web Part Maintenance Page:
?Contents=1

Show Page in Dialog View:
?isdlg=1

Application page for registering SharePoint apps
/_layouts/15/appregnew.aspx

Save Site as a template
/_layouts/savetmpl.aspx

Sign in as a different user
/_layouts/closeConnection.aspx?loginasanotheruser=true

Enable SharePoint designer
/_layouts/SharePointDesignerSettings.aspx

Quick Deploy List
Quick%20Deploy%20Items/AllItems.aspx

Open Page in Edit Mode
?ToolPaneView=2

Taxonomy Hidden List (MMS)
Lists/TaxonomyHiddenList/AllItems.aspx

User Information List:
_catalogs/users
_catalogs/users/simple.aspx

Force displaying the user profile in the site collection:
/_layouts/userdisp.aspx?id={UserID}&Force=True

Site hierarchy page (lists of sub sites)
/_layouts/vsubwebs.aspx
/_layouts/1033/vsubwebs.aspx

Add Web Parts Pane: ?ToolPaneView=2 : Add to the end of the page URL; will only work if the page is already checked out
Create: [area]/_layouts/spscreate.aspx
Create: /_layouts/create.aspx

Create list in a different portal area :

/_layouts/new.aspx?NewPageFilename=YourTemplateName.stp&ListTemplate=100&
ListBaseType=0

When you save a template in a portal area and try to create a new list in a different portal area, the template will not show on the Create page. Use this URL to force it to show.

Documents and Lists: /_layouts/viewlsts.aspx

List Template Gallery: /_catalogs/lt

Manage Audiences: /_layouts/Audience_Main.aspx

Manage Cross Site Groups: /_layouts/mygrps.aspx

Manage List Template Gallery: /_catalogs/lt/Forms/AllItems.aspx

Manage My Alerts: /_layouts/MySubs.aspx

Manage People: /_layouts/people.aspx

Manage Site Collection Administrators: /_layouts/mngsiteadmin.aspx

Manage Site Collection Users:
/_layouts/siteusrs.aspx : To access you must be an admin on the server or a site collection admin for the site.

Manage Site Groups: /_layouts/role.aspx

Manage Site Template Gallery: /_catalogs/wt/Forms/AllItems.aspx

Manage Site Template Gallery: /_catalogs/wt/Forms/Common.aspx

Manage Sites and Workspaces: /_layouts/mngsubwebs.aspx

Manage User Alerts: /_layouts/AlertsAdmin.aspx

Manage User Alerts: /_layouts/SiteSubs.aspx

Manage User Permissions: /_layouts/user.aspx

Manage Web Part Gallery: /_catalogs/wp/Forms/AllItems.aspx

Master Page Gallery: /_catalogs/masterpage : Also includes Page Layouts

Modify Navigation: /_layouts/AreaNavigationSettings.aspx

Recycle Bin: /_layouts/AdminRecycleBin.aspx

Save as site template: /_layouts/savetmpl.aspx

Site Column Gallery: /_layouts/mngfield.aspx

Site Content and Structure Manager: /_layouts/sitemanager.aspx

Site Content Types: /_layouts/mngctype.aspx

Site Settings: /_layouts/settings.aspx

Site Settings: /_layouts/default.aspx

Site Template Gallery: /_catalogs/wt

Site Theme: /_layouts/themeweb.aspx

Site usage details: /_layouts/UsageDetails.aspx

Site Usage Summary: /_layouts/SpUsageWeb.aspx

Site Usage Summary: /_layouts/Usage.aspx

Sites Registry: /SiteDirectory/Lists/Sites/Summary.aspx

Top-level Site Administration: /_layouts/webadmin.aspx

User Information: /_layouts/userinfo.aspx

Web Part Gallery: /_catalogs/wp

Web Part Page Maintenance: ?contents=1 : Add to the end of the page URL

Display template SharePoint Server 2013 1920x1080

Display template SharePoint Server 2013

Display templates for the Content Search Web Part

You can use the following Display template SharePoint to change the appearance of content that is shown in a Content Search Web Part. These display template files are located in the Content Web Parts subfolder in the Display Templates folder in the Master Page Gallery.

template-contentsearchwebpart

Display templates for the Refinement Web Part and the Taxonomy Refinement Web Part

You can use the display templates listed in the following table to change the appearance of content that is shown in a Refinement Web Part and a Taxonomy Refinement Web Part. These display template files are located in the Filters subfolder in the Display Templates folder in the Master Page Gallery. Note that there are different display templates for different refiner types.

template-webpart

Display templates for the Search Results Web Part

You can use the display templates in the following table to change the appearance of content shown in a Search Results Web Part. Note that the hover panels for the different result types have separate display templates. These display template files are located in the Search subfolder in the Display Templates folder in the Master Page Gallery.

template-search1
template-search2

Advertisements

Advertisements

16 Hive directories default location SharePoint 2016

16 Hive directories default location SharePoint 2016

16 Hive directories default location SharePoint 2016:

16 Hive directories default location SharePoint 2016 path is as below

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.

Advertisements

Advertisements

New APP created once "Project Functionality" feature is activated.

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