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 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 SBM Configurator does not support the use of SQL 2012 Dynamic Ports feature.
If customers decide to use SQL Server 2012 SP1 and use the Dynamic Port feature you can create a new ODBC connection to the SBM database and it tests just fine, however testing in Configurator returns a 'bad port' message. The issue seems to be with dynamic port selection which is being defined by the DBA..
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 No Oracle Installed on this Server
When starting the Configurator and using Oracle as your RDBMS, you may see this error if your Oracle installation is in a language other than English. Currently, the Configurator searches the HKEY_LOCALMACHINE\SOFTWARE\ ODBC \ODBCINST.INI registry tree for a key whose name starts with "Oracle in ...". On non-English systems, this may not exist - for example, the Spanish version will be "Oracle en ...".
CMS-XML LoggerConf.xml uses incorrect driver when admin installs latest SQL Server driver
Details: Failed to connect to database. - [Microsoft][ ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.[Micros
CMS-XML Email notification template isn't synchronized when using Network Load Balancing
There are 4 machines: WebServer-A & WebServer-B (using Network Load Balancing (NLB) ) Client PC-C & PC-D using ODBC connection to connect to TeamTrack
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs