Find Answers

Filter Search Results

Ask a Question

Example: "Database could not be verified"

Pages [Next]

Results

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).

Composer error - connection attempt failed. Could not connect to the Repository . Please check that the connection settings are correct.

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.

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

Unable to connect to repository in composer with error

You may experience a failure when trying to establish a connection in SBM Composer. This will leave you stuck in offline mode. The error message is:

After upgrade SBM 11.4.1, unable to log into Repository or connect via Composer

Similar Answers

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.

Cannot connect from Composer to repository in Tomcat cluster with Client Certificate Authentication

The Composer connection fails with a 403 error. This is caused by an incorrect configuration in the SSO gatekeeper-core-config.xml file. The

Cannot connect to Mashup Manager / Application Repository

If you use a named instance of SQL Server 2005 Express then you must connect using the dynamic port rather than the default port of 1433. This is defined in SQL Server Configuration Manager.

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.

Composer cannot connect to the Repository - Error: ... Failed to retrieve valid security token ... could not establish trust relationship for the SSL/TLS secure channel with authority

Composer is trying to connect via https even though the Use Secure Connection is NOT ticked. Get the following error.

Pages [Next]

Knowledgebase

Find Answers

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Additional Assistance