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
HTML SBM Version Diff
Differences Between Versions ... "Title" name ="Title ... ... "TextUser" name ="" ... ... "Text" name ="Text ... ... / if this is not delayed, Content-Disposition doesn't go through on ... ... "Url" name ="Url ... ... "Url" name ="Url ... ... header) \ No newline at end ... ... () \ No newline at end ... ... \f00 d "}. ... d "}. ... ... \f02 d "}. ... ... \f03 d "}. ... ... \f04 d "}. ...
CMS-XML Get the following error in the browser when opening or submitting an item. "The item could not be found."
The item could not be found. ... with ID 10 could not be found in ... ... in the MSSQL driver that ships with ... ... the "Microsoft ODBC Driver 11 for SQL ... ... Download the new driver to the SBM ... Install the driver ... where the AE ODBC datasource is specified and ... Give the datasource a new name and click OK Open the ODBC datasource screen in Windows ... ... that your new ODBC connection is using the driver called " ODBC Driver 11 for SQL ... ... not using that driver you can manually ... and select the driver then open configurator ... to the new ODBC Connection.
CMS-XML Date&Time is not properly imported from Excel file via ODBC driver
Development Manager 1.0Release Control 3.0Release Control 3.0.0.01Release 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
HTML SBM Version Diff
Differences Between Versions ... The Workflow Name cannot be blank. ... ... SBM Broker Service did not start. ... SBM Broker Service is not installed.< ... updates will not occur, try ... ... >The header could not be added because ... ... The database object could not be created. ... ... The requested header could not be located. ... ... The requested item could not be located. ... ... '' database could not be opened. ... ... r\nYou will not be able to ... ... The Service Control Manager could not be opened. ... r\nYou will not be able to ...
CMS-XML Readme for SBM 10.1 as of 9th February 2012
... * If you have not yet upgraded to ... ... terminology and component name changes have been ... No longer supported: No longer supported for SBM ... No longer supported: Oracle ODBC connections that use the Oracle driver are no longer supported. ... for SBM" driver that is installed ... ... for SBM" driver is now the only supported Oracle driver for SBM Application ... No longer supported: ... been deprecated and will not contain any of ... * Logical Names for Projects, ... ... the Flash Player is not installed or enabled ... ... SBM Application Administrator does not use an ODBC connection, so ...
CMS-XML Configuration Files, Web Interface Templates, JavaScript Files, and String Changes That Have Changed in 2009 R4
... TABLE"> Could not read NSInstance table ... ... group id or name ''{ ... ... group id or name ''{ ... }'' does not exist.< ... ... >A group name must be specified ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ...
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 Database Clients and Drivers for SBM
If you have been using the SBM_AE ODBC data source that is created by SBM Configurator, you do not need to make any changes; the upgrade process handles the conversion to the Oracle Client ODBC for you.
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