Find Answers

Filter Search Results

Ask a Question

Example: "Database could not be verified"

Pages [Next]

Results

OE database fails to upgrade: Tomcat server startup timed out

After upgrading to SBM 11.x from 10.x and older, the Configurator is unable to complete the orchestration engine database upgrade .

Upgrade to 11.0.1 - Configurator hung on OE DB even though no orchestrations - had to update DB manually

While upgrading to 11.0.1 and Configurator hung on the OE upgrade . There were no orchestrations and logs seemed to indicate all was completed.

How can I make Configurator ask to do the Orchestration Engine database upgrade again after I chose to stop showing warnings?

Run the following sql command against the Orchestration Engine database update OE _SETTING set SETTING_VALUE='' where ID = 1 (note the above query contains two single quotes ( ' ), not a double quote)

OE upgrade fails for SQL Server on SSL

d. Make sure SBM is setup to connect to the database using SSL. Then, go to a command prompt and run the following commands.

Failed to upgrade Orchestration Engine Database. The specified user is invalid....when the password being used has an &

The strange part is everything else in the entire product works with this password just not the upgrade in configurator. As a workaround do the upgrade of the OE database with a username password combo with no ampersand &.

Upgrading database on SQL Server 7

Database Upgrade -- SBM Upgrade Fails

Upgrade database button is not available in Configurator

Upgrading to SBM 11.x: About the Orchestration Engine Database Upgrade

Dim12: Upgrade: Cannot delete registry file error occurs during Dimensions database upgrade

Dim12: Upgrade : Cannot delete registry file error occurs during Dimensions database upgrade

Pages [Next]

Knowledgebase

Find Answers

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance