Others

How to Find the Record Causing a Project Online Publish Failure

Ayan Masood Sep 27, 2026 869 views

Question details

The user needs to identify the exact problematic record or corrupted data causing publish failures (Errors 23000 and 26000) in Project Online.

How to Find the Record Causing a Project Online Publish Failure

Product: Project Online
Device & OS: not provided
Scenario: Publishing projects in Project Online results in errors 23000 or 26000.
Observed behavior: The project fails to publish and throws Error 23000 or 26000. The standard queue view does not specify which exact record is corrupted or orphaned.

Before you start

Ensure you have administrator access to Project Web App (PWA) settings and verify your network connection before attempting to troubleshoot the publish queue.

Solution 1Recommended

Check Out Enterprise Objects and Save as a New Project

Identify checked-out objects and bypass corruption by saving your project data into a new file.

Because Error 23000 and 26000 can have multiple root causes, the standard queue view may not identify the exact corrupted record. Saving the project as a new file can often bypass hidden corruption.

Check PWA Settings

Go to PWA Settings > Force Check-in Enterprise Objects to determine whether projects or other objects are checked out.

Review Queue Jobs

Navigate to PWA Settings > My Queued Jobs to check the publish status and look for specific failure details or JobUIDs.

Save as New Project

Open the affected project in the Project application, verify your assignments and resources, and use the 'Save As' function to create a completely new project.

Publish the New Project

Attempt to publish the newly saved project. If this works, the original project file likely contained a corrupted or orphaned record.

Tip: Thoroughly verify resources and assignments before saving as a new project to ensure corrupted objects aren't carried over.

Solution 2

Escalate to Microsoft Support for Orphaned Records

If errors persist due to deep-level orphaned records, Microsoft Support intervention is required to clear them.

Free Microsoft Office alternative

Try WPS Office for Seamless Project Documentation and Management

While WPS Office does not directly replace Microsoft Project Online, it offers a robust, lightweight, and entirely free suite for managing project documentation, spreadsheets, and presentations without complex cloud publishing errors.

Highly compatible with Microsoft Office formats, including DOCX, XLSX, and PPTX.Easily track project tasks, budgets, and timelines using versatile WPS Spreadsheet templates.Lightweight software that installs quickly and runs smoothly on standard devices.Completely free to download and use with a familiar, user-friendly interface.

microsoft office alternative - wps office

Frequently Asked Questions

What does Error 23000 mean in Project Online?

Error 23000 (ProjectPublishFailure) indicates that there is a problem publishing the project to the server. This is often caused by corrupted project data, invalid resource assignments, or orphaned records that the system cannot process.

Can I find the exact corrupted record in the standard queue view?

No, the standard queue view in Project Online usually does not identify the exact problematic record for errors 23000 and 26000. It typically points to ULS logs or provides a generic JobUID, which requires further investigation or Microsoft Support to diagnose.

How do I check my publish status in PWA?

You can check your publish status by navigating to PWA Settings and selecting 'My Queued Jobs'. This section displays the status of recent jobs, though be aware that this view cannot be directly exported.

Why do I need Microsoft Support for orphaned records?

Orphaned records are disconnected data fragments in the server database. Standard users and administrators often cannot see or clear these manually from the PWA front end, requiring a Microsoft representative to identify and clear them directly from the backend.

Office Quick Solutions