Ever had Primavera P6 crash so hard that you couldn’t even log back in? I recently hit a “pm.exe – Insufficient Resources” error in Version 18 (SQLite) while working on a project with 5,000+ activities.
The culprit? A heavy layout combining stacked histograms with personalized collapsed bars for individual tasks. The graphics engine hit a wall, and because P6 tries to reload your last state on startup, I was locked out.
Here is the “Safe & Nuclear” workflow I used to get back in without losing data:
🛠 The Recovery Workflow
1. Create a Safety Net Don’t experiment on your primary file. Locate your SQLite .db file, make a copy, and rename it (e.g., Project_Fixed.db). We will perform the repair on this copy.
2. The “Nuclear” Database Reset P6 “remembers” the crash in its internal tables. To wipe that memory:
- Open the new copy in DB Browser for SQLite.
- In the Execute SQL tab, run:
DELETE FROM USERDATA; - This resets your session flags (last project, last layout) but keeps all your schedule data intact.
- Crucial: Click Write Changes before closing.
3. The Clean Login
- Point P6 to your new, cleaned database.
- Hold the SHIFT key while clicking Login. This forces P6 to ignore any cached layout settings and open to a default, blank view.
4. Kill the Corrupt Layout Once you are back in:
- Go to Layout > Open.
- Find the layout that caused the crash and delete it immediately.
- Rebuild a simplified version—don’t try to “fix” the old one!
💡 Pro-Tip for Large Schedules
If you’re managing 5,000+ activities on SQLite, avoid combining heavy graphical overrides (like custom collapsed bars) with resource histograms. SQLite is great for portability, but it lacks the heavy-duty processing of SQL Server for complex graphical “exception” rules.
Filter your data before turning on histograms to keep the memory load low!
#PrimaveraP6 #ProjectControls #Scheduling #Planning #P6Tips #ProjectManagement #SQLite
Join our community on skool for real project support: