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 Very small Memory Leak if using Oracle with SBM, ODBC32, CDatabaseEx::OpenEx
SBM 10.1.4.1
CMS-XML Administrator installed on Japanese locale OS takes long time to connect to DB via ODBC
SBM 10.1
CMS-XML Error: Database upgrade failed: Cannot connect to database using provided ODBC data source
SBM 10.1.3.1
CMS-XML How to enable SBM to communicate via SSL with a SQL Server database
If your MS SQL Server is setup with the Force Encryption value set to yes then you will have to make the following changes for SBM to communicate with it. If your SQL server is setup this way then the Application Engine components will work fine because they connect via ODBC but the JBOSS components will fail to connect via JDBC and need the following changes made to the JDBC connection string in order to connect to the SQL Server database.
CMS-XML How to enable SBM to communicate via SSL with a SQL Server database in SBM 11.x
If your MS SQL Server is setup with the Force Encryption value set to yes then you will have to make the following changes for SBM to communicate with it. If your SQL server is setup this way then the Application Engine components will work fine because they connect via ODBC but the Tomcat components will fail to connect via JDBC and need the following changes made to the JDBC connection string in order to connect to the SQL Server database.
CMS-XML SBM Installation against SQL Server 2012 SP1 does not work
When trying to install SBM 10.1.3.1 on a Windows 2008 R2 x64 Server against a local SQL Server 2012 SP1 it is not possible to get this setup working. The documentation states the SQL Server Native Client 11.0 must be used for the ODBC system DSN but if this is used then Configurator states "A data source configuration conflict has been detected. Please make sure the Application Engine ODBC data source settings are synchronized with settings in the Database Servers tab.
CMS-XML SBM 2009 R2 Installer uses SQL Server driver instead of SQL Native Client by default
After the installation make sure the ODBC connection is using the correct driver, otherwise just set up a new ODBC connection using the correct SQL Native Client in Mashup Administrator. Remember to restart IIS afterwards.
CMS-XML Import: mapping single select values gives error "Number of bound columns exceeds the number of result columns"
6. Run the import wizard. Make sure to choose the "Import from another SBM database" option, but connect to source using the new Oracle 11.1.0.6 ODBC driver DSN. You should now be able to map the select values without errors.
CMS-XML Killer Import Error: Executing SQL directly; no cursor. Incorrect syntax near the keyword 'order' doing import from db
SBM 11.0Service Manager 5.2.1 ... ( ODBC native: State:01000,Native:16954,Origin:[Microsoft][SQL Server Native Client 10.0][SQL Server]
CMS-XML Configuration Utility Error
SBM 2009 R3 ... Check that the configuration file 'C:/Program Files/Serena/ SBM /Application Engine/LoggerConf.xml' exists and has correct settings. ... - [Oracle][ ODBC ][Ora]ORA-01017: invalid username/password; logon denied [Oracle][ ODBC ][Ora]ORA-01
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs