OpenUtilities Wiki Error - No version resource could be located in database

Error - No version resource could be located in database

	Product(s):	promis.e, Bentley Substation
	Version(s):	through 08.11.12.137
	Environment:	N/A
	Area:	Database Platform Support
	Subarea:	N/A

Error or Warning Message

"Configuration not saved: No version resource could be located in database. Project schema is invalid" appears on the Setup dialog.

Explanation

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.

This message can also occur if no database is specified for the Database or Default Database field on Setup > Project Database.

How to Avoid

Ensure a valid database is specified in the Database or Default Database field on Setup > Project Database.

Verifying Version with SQL Server

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. Note: While this dialog can also be used to add or modify a property, DO NOT change the version number here in an attempt to "upgrade" or "downgrade" the database schema.

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, see Minimum SQL user permissions. In one case, the login had the "public" role assigned but not "db_owner" for the database in question.

If the Version property does not exist or has an incorrect value, execute the script that updates the database schema. See the "Update the Database Method 2: Executing a Script" section in Creating and Updating the Project Database.

Verifying Version with Oracle

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. Note: DO NOT change the version number here in an attempt to "upgrade" or "downgrade" the database schema.

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.

If the comment on the Project table does not exist or has an incorrect value, execute the script that updates the database schema. See the "Update the Database Method 2: Executing a Script" section in Creating and Updating the Project Database.