Contents
Are there any error codes for Project Server?
For example, because the ExchangeSync and PWA web services are not supported for third-party development, you are not likely to see error codes from methods in those areas, such as the Rules and StatusReports methods. However, tables in this article include all Project Server error codes for completeness. Table 1.
Is the project psi web service still supported?
In the Internet Information Services (IIS) Manager window, expand the SharePoint Web Services node, choose the GUID directory name, and then choose Advanced Settings to copy the Virtual Path value. The ASMX web service interface of the PSI is deprecated in Project Server 2013, but is still supported.
Where can I find documentation for project psi?
This article is an overview of the documented assemblies, namespaces, and services in the PSI. The Project Server 2013 class library and web service reference in the SDK contains all of the managed code documentation for the PSI and the Microsoft.ProjectServer.Client namespace in Project Server 2013.
Do you need psi for Microsoft Project online?
To develop applications for Project Online, you must use the Microsoft.ProjectServer.Client namespace instead of the PSI. The PSI in Project Server 2013 has a dual interface.
Where do I find the error code for my API?
One strategy might be to call attention to any particularly relevant status or error codes for a specific endpoint, and then link to the centralized “Response and Status Codes” page for full information. Status and error codes may not be readily apparent when you’re documenting your API.
What is the error code for operations per second?
Operations per second is over the account limit. One of the HTTP headers specified in the request is not supported. One of the XML nodes specified in the request body is not supported. One of the query parameters specified in the request URI is not supported. The resource doesn’t support the specified HTTP verb.
What should be included in an API response page?
Most APIs should have a general page listing response and error codes across the entire API. A standalone page listing the status codes (rather than including these status codes with each endpoint) allows you to expand on each code with more detail without crowding the other documentation.
https://www.youtube.com/watch?v=l0AAQcx-l9U