Ignoring Non-Fatal Errors when Upgrading a Database

When upgrading your database to a new Archibus version and merging your database with a later database definition from Archibus, you may find that the Web Central startup process halts because of bad items in the database.

For instance, the following will cause the Web Central startup process to halt:

• a malformed workflow rule
• a table that has no fields
• a table has incorrect primary keys
• a field has a bad enumeration list

Since the startup process does not complete, you cannot fix the issue because you cannot load Web Central or the Smart Client to access the tables causing the problems.

To enable the startup process to continue when it finds errors:

1. Set the following in core.properites:
   • core.ignoreNonFatalErrorsOnStartup=true
2. You must also set the following: 
   • core.runScheduledRules=false
   • preloadTableDefs="false"

Note: This setting is a convenience for upgrading schema. Never set core.ignoreNonFatalErrorsOnStartup=true in production.