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 Aux relational data imported invalidly into aux table by both odbc import and app admin import
Aux relational data imported invalidly into aux table by both odbc import and app admin import
CMS-XML Error: Database upgrade failed: Cannot connect to database using provided ODBC data source
Error: Database upgrade failed: Cannot connect to database using provided ODBC data source
CMS-XML Date&Time is not properly imported from Excel file via ODBC driver
Date&Time is not properly imported from Excel file via ODBC driver
CMS-XML Administrator installed on Japanese locale OS takes long time to connect to DB via ODBC
Administrator installed on Japanese locale OS takes long time to connect to DB via ODBC
CMS-XML Very small Memory Leak if using Oracle with SBM, ODBC32, CDatabaseEx::OpenEx
Very small Memory Leak if using Oracle with SBM, ODBC 32, CDatabaseEx::OpenEx
CMS-XML Error "InitExtension Failed" when logging into the SBM User Workspace
Step 1: Test the ODBC connection
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 SBM 2009 R2 Installer uses SQL Server driver instead of SQL Native Client by default
Even though the SQL Native Client has been installed before the SBM installation, the ODBC connection set up by the installer may be using the SQL Server driver instead.
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.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs