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 Get the following error in the browser when opening or submitting an item. "The item could not be found."
Open the ODBC datasource screen in Windows which is usually in the Administrative Tools area Go to the System DSN tab and just verify that your new ODBC connection is using the driver called "ODBC Driver 11 for SQL Server" If it's not using that driver you can manually create one on that screen and select the driver then open configurator and point to the new ODBC Connection.
CMS-XML ODBC password displaying in mail log
The data source ' DSN =TeamTrack_Prod; UID =teamtrak;PWD=*********' could not be verified . Error Opening Database The actual password for the database is displayed in the log file when this error appears.
CMS-XML Get "InitExtension Failed Some TS_LASTIDS table entries conflict with TS_ID values in other tables" when logging into SBM
InitExtension Failed: The data source ' DSN =SBM; UID =sa' could not be verified . Error Opening Database
CMS-XML InitExtension - Error Opening Database while logging on the SBM User WorkSpace.
InitExtension Failed: The data source ' DSN =Mashup2009; UID =sa' could not be verified . Error Opening Database.
CMS-XML InitExtension error when AE db needs to be upgraded still says to use SBM System Administrator
InitExtension Failed: The data source ' DSN =SBM; UID =sa' could not be verified . Error Opening Database
CMS-XML Utility to test ODBC query speed for SBM.
From Control Panel > Administrative tools, open Data Sources (ODBC) On the System DSN tab, select SBM_AE (for current versions), and click on Configure. On the Failover tab, change Connection Retry Count to be 0.
CMS-XML Database Clients and Drivers for SBM
If you have been using your own DSN prior to the upgrade and it is configured with the deprecated driver, nothing is changed after the upgrade; however, the driver is uninstalled by SBM. This means you will need to either use the default SBM_AE ODBC or manually update your DSN to use the Oracle Client ODBC driver after the upgrade process is finished.
CMS-XML Incorrect SQL Server Port Appears in the Configuration Utility
Before you upgrade, make sure your current System DSN is connected to your SQL Server database using TCP/IP and not Named Pipes.
CMS-XML Import: mapping single select values gives error "Number of bound columns exceeds the number of result columns"
6. Run the import wizard. Make sure to choose the "Import from another SBM database" option, but connect to source using the new Oracle 11.1.0.6 ODBC driver DSN . You should now be able to map the select values without errors.
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