Create State service application.

A state service application is the container for state service databases.

Using Windows PowerShell

1. Click SharePoint 2013 Management Shell.

2. From the Windows PowerShell command prompt (that is, PS C:\>), type the following command :

New-SPStateServiceDatabase -Name "State Service Database" | New-SPStateServiceApplication -Name "StateServiceApp1" | New-SPStateServiceApplicationProxy -DefaultProxyGroup

Create a Visio Graphics Service service application

Using Central Administration

To create a service application, you must be a member of the farm administrators group.

1. Browse SharePoint 2013 Central Administration.

2. On the SharePoint Central Administration website Home page, in the Application Management section, click Manage service applications.

3. On the ribbon, click New, and then click Visio Graphics Service. Type a name for the new service application.

4. Choose an existing application pool or create a new one.

5. Choose whether to create a Visio Graphics Service Application Proxy (recommended).Click OK.

Using Windows PowerShell

1. Click SharePoint 2013 Management Shell.

2. From the Windows PowerShell command prompt (that is, PS C:\>), type the following command :

New-SPVisioServiceApplication -Name <ServiceAppName> -ApplicationPool <AppPoolName> -AddToDefaultGroup

Example

New-SPVisioServiceApplication -Name "Visio Graphics Service Application" -ApplicationPool "SharePoint Hosted Services" -AddToDefaultGroup

How to create a SharePoint Subscription Settings Service application through PowerShell

This example assumes that a managed account for DOMAIN\ManagedAccount already exists. 

$AppPool = New-SPServiceApplicationPool -Name SettingsServiceAppPool -Account (Get-SPManagedAccount DOMAIN\ManagedAccount)

$App = New-SPSubscriptionSettingsServiceApplication -ApplicationPool $appPool -Name SettingsServiceApp -DatabaseName SettingsServiceDB

$proxy = New-SPSubscriptionSettingsServiceApplicationProxy -ServiceApplication $App

Get-SPServiceInstance | where{$_.TypeName -eq "Microsoft SharePoint Foundation Subscription Settings Service"} | Start-SPServiceInstance

This example creates

- an application pool

- a new subscription settings service application

- a subscription settings service application proxy

- and starts the service instance on the local machine. 

BDC The name ‘Domain\User Name‘ could not be resolved via Active Directory

Issue

When you work with SharePoint 2010 and BDC Service application when you try to create an External Content Type, you might come across this error. This is because the person who had created the Content type is not present in the Active Directory. He/she may have left your organization.

Resolution

1) Browse to Central Administration

2) Choose the BDC Service application. Make sure that this person is not listed as the administrator on the service application

3) Inside the BDC service application, select Set Metadata Store Permissions

4) The user listed in the error will be listed here.

5) Select the user and remove him/her.

6) Make sure that you select the checkbox that says - 

Propagate permissions to all BDC Models, External Systems and External Content Types in the BDC Metadata Store. Doing so will overwrite existing permissions.

7) Click OK

Unable to process the request . Wait a few minutes and try performing this operation again

Issue Description

Recently I came across this issue where some of the end users were getting an error message when they tried to open an Excel file in SharePoint in the browser.

Unable to process the request.

Wait a few minutes and try performing this operation again.

Cause

The Excel Services Application server computer is in a non-valid state and may need to be restarted.

Resolution

Most of the online articles were asking me to restart the Central Administration server.I did not want to do that and found a different fix.

Identify the application pool running the Excel Services service application (from IIS) and Recycle it.

1) Start –>Run –> inetmgr

2) Under the Sites click on SharePoint Web Services. This will list down the Services in SharePoint.

3) Click on each GUID –> Change the view from Features View to Content View

4) On finding ExcelService.asmx -> Right click that web service -> Manage Application -> Advanced Settings.

5) Identify the Application Pool (make a note of this).

6) Now in IIS –> Application Pools –> choose the Application Pool you noted down in previous step   -> Recycle (recycle the application pool).

Identify the Application Pool for a Service Application

1) Start –>Run –> inetmgr

2) Under the Sites click on SharePoint Web Services. This will list down the Services in SharePoint.

3) Click on each GUID –> Change the view from Features View to Content View

4) On finding SearchService.svc -> Right click that web service -> Manage Application -> Advanced Settings.

5) Identify the Application Pool (make a note of this).

6) Now in IIS –> Application Pools –> choose the Application Pool you noted down in previous step   -> Recycle (recycle the application pool).

Internal server error exception: System.NullReferenceException: Object reference not set to an instance of an object

Error Description

Recently I came across this error with SharePoint Search. I was searching in a SharePoint list and got the below error.

Error

Internal server error exception:

Troubleshoot issues with Microsoft SharePoint Foundation.

On checking the ULS logs I found the below entries

01/28/2015 10:59:51.10         w3wp.exe (0x31D8)                0x2030    SharePoint Server Search      Query      fm9a        Unexpected                CoreResultsWebPart::OnInit: Exception initializing: System.NullReferenceException: Object reference not set to an instance of an object.     at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.SetPropertiesOnQueryReader()     at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.OnInit(EventArgs e)               7001a8bf-b506-4096-b46b-003fbb5ec91b

01/28/2015 10:59:51.10         w3wp.exe (0x31D8)                0x2030    SharePoint Server Search      Query      g1j9         Exception                Internal server error exception: System.NullReferenceException: Object reference not set to an instance of an object.     at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.SetPropertiesOnQueryReader()     at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.OnInit(EventArgs e) System.NullReferenceException: Object reference not set to an instance of an object.     at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.SetPropertiesOnQueryReader()     at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.OnInit(EventArgs e)               7001a8bf-b506-4096-b46b-003fbb5ec91b

01/28/2015 10:59:51.10         w3wp.exe (0x31D8)                0x2030    SharePoint Server  Unified Logging Service       c91s        Monitorable                Watson bucket parameters: SharePoint Server 2010, ULSException14, 06175311 "sharepoint server search", 0e001b67 "14.0.7015.0", 17853a8f "microsoft.office.server.search", 0e001bd1 "14.0.7121.0", 531f1826 "tue mar 11 10:05:26 2014", 000032a4 "000032a4", 0000002d "0000002d", 4a6d3421 "nullreferenceexception", 67316a39 "g1j9"    7001a8bf-b506-4096-b46b-003fbb5ec91b

Solution 1

If you go into Central Administration -> System Settings -> Manage Services on Server. Make sure the below services are started.

- SharePoint Server Search

- Search Query and Site Settings Service

Solution 2

Click through all the Search Administration pages in Central Admin.Click through all the Search Administration pages in Central Admin. Now perform the search again. The issue should have disappeared.

Solution 3

Identify the underlying application pool for search (Reference)

Perform an application pool recycle

SharePoint Crawled Properties and Managed Properties

Last year, when I had an interview, I was asked the difference between crawled property and managed property. Though I have come across this multiple times and even after working on Search Project, I could not give a satisfactory answer.(honestly ,even for me the answer was not satisfactory)

So what is Crawled Property and Managed Property in SharePoint ???

Crawled Properties and Managed Properties are very basic SharePoint concepts but they are building elements of SharePoint Search. Below is an example which might help you understand this in a better way.

SharePoint crawls data from different sources. The data in these various source systems have metadata which can have different names but it refers to the same information.

As an example different systems can store the information about the Author in various systems with the name as :

Author

Created By

Writer

Owner

and in case of emails it is stored in field From.

But all these fields represent the same information which represent who has created this.

Now when SharePoint crawl these various systems , all these properties become Crawled Properties.

In SharePoint we can group all these Crawled Properties under one Managed Properties.

The below image is a pictorial representation of what I said above.

Note

One crawled property can be part of multiple Managed Properties.

Managed property can be used in scopes, refiners..etc.

How to create a SharePoint State Service application through PowerShell

If you configure the SharePoint service applications manually and not run the configuration wizard, you will miss creating the State Service Application as it is not listed down as a service application option in Central Administration -> Manage Service applications page. ( This Service Application is not available for creation in the New dialog in Central Administration, Manage Service Application)

So it should be created through PowerShell. Below are the commands to create one :

$serviceApp = New-SPStateServiceApplication -Name "State Service Application"

New-SPStateServiceDatabase -Name "SharePoint_Service_State" -ServiceApplication $serviceApp

New-SPStateServiceApplicationProxy -Name "State Service Application Proxy" -ServiceApplication $serviceApp -DefaultProxyGroup

Related Post

SharePoint Search Service Application Creation through PowerShell

Search service Application can be created and configured through Central Administration and PowerShell as well. The below commands creates the Search Service Application and the associated databases.Further configuration can be done from Central Administration. The main purpose of doing this is to create search related databases without GUID’s.

$SSADB = "SearchDB”

$SSAName = "Search Service Application"

$SVCAcct = "Domain\UserName"

$SSI = Get-SPEnterpriseSearchServiceInstance -local

1. Start Services search services for SSI

Start-SPEnterpriseSearchServiceInstance -Identity $SSI

2. Create an Application Pool.

$AppPool = New-SPServiceApplicationPool -Name $SSAName" AppPool" -account $SVCAcct

3. Create the SearchApplication and set it to a variable

$SearchApp = New-SPEnterpriseSearchServiceApplication -Name $SSAName -Applicationpool $AppPool -DatabaseName $SSADB

4. Create search service application proxy

$SSAProxy = New-SPEnterpriseSearchServiceApplicationProxy -Name $SSAName" ApplicationProxy" -Uri $SearchApp.Uri.AbsoluteURI

5. Provision Search Admin Component.

Set-SPEnterpriseSearchAdministrationComponent -SearchApplication $SearchApp -SearchServiceInstance $SSI

The database names would be as below by running the above PowerShell.

Administration Database: SearchDB

Crawl Database: SearchDB_CrawlStore

Property Database: SearchDB_PropertyStore

How to create a SharePoint Usage and Health Data Collection Service Application through PowerShell

Usage and Health Data Collection Service Application collects Data about Usage and Health of your farm. This information is used for Health Monitoring and this is also required for running the Web Analytics Service. If you do not have a Usage and Health Data Collection Service Application or your Usage and Health Data Collection Proxy is stopped, you will not see any data in the Web Analytics Report.

You cannot create Usage and Health Data Collection Service Application from Central Admnistration.

You have to use PowerShell for this :

New-SPUsageApplication -Name “UsageAppName” -DatabaseServer “DBServerName” -DatabaseName “DBName”

$Usage = Get-SPServiceApplicationProxy | where {$_.TypeName -eq “Usage and Health Data Collection Proxy”}

$Usage.provision()

More information

An exception occurred when trying to issue security token: The HTTP service located at http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc/actas is too busy.

There was an unexpected server reboot for our applications server and our service application features were failing. On checking, I noticed the below error in the Windows Event Viewer

Event ID: 8306

An exception occurred when trying to issue security token: The HTTP service located at http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc/actas is too busy.

On browsing to http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc ,  I got the below error

Fix

Identify the application pool for the Service Applications.

Application Pool -> Check Status -> Start