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 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.
CMS-XML Composer cannot connect to repository "Connection attempt failed. Could not connect to the Repository. An HTTP Content-Type header is required for SOAP messaging and none was found."
" Connection attempt failed. Could not connect to the Repository. An HTTP Content-Type header is required for SOAP messaging and none was found."
CMS-XML 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:
CMS-XML After upgrade SBM 11.4.1, unable to log into Repository or connect via Composer
After upgrade SBM 11.4.1, unable to log into Repository or connect via Composer
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 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
CMS-XML 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.
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 Cannot connect Composer to Application Repository
The above error message is logged as per below in the sso-idp.log. .... 2017-05-25 13:10:37,657 INFO TS 172.30.209.2 f: g: NTLMAuthenticator.internalAuthenticate(224): NTLM authentication for <domainName>;<userName>:******* failed with code Failed to connect : <SBMServer>/<IPAddress> (-1073741823)
CMS-XML Unable to Connect to Document Repository checking in msp project.
2. Login to msp connector as that user. 3. Check out a msp connected task plan make a change and check in. 4. It will get to the point where it's trying to upload and then give "Unable to Connect to Document Repository" and the file will remain checked out.
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