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 Composer error - connection attempt failed. Could not connect to the Repository. Please check that the connection settings are correct. Underlying error: (No compatible tokens found on the request).
One scenario that will cause this error is if SBM is started and the database is not available at that time. If you start or make the database available after SBM is started the User Workspace UI will recover gracefully and the SBM UI will work as expected but Composer ( Tomcat / JBoss ) isn't able to gracefully recover from this situation causing Composer to throw the error above.
CMS-XML Deleting a contact from the SBM Administrator tool in the Contacts Auxiliary table you may get the following error in the UI and the contact doesn't get deleted. "An exception occurred while attempting to fetch a record count or a record integer value from the database"
The record list with the 'select .TS_ID, .TS_UUID from with (nolock) where TS_ID in (select TS_SOURCERECORDID from TS_USAGES where TS_FIELDID=153 and TS_RELATEDRECORDID=7)' select statement could not be read from the '' table.
CMS-XML Common errors in server.log when JBoss or Tomcat can't communicate with the database server.
With any of the errors above it basically means JBoss or Tomcat can't communicate with the database. When JBoss starts it reads the following files in order to connect to the database [SBM Install Dir]\Common\jboss405\server\default\deploy\commonlogger-ds.xml
CMS-XML SQLNET.ALLOWED_LOGON_VERSION prevents SBM from connecting to the Oracle Database
At times it is necessary to use a specific Oracle version logon. This is accomplished by setting SQLNET.ALLOWED_LOGON_VERSION = (11,10,9,8) in the SQLNET.ORA file. When this is set as SQLNET.ALLOWED_LOGON_VERSION = (11,10), the SBM Application Engine is unable to connect to Oracle.
CMS-XML Unable to load initial data for Work Center
Application Repository is inaccessible too with "Internal Server Error (500)" Running Static Diagnostics test shows all successful except Notification server and Mail Client Database Connection: Cannot connect to the Application Engine database or an internal error has occurred server.log showing many JDBC connection error such as:
CMS-XML How to make PPM connect to SQL via a trusted connection or NT account instead of SQL account.
Open the PPM Administration tool and Click New ( If you're running Windows 2008 right click on the PPM Administration icon and choose to "Run as Administrator" or you might get an error saying "Logon Failed: Unable to connect to database " when you finish.) Name the connection Click the "Only Connection" radio button
CMS-XML Various errors when Tomcat is started while the SBM database is not accessible.
Composer error - connection attempt failed. Could not connect to the Repository. Please check that the connection settings are correct.
CMS-XML About the Application Repository component and database (How to manually remove the Application Repository component)
Connection attempt failed. Could not connect to the Repository. Please check that the Repository Machine Name and Port are connect.
CMS-XML Get the following error in the browser when opening or submitting an item. "The item could not be found."
Open an existing item that had this problem before and verify your changes worked. If you look at the details for this driver on the Microsoft download scren it has the following text to show that this driver can be used with the followiing database versions. Microsoft ODBC Driver 11 for SQL Server is a single dynamic-link library (DLL) containing run-time support for applications using native-code APIs to connect to Microsoft SQL Server 2005, 2008, 2008 R2, SQL Server 2012, SQL Server 2014 and Windows Azure SQL Database
CMS-XML Clicking on documents view and you get error "Unable to create new root folder"
One common scenario that may lead to an apparent corrupted password in the config file is when the document store database is copied from a test environment to a production environment or vice versa and the password used by the docstore is different on the two systems. In this case a new connection would need to be created on the server the db was copied to because the connection information is stored in the web.config file in the Documents Manager folder and if the passwords don't match the errors above can happen.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs