Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Upgrading to SBM 11.x: About the Orchestration Engine Database Upgrade
Retrying Orchestration Engine Upgrades and Clearing Warnings fail_out.xml if it is deleted or missing . For more examples on these options, refer to the renew command "-redeploy
CMS-XML Unable to upgrade Orchestration Engine
SBM 11.0
CMS-XML Orchestration Engine Database Upgrade Fails with Timeout Error
SBM 11.0.1.1
CMS-XML What to enter when the Orchestration Engine upgrade prompts for an SBM user name and password
What to enter when the Orchestration Engine upgrade prompts for an SBM user name and password
CMS-XML Get the following error when you try to run the Orchestration Engine Upgrade or any of the renew utilities. Can't find the registry key
Get the following error when you try to run the Orchestration Engine Upgrade or any of the renew utilities. Can't find the registry key
CMS-XML Failed to upgrade Orchestration Engine Database. The specified user is invalid....when the password being used has an &
SBM 11.0
CMS-XML SBM 10.x database upgrade to SBM 11.x gives error "Failed to upgrade Orchestration Engine database. Connection to the Application Engine server has timed out."
SBM 10.x database upgrade to SBM 11.x gives error "Failed to upgrade Orchestration Engine database. Connection to the Application Engine server has timed out."
CMS-XML How can I make Configurator ask to do the Orchestration Engine database upgrade again after I chose to stop showing warnings?
You might first go into this directory and move the log files that start with "upgrade..." to another folder just so you have clean ones for the next upgrade. C:\Program Files\Serena\ SBM \Common\Tomcat 7.0\server\default\logs Make sure Configurator is not running
CMS-XML Working with Orchestration Engine Usage Statistics
Starting in SBM 11.2, administrators can use the Application Usage report in Work Center to track orchestration usage. Data for this report is stored in the SUA_ORCHACCESS table that is added as part of the upgrade to 11.2 (or higher). A new set of renew utility commands is available to help you move Event Manager data for asynchronous orchestrations that was collected prior to the upgrade into this new table and purge data from this new table as necessary.
CMS-XML The Orchestration Engine purge utility does not purge some 2008 R2 entries and can also run out of transation log space for SQL Server
Running the new OE purge utility in 2009 R2 for the first time after upgrade can experience problems and does not seem to remove all data it could.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs