Find Answers

Filter Search Results
All Products:

Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML SBM 2009 R2 Installer uses SQL Server driver instead of SQL Native Client by default
SBM 2009 R2 Installer uses SQL Server driver instead of SQL Native Client by default
CMS-XML DIM10: Design Part View shows no items (DB2 only), error occurs [IBM][CLI Driver][DB2/NT] SQL0401N The data types of the operands for the operation "=" are not compatible. SQLSTATE=42818
DIM10: Design Part View shows no items (DB2 only), error occurs [IBM][CLI Driver ][DB2/NT] SQL 0401N The data types of the operands for the operation "=" are not compatible. SQLSTATE=42818
CMS-XML Collage installation for MS/SQL on Unix incorrectly prompts for JDBC drivers
If running an installation of 5.1.3, the installer should use the jTds drivers shipped with Collage. However, the installation prompts the user for the location of the Microsoft drivers and will not proceed without them.
CMS-XML Dim10: When actioning a request, an error of [Microsoft][ODBC SQL Server Driver] COUNT field incorrect or syntax error occurs
Dim10: When actioning a request, an error of [Microsoft][ODBC SQL Server Driver ] COUNT field incorrect or syntax error occurs
CMS-XML Dim CM 14.x: DBI4502373E [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Invalid column name 'delta_version'.
During an upgrading from Dimensions 12.1.1 to 14.5 on SQL Server the following problem was observed: -- Preparing to upgrade BASEDB to 14.1.. -- (Note: This particular stage of the upgrade will take 20+ minutes)
CMS-XML LoggerConf.xml uses incorrect driver when admin installs latest 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. As workaround, manually update LoggerConf.xml to the correct driver after restart IIS or perform Apply changes from Configurator. Check S140514 for recommended database drivers.
CMS-XML MCLG: Problems with large (>256 MB) files and MS/SQL 2000
With Collage's switch to the jTds drivers (in 5.1.2) and a couple changes in 5.1.3, it was possible to push out the limit a little. With the release of Collage 5.1.3 and, depending on various other factors, it may be possible for Collage with MS/SQL 2000 to handle up to ~600 MB, though this is not guaranteed.
CMS-XML MCLG: Using Collage with a Microsoft SQL Server 2000 named instance
Collage can store its admin and/or project databases on a named instance of Microsoft SQL , but the connection information must be entered correctly for the JDBC driver .
CMS-XML SBM for Oracle driver does not recover after losing its connection
This not an issue with SQL Server. The driver eventually restores the connection the next time that the process tries to access the database.
CMS-XML OE upgrade fails for SQL Server on SSL
The problem with upgrade is caused by defect for ssl in the jtds driver that is fixed in DEF284106 . But renew is self contained jar and jtds driver that is included in our renew.jar has ssl defect.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs