Share via

Test-SPProjectServiceApplication

Module:
SharePointServer module

This cmdlet runs a series of health checks against the Project Service Application.

Syntax

Default (Default) 

Test-SPProjectServiceApplication
    [-Identity] <PsiServiceApplicationPipeBind>
    [[-Rule] <ProjectServiceApplicationHealthRuleName>]
    [-AssignmentCollection <SPAssignmentCollection>]
    [<CommonParameters>]

Description

This cmdlet runs a series of health checks against the Project Service Application.

Examples

EXAMPLE

$sa = Get-SPServiceApplication | ?{$_.TypeName -eq 'Project Application Services'}
Test-SPProjectServiceApplication -Identity $sa

This example runs all health checks again the service application named "Project Service Application."

Parameters

-AssignmentCollection

Applicable: Project Server 2013, Project Server 2016, Project Server 2019

Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.

When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur.

Parameter properties

Type:SPAssignmentCollection
Default value:None
Supports wildcards:False
DontShow:False

Parameter sets

(All)
Position:Named
Mandatory:False
Value from pipeline:True
Value from pipeline by property name:False
Value from remaining arguments:False

-Identity

Applicable: Project Server 2013, Project Server 2016, Project Server 2019

The name of the Project Service Application to test against.

Parameter properties

Type:PsiServiceApplicationPipeBind
Default value:None
Supports wildcards:False
DontShow:False

Parameter sets

(All)
Position:0
Mandatory:True
Value from pipeline:True
Value from pipeline by property name:False
Value from remaining arguments:False

-Rule

Applicable: Project Server 2013, Project Server 2016, Project Server 2019

Which rule to run against the service application.

Valid rules are:

All, CalcServiceWorkerState, QueueInFlightJobs, QueueServiceInternalState

Project Server 2013 has this additional rule which is not available in Project Server 2016, Project Server 2019:

QueueSiteCheck

Project Server 2016, Project Server 2019 added this additional rule:

DatabasePermissions

Parameter properties

Type:ProjectServiceApplicationHealthRuleName
Default value:None
Accepted values:All, QueueServiceInternalState, QueueInFlightJobs, CalcServiceWorkerState, DatabasePermissions
Supports wildcards:False
DontShow:False

Parameter sets

(All)
Position:1
Mandatory:False
Value from pipeline:True
Value from pipeline by property name:False
Value from remaining arguments:False

CommonParameters

This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -ProgressAction, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters.

Inputs

Microsoft.Office.Project.Server.Cmdlet.PsiServiceApplicationPipeBind

Microsoft.Office.Project.Server.HealthRules.ProjectServiceApplicationHealthRuleName Microsoft.SharePoint.PowerShell.SPAssignmentCollection

Outputs

System.Object