| |
Results |
|
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:
|
|
|
|
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
|
|
|
|
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
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
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 .
|
|
|
|
Upgrading from old version to SBM 10.1.5+. Configurator does not offer Config snapshot import during wizard mode.
|
Close Configurator and the edit registry to stop wizard mode by changing ConfigState to "Finish" instead of "Start" in HKEY_LOCAL_MACHINE\SOFTWARE\Serena\Mashups\Suite
|
|
|
|
Log files collected from Configurator are too large
|
into "C:\Program Files\Serena\SBM\Common\Diagnostics\MongoDb\data". 5. To further reduce the size of the logs, you can also stop the "SBM Tomcat" service and delete all files in "C:\Program Files\Serena\SBM\Common\Tomcat 7.0\server\default\logs" then restart the "SBM Tomcat" service.
|
|
|
|
SLA Engine Service Appears in Configurator on Notification Server Machine in Distributed Installation with SSM 5.2.1 and SSM 5.2.2
|
Therefore, to avoid confusion with running the right service in this scenario, stop the SLA Engine on the server that hosts the Notification Server and do not start it. The SLA engine will not work properly if it is started manually on this server.
|
|
|
