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 Configurator: Application Engine database upgrade hangs on large databases
The Application Engine database upgrade can hang in Configurator on large databases. This happens in the interaction between the Configurator and the console program that performs the upgrade. A workaround for this is:
CMS-XML Upgrade to 11.0.1 - Configurator hung on OE DB even though no orchestrations - had to update DB manually
Upgrade to 11.0.1 - Configurator hung on OE DB even though no orchestrations - had to update DB manually
CMS-XML Need to stop two configurators being able to be started on the same server as can overwrite each other and cause configuration issues
Need to stop two configurators being able to be started on the same server as can overwrite each other and cause configuration issues
CMS-XML How can I make Configurator ask to do the Orchestration Engine database upgrade again after I chose to stop showing warnings?
When you first upgrade to SBM 11.0 you get prompted to upgrade the Orchestration Engine database. If it has errors you get a message stating that you can just ignore the warnings and configurator will stop prompting you to upgrade the orchestration database. If you would like to get the prompt back in configurator later on do the following.
CMS-XML Stop or start notification server or mail client or SLA without using Configurator in SBM 10.1 and newer
To stop either the notification server (ns, mail client (mc) or SLA server (sla), set the appropriate value to 1, save the file, and then either restart SBM JBOSS/Tomcat according to release per above. To start either, follow the same steps and change the value to 0.
CMS-XML When you have Windows authentication after session timeout, page hangs instead of getting logged back in.
2. What are the steps to reproduce the problem? In Configurator : Set Authentication to Windows Domain
CMS-XML How to troubleshoot IIS hang or crash problems
To configure Active Diagnostics for a crash/hang problem: Open SBM Configurator . In the Diagnostics view, switch to the Active Diagnostics tab.
CMS-XML SBM hangs suggest to increase ConnectRetryCount with SQL Server 2014 or later
SBM 11.5 and better will accept the ODBC driver 17 for SQL Server. SBM 11.4 requires creating the ODBC connection manually so that we can use the ODBC Driver 17 for SQL Server. Create the ODBC connection manually using ODBC driver 17 for SQL Server. Set Configurator to use the newly created ODBC connection and Apply.
CMS-XML Active Diagnostics service won't start or you see a socket error in Configurator about the Active Diagnostics service.
When you open Configurator and look at the Manage Services section you may see the SBM Active Diagnostics service not started. If you try to start it, the server may run for a second but immediately stops . Also, when you click on the Diagnostics view and click the "Active Diagnostics" tab, there will be a link to start the service.
CMS-XML SBM Configurator should warn if a key certificate entry is being imported in a trust store
The SSL server credential's certificate does not have a private key information property attached to it. This most often occurs when a certificate is backed up incorrectly and then later restored. This message can also indicate a certificate enrollment failure .
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs