KrisAxUserX13 Posted 14 hours ago Share Posted 14 hours ago I was knocked me out of version X13 with the below error. I deleted all of my files and reinstalled Chief Arch and I STILL get this error... It has something to do with a corrupted file? Complete note is: "Assertion failed: A serious error occurred. Do not save the file in its current state. If you want to try saving your work, use Save As to create a new file. Please restart the program and contact Technical Support. C:\p4sync\dev\Releases\23\chief\source\ChiefQtApplication.cpp(259): Error #272000999 "A serious error occurred. Do not save the file in its current state. If you want to try saving your work, use Save As to create a new file. Please restart the program and contact Technical Support." 4/16/2026 12:01:20 PM Build: 23.4.1.8x64" Any thoughts out there? Thanks!! Link to comment Share on other sites More sharing options...
para-CAD Posted 14 hours ago Share Posted 14 hours ago That's a tech support issue. Those guys are really good at solving such problems. Link to comment Share on other sites More sharing options...
CarrieS Posted 12 hours ago Share Posted 12 hours ago The 999 error is a generic "something weird happened" type of error that doesn't have a specific cause. It could be related to an object in the plan, geometry on how something is coming together wrong, or even system requirements like graphics or available space. I recommend starting with updating your graphics driver (use a "clean install" or "factory reset" option which is frequently listed under a custom install setting in the driver install wizard). Chief is so dependent on the GPU that updating the graphics driver fixes a ton of stuff. Be sure to reboot after updating. Windows updates and GPU updated can work in tandem so be sure to verify Windows updates are installed as well if you're on PC. It is generally easy to determine if a problem is plan specific, open up a new plan or other plans and see if you get the same error when doing the same actions. If it is plan specific, save off a copy of the plan and start deleting things until the error goes away and then reverse engineer until the culprit is found. (Edit> Delete Objects is useful for this) Another thing to try is seeing if you get the same error in the trial version of the latest release. Then you'd know if it was something Chief Architect had encountered before and patched. Also, just so expectations are clear, your version falls under paid support. If you end up calling Tech Support, they may need to set up a paid incident before digging in. The steps above are the same ones we’d start with on a call, so trying them first can often save you that cost. Carrie 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now