Find Answers

Filter Search Results
All Products:

Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML Date&Time is not properly imported from Excel file via ODBC driver
Development Manager 1.0Release Control 3.0Release Control Control 3.1SBM 2009 R4.02Service Manager 2.0
CMS-XML Error: Database upgrade failed: Cannot connect to database using provided ODBC data source
Release Manager 5.0.1Service Manager 5.0.1
CMS-XML Dim CM 14.x: DBI4502373E [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Invalid column name 'delta_version'.
Error detected in D :\Program Files\Micro Focus\Dimensions 14.5\CM\dbms\upgrade\upgradedb_141.sql, line 3062
CMS-XML Dim12: SQL Server: The multi-part identifier "pcms_seq.nextval" could not be bound
When attempting various operations in the Destkop Client and/or .NET, the following errors can occur and can change slightly in text depending upon the action being done. Errors are similar to the following depending on the action: Check Out Item - [Microsoft][ ODBC SQL Server Driver ][SQL Server]Invalid column name 'sysdate'. [Microsoft][ODBC SQL Server Driver][SQL Server]The multi-part identifier "pcms_seq.nextval"
CMS-XML Error When Creating ODBC Data Source in Mashup Administrator
To work around this problem, create the data source using Windows Data Sources Administrative tool instead of Mashup Administrator. The tool is launched from Control Panel | Administrative Tools | Data Sources (ODBC). For Oracle databases, be sure to create a system DSN using the Oracle driver .
CMS-XML LoggerConf.xml uses incorrect driver when admin installs latest SQL Server driver
Notice that the System Admin is connecting to the correct database and driver eg "ODBC Driver 11 for Sql Server" but LoggerConf.xml use "SQL Server" driver. Set up the SBM data source to use driver " ODBC Driver 11 for SQL Server" makes things work and editing LoggerConf.xml to use " DRIVER ={ ODBC Driver 11 for SQL Server}" works great, but upon hitting Apply in Configurator, the LoggerConf.xml is changed back to the "SQL Server" driver which does not work.
CMS-XML KM-Dim9: Reported Defect: Creating baseline fails on SQL server with (DEF114605)
Create Baseline: [Microsoft][ ODBC SQL Server Driver ][SQL Server]The column prefix 'bl_chdoc_items' does not match with a table name or alias name used in the query. - in the output lokks like this:
CMS-XML SBM: Listing report always shows "Associated Attachments" as empty
To resolve this issue, set the "Enable Closing Cursors" checkbox in the Oracle ODBC Driver Configuration of the SBM data source .
CMS-XML Notification Server process is crashing intermittently
names are specified in the ODBC data source .
CMS-XML W2003 SP1 - SQL Server 2000 - ODBC Administrator does not open (and Notification Server does not start)
b) When the failure occurs, change Data Source to the TeamTrack Sample ( no need to mess with the registry). ... d ) Click No on the change your web server question, TTAdmin starts. ... (2) Disable ODBC Connection Pooling. ... c) Create a new DWORD named ODBCConnectionPooling
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Working with items, part 1 (demonstration)
This Dimensions CM demonstration shows you how to perform impact analysis to determine which files are affected by specific changes

Additional Assistance

  • Submit a Case Online
  • FAQs