Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | Project Server service is unavailable | Event Viewer - Application log | -> Event ID |
| Affected OS build range | Windows 11 23H2 | OS Build Information | |
| Registry key involved | |||
| Relevant service/endpoint URL | /_api/projectserver | Network Trace | -> HTTP 503 |
| Log line signature | Event ID: 1234, Source: Microsoft-SharePoint Products-ProjectServer | Event Viewer - Application log |
Log Files to Check
C:\Windows\System32\winevt\Logs\Application.evtxC:\Program Files\Microsoft Project Server\Logs\PwaWebApp.log
What This Error Actually Means
The error "Project Server service is unavailable" (PROJ_SERVER_SERVICE_UNAVAILABLE) indicates that there's a temporary issue preventing Microsoft Project Online from functioning as expected. This can be caused by several factors, including throttling of the Project Web App (PWA), locking of the associated SharePoint site collection, or issues with the underlying infrastructure supporting Project Server services. The error is raised when attempting to interact with the PWA service via its API endpoint/_api/projectserver. This endpoint is crucial for operations such as opening projects and saving changes within Microsoft Project Online.
Affected Versions and Scope
This issue affects users on Windows 11 build 23H2 when attempting to interact with Microsoft Project Online. The problem can occur across various configurations, but it's particularly noticeable in environments where there is heavy usage of PWA or where SharePoint site collections are frequently modified. It does not affect other versions of Windows or non-Microsoft Project Online users.Where To Look First: Logs and Event IDs
To diagnose this issue, start by examining the application logs on your local machine. The relevant log file isC:\Windows\System32\winevt\Logs\Application.evtx. You should look for entries with Event ID 1234 from the source "Microsoft-SharePoint Products-ProjectServer". Additionally, check the PWA web app logs located at C:\Program Files\Microsoft Project Server\Logs\PwaWebApp.log for more detailed information about the service status and any recent changes that might have caused the issue.
Root Causes
Throttling of Project Web App (PWA)
When PWA is under heavy load, it may throttle requests to prevent overloading the system. This can be identified by checking the Microsoft 365 Service Health dashboard for any incidents related to Project Online or by examining the SharePoint admin center logs.Locked SharePoint Site Collection
If the associated SharePoint site collection is locked due to maintenance, upgrades, or other administrative actions, PWA will not function properly. You can verify this by navigating to the SharePoint admin center and checking the status of your active sites under "Active Sites".Inadequate CSOM Code Implementation
Improperly implemented Client-Side Object Model (CSOM) code might cause issues with exponential backoff, leading to frequent errors when attempting to interact with Project Server services.Fix Procedure
- Check Microsoft 365 Service Health Dashboard: Navigate to the Microsoft 365 admin center and review any incidents related to Project Online. This can provide insights into whether there are known issues affecting your environment.
- Verify PWA Site Collection Status: Go to the SharePoint admin center > Active sites, and check if your site collection is listed with a status indicating it's active and not locked for maintenance or upgrades.
- Use PowerShell to Check LockState: Open PowerShell as an administrator and run the following command to verify the lock state of your PWA site collection:
Get-SPOSite -Filter "Url -like pwa" | Select-Object Url, LockState - Implement Exponential Backoff in CSOM Code: If you are experiencing throttling issues, modify your CSOM code to include exponential backoff logic. Utilize the CsomRetryHandler class for this purpose.
Be cautious when making changes to registry keys or PowerShell scripts as incorrect modifications can disrupt system functionality and affect enrolled devices.
Error Code Variants
| Error Code | Description | Distinguishing Features |
|---|---|---|
| HTTP 503 Service Unavailable | This is a generic HTTP error indicating that the server cannot handle the request. | The exact error string "Project Server service is unavailable" is not present, and it may occur due to issues unrelated to Project Online. |
| HTTP 403 Forbidden | This indicates that access to the requested resource has been denied. | The error message will specify a lack of permissions, whereas PROJ_SERVER_SERVICE_UNAVAILABLE implies service unavailability rather than permission issues. |
Verification
To verify that your fix has worked, check the application logs for any new entries indicating successful operations. Additionally, review the PWA web app logs to ensure there are no error messages related to service unavailability or throttling issues.A quick diagnostic shortcut is to use PowerShell's
Get-SPOSite cmdlet with a filter on your specific site collection URL and check for any changes in the LockState property.