'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Project Web App Publishing Errors 24016, 24017, and 26000
Question details
The user needs to resolve publishing failures in Project Web App involving specific synchronization and queue job error codes.
- Product
- Microsoft Project Web App
- Device & OS
- not provided
- Scenario
- Publishing projects from Project Desktop to Project Web App.
- Observed behavior
- Projects save successfully but fail during publishing, returning ReportingGetSPWebFailed, ReportingWSSSyncMessageFailed, and GeneralQueueJobFailed errors.
Ensure you have the exact project names, error codes, and error timestamps documented, as your IT administrator will need these details to escalate the issue.
Open a Support Request in the Microsoft 365 Admin Center
Because these errors require backend tenant and queue-log analysis, the issue must be escalated to Microsoft Support by a tenant administrator.
Errors 24016, 24017, and 26000 are related to SharePoint synchronization and Security Token Service failures. Since they require deep investigation of the tenant environment and queue logs, end-users cannot resolve them directly.
Provide your tenant administrator or IT team with the specific project names that are failing to publish and the exact error codes (24016, 24017, or 26000).
Have the administrator sign in to the Microsoft 365 Admin Center using their admin credentials.
Navigate to the 'Support' or 'Help & support' section in the admin portal to open a new support ticket.
Include the collected project details and mention the failed queue jobs (ReportingGetSPWebFailed, ReportingWSSSyncMessageFailed, GeneralQueueJobFailed) so Microsoft Support can investigate the tenant configuration.
Experience a Seamless and Lightweight Office Solution with WPS Office
If complex backend syncing issues in Microsoft 365 disrupt your daily workflow, consider trying WPS Office for your standard documentation needs. It provides a lightweight, highly compatible, and user-friendly environment for managing all your Word, Excel, and PowerPoint files without the heavy enterprise overhead.
- 1. Download WPS Office: Visit the official WPS website and download the free installation package for your operating system.
- 2. Install the Application: Run the installer and follow the on-screen prompts to set up WPS Office on your device.
- 3. Open and Edit Files: Launch WPS Office to instantly open, edit, and save your existing Microsoft Office files with full compatibility.
Frequently Asked Questions
What does error 24016 mean in Project Web App?
Error 24016 generally points to a ReportingGetSPWebFailed event, which means the system encountered an error retrieving SharePoint web data during the sync process. This is typically caused by a backend configuration or token issue.
Can I fix Project Web App error 26000 on my own?
No, error 26000 (GeneralQueueJobFailed) indicates a failure in the backend queue processing. You must contact your Microsoft 365 tenant administrator to investigate the server logs or open a Microsoft Support ticket.
Why do my projects save successfully but fail to publish?
Saving a project updates the draft database without immediately triggering full SharePoint synchronization. Publishing attempts to update the published database and sync with SharePoint workspaces, which is where synchronization and Security Token Service errors typically occur.
