Find Answers
|
|
All Operating Systems: | | | | | All Solution Types: | | | | | Source: | | | | |
| |
|
|
|
| |
Results |
|
SBM Version Diff
Differences Between Versions // cannot use encodeUri, because it does not encode the reserved ... // Do not show? // No results var noResultsText ... " No results found." : " No results." ... ... sort indicator when no search results are ... ... currently visible, don't hide it var ... ... ; // Don't alter locked columns ... { // Don't alter locked columns ... or toggle ( no argument) the ... ... No unlocked columns< ... ... Unselect rows which aren't in the current ... If no arguments were found ... If no arguments were found ...
|
|
|
|
SBM Version Diff
|
Differences Between Versions } \ No newline at end ... ... ; } \ No newline at end ... \ No newline at end ... \ No newline at end ... \ No newline at end ... ... = "We could not locate all of ... ... "Sorry, no data was found ... ... | "We could not locate all of ... ... "Sorry, no data was found ... ... that might have no text - var ... ... with backgroundImage and no text ... // if was not already in the ... ... // ignore no label.. ... ... + // does not need unescape from ... ... column should have no left margin in ...
|
|
|
Readme for SBM 10.1 as of 9th February 2012
|
... * If you have not yet upgraded to ... No longer supported: No longer supported for SBM ... No longer supported: Oracle ODBC connections that use the Oracle driver are no longer supported. No longer supported: ... been deprecated and will not contain any of ... ... before Promotion or Deployment ... the Flash Player is not installed or enabled ... ... SBM Application Administrator does not use an ODBC connection , so administrators ... ... " and " Is Not (None) ... ... for creating escalations has not changed, however ... ... to those that do not have subscribers.
|
|
|
|
How to enable SBM to communicate via SSL with a SQL Server database
|
... Set the JDBC connection string correctly ... set the JDBC connection string to connect ... ... the Windows ODBC connection will automatically negotiate ... SSL therefore you do not need to update ... ... You have to accept the red error ... you test the connection ' no such db' ... ... name, it is not necessary to add ... ... \default\ deploy Change the connection -url value ... server if it doesn't already have these ... < connection -url> ... required</ connection -url> < connection -url>jdbc:jtds ... SBMDB;ssl=required</ connection -url>
|
|
|
|
Template Content Differences
|
No )", ... Unable ... Connection ... connection ... Cannot ... cannot ... cannot ... No ... No ... No ... Cannot ... cannot ... No ... Deployment )" ... No ... No )", ... ( No \))" ... no ... no ... cannot ... cannot ... cannot ... no ... No ... no ... No ... Cannot ... Cannot ... Cannot ... No ... No ... No ... cannot ... Cannot ... cannot ... no ... connection )", ... cannot ... No ... No ... No ... cannot ... No )", ... ( Accepted /Completed\))", ... ( No \))", ... Accept )", ... cannot ... No )", ... No ... No ... Unable ... Cannot ... No ... No ... cannot ... cannot ... cannot ... cannot ... no ... Unable ... cannot ... cannot ... No ... No ... no ... Cannot ... No ... Cannot ... No ... cannot ... Cannot ... Unable ... < No ... Cannot ... Accept )", ... Unable ... Unable ... No ... Connection ... Cannot ... cannot ... No ... No ... cannot ... Connection ... No )", ... no ... no ... cannot ... cannot ... no ... No ... Unable ... cannot ... No )", ... cannot ... cannot ... cannot
|
|
|
|
Connection check in MM Environment server definition doesn't work on SSL
|
Using SSL connection using a certificate already in cacerts (therefore "trusted"). Everything works ok ( deployments , etc) but when defining the server using SSL connection the "Check connection " button was always failing. The issue is caused by the CN on the certificate != from the hostname entered in the endpoint (URL).
|
|
|
|
Composer error - connection attempt failed. Could not connect to the Repository. Please check that the connection settings are correct. Underlying error: (No compatible tokens found on the request).
|
The problem is in missed configuration of the maximum TCP packet size in Load Balancer. By default, it is 8 kb in the Apache HTTP Server and must be 16 kb as it is set in SBM.
|
|
|
|
Deploying a process app from Composer gives error "Authentication Failed: Unable to contact Authentication Service"
|
org.apache.axis2.AxisFault: Connection refused: connect
|
|
|
|
Trying to connect Composer using Secure SSL Connection get error "The request was aborted: Could not create SSL/TLS secure channel"
|
JBoss: C:\Program Files\Serena\SBM\Common\jboss405\server\default\ deploy \jbossweb-tomcat55.sar\server.xml Tomcat:
|
|
|
|
TCP connection reset when taking a snapshot
|
Currently, a work around can be used to set the TCP timeout on the load balancer / proxy server to something like 60 minutes. This, however, simply allows the Snapshot to complete, but does not address length of time it takes to promote.
|
|
|
|
|
|
|
|
|
|
