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 SBM: Settings on ODBC Data Source change every time we click Apply in Configurator
SBM: Settings on ODBC Data Source change every time we click Apply in Configurator
CMS-XML SBM 11.3+: How to run a command line data import (ODBC Import)
SBM 11.3+: How to run a command line data import ( ODBC Import)
CMS-XML PRO8 TRKINET Database information is not complete. Error: SQL state = 08003 (Microsoft) ODBC driver manager Connection Not Open
PRO8 TRKINET Database information is not complete. Error: SQL state = 08003 (Microsoft) ODBC driver manager Connection Not Open
CMS-XML Data Direct driver for exclusive use with SBM
A custom API program accessing the SBM Database through the Oracle for SBM driver will give the following ODBC error message:
CMS-XML Contrary to Documentation Oracle 8 is not Supported in 5.7 - it is known not to work.
[Data Direct][ ODBC Oracle Wire Protocol driver](Oracle) ORA-00933: SQL Command not properly ended. This happens when trying to view attachements to a frozen release.
CMS-XML I would like to import data into a multi-user field
Multi-User fields are a special type of field and are not always available for mapping. You can only map multi-user fields when doing an ODBC (database) import. This feature is not available when importing from Excel.
CMS-XML Database driver to use for SQL Server
When using SBM with SQL Server 2014 and later, we recommend using the ODBC Driver 17 for SQL Server. SQL Server 2014 is the first in the line of Azure databases. This database needs a driver that has logic for recovering from high latency and less than desirable network connections. Previous ODBC Driver XX versions presented issues recovering network hicups.
CMS-XML Import Data Wizard Release Notes - TeamTrack 6.3
3. There are now three separate source options for importing data into TeamTrack. You can choose to import data from a generic database that supports ODBC , another TeamTrack database, or a Serena Tracker database.
CMS-XML How to Delete the Mashup2009 DSN Manually After SBM Uninstall
HKEY_LOCAL_MACHINE\SOFTWARE\ ODBC \ ODBC .INI\Mashup2009
CMS-XML Using System Administrator tool to import to Aux table get "Killer Import Error: Duplicate destination keys not allowed."
If you are importing from a odbc data source and you're using column A (for instance) as the unique key identifier, then make sure all the rows in column A are unique. If any two rows in your unique identifier column are the same, you will see this error when you import. To correct this, just make the cell values unique for each row.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs