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 SQL*Plus Report
... SELECT EXU81 NOS SELECT EXU81 ... ... SELECT EXU9 NOS SELECT EXU9 ... ... /sun/ jndi /cosnaming/ ... /sun/ jndi /cosnaming/ ... /sun/ jndi /dns/ ... /sun/ jndi /dns/ ... /sun/ jndi /dns/ ... /sun/ jndi /dns/ ... /sun/ jndi /
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 . ... The record with ID 10 could not be found in the 'IDM' table. ... As of this writing the following url will take you to the download location. ... Find where the AE ODBC datasource is specified and click Change Give the datasource a new name and click OK Open the ODBC datasource screen in Windows which is usually in the Administrative Tools area ... The important part is that Configurator ends up using the ODBC datasource which is using the ODBC Driver 11 for SQL Server driver.
CMS-XML Configuration Files, Web Interface Templates, JavaScript Files, and String Changes That Have Changed in 2009 R4
... TABLE"> Could not read NSInstance table ... ... }'' does not exist.< ... ... .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 ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ... ... .EN} does not have the privilege ...
HTML Solutions Business Manager 11.4 Security Bulletin
Summary Secure JNDI Datasource Passwords (DEF298499) JNDI datasource passwords are now automatically encrypted using the security algorithm selected for SSO files in SBM Configurator. ... You can now configure the list of allowed URL protocols for Work Center Favorites.
CMS-XML Readme for SBM 10.1.1.1 as of 12th April 2012
This diagnostic test verifies the SBM Orchestration Engine data sources and the availability of the various message queues to send and receive synchronous and asynchronous requests. ... 3. Enter your current Exchange server version, connection URL , and system user credentials. ... A list of defects fixed in this version can be found in the Knowledge Base.
PDF Serena Collage Components User's Guide
... 29 reference 23 data sources , defining 60 ... ... browsers 57 relative URL to assets, ... searching for assets 32 Select component about 107 structure 108 SELECT statements, SQL 65 setting up DreamWeaver integration 16 single source for multiple language output 112 site structure, using for navigation 84, 95 sitemaps, building 95 sitestructure property, NavMap 98 size, asset 28 sorting asset queries 41 SQL files, processing 60 SQL queries, creating and storing 64 start date ordering AssetQuery results by 41, 92 structured queries, creating and storing 64 Sybase port number 62
PDF TeamTrack Database Schema
... allowed, a search for transition triggers ... ... attachment to an URL address. ... , Title, URL . TS_DATASOURCE varchar(255) 63002 Name of the ODBC data source TS_USERLOGIN varchar(255) 63002 User/Database login name or account TS_USERPASSWORD varchar(255) 63002 Encrypted user/account password TS_TRACKERSERVER varchar(255) 63002 Tracker-specific identification of database TS_TRACKERPROJECT varchar(255) 63002 Tracker-specific identification of database
CMS-XML How to fix a 404 error when using the Rest Grid widget with an SSL (HTTPS) url. "We did not find any matches for your request"
How to fix a 404 error when using the Rest Grid widget with an SSL (HTTPS) url . "We did not find any matches for your request"
CMS-XML After merge two incidents, the child incident shows error "The item could not be found"
The last operation resulted in an error, but the following unrecognized error code was received: The item could not be found. The server was processing this URL when this message was created:
CMS-XML No declaration found for element 'Locale' error during deployment
Open the SBM Application Repository and login. Go to the Environment where the deployment failed and check to make sure the Target Server and Runtime URL's are correct, including the BPEL and Event Manager URL's .
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