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 After upgrade to SBM 10.1 and above, I am getting an "Authentication Error" when connecting to the Application Repository
After upgrading to SBM 10.1 or above, you may get the following error whilst trying sign on to the Application Repository (previously known as the Application Administrator):
CMS-XML Error 403 or (500) when trying to load Application Repository, or SBM Composer error "No compatible tokens found on the request".
Error "(500)" on the login page When trying ot connect form SBM Composer: Connection attempt failed.
CMS-XML Application Repository Login: Internal Server Error (500)
This scenario is a consequence of inadequate privileges for the database user connected to the Application Repository schema. For SQL Server please see KB S138590. For Oracle Server please see KB S133641.
CMS-XML Get Internal Server Error (500) when logging into the Application Repository.
Could not create connection ; - nested throwable: (java.sql.SQLException: I/O Error : DB server closed connection .))
CMS-XML Cannot connect Composer to Application Repository
Trying to access the application repository via Composer results in failure and the following error message is displayed : “Failed to receive valid security token from http://<server name>/:8085/idp/sevices/Trust for user <user name>” This scenario comes about when using IWA/NTLM/NTCR with SSO as authentication mode.
CMS-XML Cannot connect to Application Repository is database name contains & symbol
The following error appears in the browser when you attempt to connect in this scenario: This page contains the following errors : error on line 109 at column 72: EntityRef: expecting ';' Below is a rendering of the page up to the first error .
CMS-XML Composer cannot connect from a users workstation but they can connect successfully to Application Repository from IE using the same connection details
In a standard single JBOSS configuration you will get a security token error when trying to connect from Composer. In a JBOSS cluster configuration the VIP (cluster virtual IP address) will just give a message that the configuration is incorrect.
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).
Another test to see if you're in this position is to open the Application Repository and see if you see the following error HTTP Status 403 Forbidden If you try to open the Work Center interface you might see the following error
CMS-XML Trying to connect Composer using Secure SSL Connection get error "The request was aborted: Could not create SSL/TLS secure channel"
Composer currently only uses TLSV1 Protocols and Ciphers when connecting to app repository via HTTPS so if either is missing from the SSL/TLS connector then it won't be able to connect anymore.
CMS-XML Logging into Repository gives error "Authentication error: A Soap fault occurred while contacting the authentication service"
When trying to log into the SBM Application Repository , the user gets the following error :
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Comparing files (demonstration)
This Dimensions CM demonstration shows you how to compare two item revisions in the repository, and compare an item revision in the repository with a file in a work area
Dimensions CM: Viewing work area and repository changes (demonstration)
This Dimensions CM demonstration shows you how to use the Windows Explorer integration to view the changes made to a work area and a repository.

Additional Assistance

  • Submit a Case Online
  • FAQs