SharePoint Server or Project Server Patch Installed Patch Missing

Description

After installing a SharePoint Server or Project Server Service Pack or Cumulative Update, the Configuration Wizard shows that the Patch is missing from servers in the farm.  In this case, the Configuration Wizard on Server 1 is showing that the Project Server 2013 SP1 Patch is missing, yet it was already installed.

Error:  Some farm products and patches were not detected on this or other servers.  If products or patches are missing locally, you must quit this program and install the required products and patches on this server before restarting this wizard.  If products or patches are missing on other servers, you must install the required products and patches on the specific servers, and you may then click the Refresh button to perform the status check again.

Attempting to run the Project Server 2013 SP1 Patch installation again from the .exe verifies that the Patch is already installed on the system.  Herein lies the problem.  On one hand, the Configuration Wizard will not run because it thinks the patch is missing.  On the other hand, it is not possible to install the patch because it is already installed on local server.  Patch installed, patch missing, patch installed, patch missing.

Solution

The solution to this problem is to run a PowerShell cmdlet on each of the servers that the Configuration Wizard is reporting, patch missing.

1.  Log into the SharePoint Server

2.  Open the SharePoint Management Shell as Administrator

3.  Get-SPProduct -local

This cmdlet retrieves a list of the SharePoint-related products installed in the farm.  It also retrieves the version information for updates installed.  Using the -Local switch retrieves information for local server only.

It may take some time for the cmdlet to run, but once it completes on the servers, you can do a refresh on the Configuration Wizard and the Configuration will recognize that the patches are, in fact, installed on the servers and it will advance automatically to the next screen.  You can continue run the Configuration Wizard upgrade procedure.

References

Microsoft TechNet (May, 2010).  Document farm configuration settings (SharePoint Foundation 2010).  Retrieved March 3, 2014 from http://technet.microsoft.com/en-us/library/ff645390%28v=office.14%29.aspx

Microsoft TechNet (January, 2014).  Document farm configuration settings in SharePoint 2013.  Retrieved March 3, 2014 from http://technet.microsoft.com/en-us/library/ff645391.aspx

Microsoft TechNet (July, 2012).  Get-SPProduct.  Retrieved March 3, 2014 from http://technet.microsoft.com/en-us/library/ff607885.aspx

SharePoint 2013: How to Configure the Metadata Service Application using PowerShell

Description

This post describes how to configure the SharePoint Server 2013 Metadata Service Application using PowerShell.


Solution

1)  Document the Naming Convention
Determine a naming convention for each of the Service Application components.  Document the naming convention.

Application Pool: SvcApp_SPServiceApplicationPool_01
Application Pool Service Account:  Domain\SvcAccount
Application:  SvcApp_SPMetadataServiceApplication_01
Proxy:  SvcApp_SPMetadataServiceApplication_01_Proxy_01  
Database: SvcApp_SPMetadataServiceApplication_01_DB_01

2)  Prepare the Application Pool / Service Account
Example: Subscription Settings Application Pool: SvcApp_SPServiceApplicationPool_01 Application Pool Service Account:  Domain\SvcAccount

A) If you are using an existing application pool:
You do not need to create a Service Account nor an Application Pool.  Note the names of each.

Verify Application Pool.
Get-SPServiceApplicationPool | Select Name

Get the existing Application Pool.
$SvcAppPool = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_01"

B) If you are creating a new application pool:
Determine which service account you will use to run the application pool that will be assigned to the.  If you need to, create and register a service account to run the Subscription Settings Service Application.

Create the Service Application Pool and register it to the Service Account.
$SvcAppPool = New-SPServiceApplicationPool -Name "SvcApp_SPServiceApplicationPool_01"$AppPool = New-SPServiceApplicationPool -Account (Get-SPManagedAccount Domain\SvcAccount)

Verify Application Pool.
Get-SPServiceApplicationPool | Select Name

Get the existing Application Pool.
$SvcAppPool = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_01"

3)  Open the SharePoint 2013 Management Shell as Administrator.

4)  Create the Service Application and assign it to the Application Pool.
$SvcApp = New-SPMetadataServiceApplication –ApplicationPool $SvcAppPool -Name "SvcApp_SPMetadataServiceApplication_01" -DatabaseName "SvcApp_SPMetadataServiceApplication_01_DB_01"

Verify Service Application.
Get-SPServiceApplication | Select Name

5)  Create the Service Application Proxy and assign it to the Service Application.
$SvcAppProxy = New-SPMetadataServiceApplicationProxy -Name "SvcApp_SPMetadataServiceApplication_01_Proxy_01" -ServiceApplication $SvcApp

Verify Service Application Proxy
Get-SPServiceApplicationProxy | Select Name


References

Microsoft TechNet (2012).  New-SPMetadataServiceApplication.  Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ff607557.aspx.

Microsoft TechNet (2012).  New-SPMetadataServiceApplicationProxy.  Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ff608097.aspx.

Microsoft TechNet (2012).  Service application cmdlets in SharePoint 2013.  Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ee906561.aspx.

Microsoft TechNet (2012).  SharePoint 2013 - Service Applications.  Retrieved January 22, 2014 from http://social.technet.microsoft.com/wiki/contents/articles/12512.sharepoint-2013-service-applications.aspx.

SharePoint 2013: How to Configure the Usage Service Application using PowerShell

Last Updated March 28, 2014  


Description

This post describes how to configure the SharePoint Server 2013 Usage Service Application using PowerShell.


Solution

1)  Plan and Document the Naming Convention.
Document a naming convention for each of the Service Application components.  

Example:
Application Pool Service Account:  Domain\SvcAccount (this should already be created)
Application Pool: SvcApp_SPServiceApplicationPool_02 (this should already be created)
Service Application: SvcApp_SPUsageApplication_01
Service Application Database:  SvcApp_SPUsageApplication_01_DB_01 
Service Application Proxy:  SvcApp_SPUsageApplication_01_Proxy_01

2)  Open the SharePoint 2013 Management Shell. 

3)  Verify the Name of the Application Pool.
Get-SPServiceApplicationPool | Select Name

4)  Get the existing Application Pool.
$SvcAppPool02 = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_02"

5)  Create the Service Application and assign it to the Application Pool.
$SvcApp = New-SPUsageApplication –Name “SvcApp_SPUsageApplication_01” -DatabaseName "SvcApp_SPUsageApplication_01_DB_01" –DatabaseServer “SQL Alias Name” 

The Proxy is created automatically when the New Service Application cmdlet is run.  It does not appear that the name of the Proxy may be set or changed independently for this Service Application at the time of creation.

6)  Verify Service Application.
Get-SPServiceApplication | Select Name 

7) Verify Service Application Proxy.
Get-SPServiceApplicationProxy | Select Name   

8) Get the Usage and Health Data Collection Proxy.
$SvcAppProxy = Get-SPServiceApplicationProxy | Where {$_.TypeName -like “Usage and Health*”}

9) Start the Usage and Health Data Collection Proxy.
$SvcAppProxy.Provision()

References

Microsoft TechNet (2012).  New-SPUsageApplication.  Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ff607699.aspx.

Microsoft TechNet (2012).  Service application cmdlets in SharePoint 2013.  Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ee906561.aspx.

Microsoft TechNet (2012).  SharePoint 2013 - Service Applications.  Retrieved January 22, 2014 from http://social.technet.microsoft.com/wiki/contents/articles/12512.sharepoint-2013-service-applications.aspx.

SharePoint 2013: How to Configure Secure Store Service Application using PowerShell

Last Updated March 28, 2014

Description

This post describes how to configure the SharePoint Server 2013 Secure Store Service Application using PowerShell.

Solution

1)  Document the Naming Convention
Determine a naming convention for each of the Secure Store Service Application components.  Document the naming convention.

Example:
Application Pool Service Account:  Domain\SvcAccount (this should already be created)
Application Pool: SvcApp_SPServiceApplicationPool_02 (this should already be created)
Service Application: SvcApp_SPSecureStoreServiceApplication_01
Database: SvcApp_SPSecureStoreServiceApplication_01_DB_01

Service Application Proxy:  SvcApp_SPSecureStoreServiceApplication_01_Proxy_01

2)  Open the SharePoint 2013 Management Shell as Administrator.

3)  Start the Secure Store Service.
Get-SPServiceInstance | Where {$_.TypeName -like "Secure Store Service"}

Use the Get-SPServiceInstance cmdlet to get the ID Numbers of the SPServiceInstance(s).  Once you have the ID Numbers, use the numbers to start each SPServiceInstance.  Once fully started, the status of each will show as "Online".

Example:
Start-SPServiceInstance 67877d63-bff4-4521-867a-ef4979ba07ce

Start-SPServiceInstance IDNumber1
Start-SPServiceInstance IDNumber2

3)  Verify the Name of the Application Pool.
Get-SPServiceApplicationPool | Select Name

4)  Set the Service Application Pool in a variable.
$SvcAppPool02 = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_02"

5)  Create the Secure Store Service Application.  Specify the Application Pool, the AuditingEnabled setting, the Service Application Name, the Database Name, and the Database Server Name.

$SvcApp = New-SPSecureStoreServiceApplication -ApplicationPool $SvcAppPool –AuditingEnabled:$false -Name "SvcApp_SPSecureStoreServiceApplication_01" -DatabaseName "SvcApp_SPSecureStoreServiceApplication_01_DB_01" -DatabaseServer "SQL Server Alias"
 
6)  Verify the Service Application.
Get-SPServiceApplication | Select Name

7)  Create the Service Application Proxy and assign it to the Service Application.
$SvcAppProxy = New-SPSecureStoreServiceApplicationProxy -Name "SvcApp_SPSecureStoreServiceApplication_01_Proxy_01" -ServiceApplication $SvcApp

8)  Verify Service Application Proxy.
Get-SPServiceApplicationProxy | Select Name

References

Farid, S. (2011).  Configure Secure Store Service using PowerShell.  Retrieved January 22, 2014 from http://samirfarid.wordpress.com/2011/11/28/configure-secure-store-service-using-powershell.

Microsoft TechNet (2014).  Configure the Secure Store Service in SharePoint 2013.   Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ee806866.aspx.

Microsoft TechNet (2014).  New-SPSecureStoreServiceApplication.  Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ff608083.aspx.

Microsoft TechNet (2014).  New-SPSecureStoreServiceApplicationProxy.  Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ff607856.aspx.

Microsoft TechNet (2014).  Secure Store Service cmdlets in SharePoint 2013.  Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ee906549.aspx.

Microsoft TechNet (2014).  Service application cmdlets in SharePoint 2013.  Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ee906561.aspx.

Microsoft TechNet (2014).  SharePoint 2013 - Service Applications.  Retrieved January 22, 2014 from http://social.technet.microsoft.com/wiki/contents/articles/12512.sharepoint-2013-service-applications.aspx.

SharePoint 2013: How to Configure Subscription Settings Service Application using PowerShell

Last Updated March 28, 2014



Description

This post describes how to configure the SharePoint Server 2013 Subscription Settings Service Application using PowerShell.

Solution

1)  Document the Naming Convention






Document a naming convention for each of the Subscription Settings Service Application components.

Example:
Application Pool Service Account:  Domain\SvcAccount (this should already be created)
Application Pool: SvcApp_SPServiceApplicationPool_03 (this should already be created)
Service Application: SvcApp_SPSubscriptionSettingsServiceApplication_01
Service Application Database: SvcApp_SPSubscriptionSettingsServiceApplication_01_DB_01 
Service Application Proxy:  The Proxy is named automatically by SharePoint 

2)  Open the SharePoint 2013 Management Shell as Administrator.

3)  Verify the Name of the Application Pool.
PS C:\ Get-SPServiceApplicationPool | Select Name

4)  Set the Service Application Pool in a variable.
$SvcAppPool03 = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_03"

5)  Create the Service Application and assign it to the Application Pool.
$SvcApp = New-SPSubscriptionSettingsServiceApplication -ApplicationPool $SvcAppPool03 -Name "SvcApp_SPSubscriptionSettingsServiceApplication_01" -DatabaseName "SvcApp_SPSubscriptionSettingsServiceApplication_01_DB_01" -DatabaseServer "MSSQL Client Alias"
 
6)  Verify the Service Application.
PS C:\ Get-SPServiceApplication | Select Name

5)  Create the Service Application Proxy and assign it to the Service Application.
$SvcAppProxy = New-SPSubscriptionSettingsServiceApplicationProxy -ServiceApplication $SvcApp

It does not appear that the name of the Proxy can be set using the cmdlet.  SharePoint will name the Proxy automatically.

7)  Verify Service Application Proxy.
PS C:\ Get-SPServiceApplicationProxy | Select Name

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


References

Microsoft TechNet (2012).  New-SPSubscriptionSettingsServiceApplication.  Retrieved November 27, 2012 from http://technet.microsoft.com/en-us/library/ff607823.aspx.

Microsoft TechNet (2012).  Service application cmdlets in SharePoint 2013.  Retrieved November 27, 2012 from http://technet.microsoft.com/en-us/library/ee906561.aspx.

Microsoft TechNet (2012).  SharePoint 2013 - Service Applications.  Retrieved November 27, 2012 from http://social.technet.microsoft.com/wiki/contents/articles/12512.sharepoint-2013-service-applications.aspx.

SharePoint 2013: How to Configure State Service Application using PowerShell

Last Updated March 28, 2014 

Description

This post describes how to configure the SharePoint Server 2013 State Service Application using PowerShell.

Solution

1)  Document the Naming Convention.
Document a naming convention for each of the State Service Application components.

Example:
Application Pool Service Account:  Domain\SvcAccount (this should already be created)
Application Pool: SvcApp_SPServiceApplicationPool_02 (this should already be created)
Service Application:  SvcApp_SPStateServiceApplication_01

Service Application Database:  SvcApp_SPStateServiceApplication_01_DB_01

Service Application Proxy:  SvcApp_SPStateServiceApplication_01_Proxy_01

2)  Open the SharePoint 2013 Management Shell as Administrator.

3)  Verify the Name of the Application Pool.
Get-SPServiceApplicationPool | Select Name

4)  Set the Service Application Pool in a variable.
$SvcAppPool02 = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_02"

5)  Create the Service Application and assign it to the Application Pool. 

New-SPStateServiceDatabase -Name SvcApp_SPStateServiceApplication_01_DB_01 | New-SPStateServiceApplication -Name SvcApp_SPStateServiceApplication_01 | New-SPStateServiceApplicationProxy -Name SvcApp_SPStateServiceApplication_01_Proxy_01 | -DefaultProxyGroup

6) Verify State Service Application.
Get-SPStateServiceApplication | Select Name

7)  Verify State Service Database.
Get-SPStateServiceDatabase | Select Name

9) Verify State Service Application Proxy.
Get-SPStateServiceApplicationProxy | Select Name


References

Microsoft TechNet (2012).  New-SPStateServiceApplication.  Retrieved November 27, 2012 from http://technet.microsoft.com/en-us/library/ff608084.aspx.

Microsoft TechNet (2012).  Service application cmdlets in SharePoint 2013.  Retrieved November 27, 2012 from http://technet.microsoft.com/en-us/library/ee906561.aspx.

Microsoft TechNet (2012).  SharePoint 2013 - Service Applications.  Retrieved November 27, 2012 from http://social.technet.microsoft.com/wiki/contents/articles/12512.sharepoint-2013-service-applications.aspx.

Microsoft TechNet (2012).  State service and session state cmdlets in SharePoint 2013.  Retrieved November 27, 2012 from http://technet.microsoft.com/en-us/library/ee890113.aspx.