You are currently reviewing an older revision of this page.
"Configuration not saved: No version resource could be located in database. Project schema is invalid" appears on the Setup dialog.
This message indicates that the Version extended property of the Project table in the SQL Server project database being used is missing or cannot be read.
If using Oracle for the project database, the message indicates that the comment on the "Project" table is missing or cannot be read.
The Version property/comment may actually be correct on the server but cannot be read by the login being used.
Connect to the server using SQL Server Management Studio (SSMS).
In SSMS, drill down in the Object Explorer tree view into Databases > (your database name) > Tables
Right click the dbo.Project table and select "Properties".
On the Extended Properties page there should be properties called "ShortProductName" and "Version". For the software to accept the database, the value of "Version" must match the value expected. See Project Database Version - promis.e and Project Database Version - Substation.
If the Version property exists and the value is correct, ensure the correct database is being examined and that promis•e/Bentley Substation is pointing to that database on Setup. If so, check the permissions of the login being used.
Check for the presence of a comment on the "Project" table of the database. It should have a value that matches the version number according to Project Database Version - promis.e or Project Database Version - Substation.
If the comment on the Project table exists and the value is correct, ensure the correct database is being examined and that promis•e/Bentley Substation is pointing to that database on Setup. If so, check the permissions of the login being used.
Creating and Updating the Project Database
Project Database Version - promis.e
Project Database Version - Substation
SELECTsupport TechNotes and FAQs