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 Can't log into Repository after enabling SSL in AE.
Can't log into Repository after enabling SSL in AE.
CMS-XML Error "Invalid User ID or Password" when log into Repository after enabling SSL in AE
Error "Invalid User ID or Password" when log into Repository after enabling SSL in AE
CMS-XML Does logging into the Application Repository use a license?
No Simply logging into App Repository doesn't consume a license but doing a deploy will consume a license because it needs to login to Application Engine and run web services at that point.
CMS-XML SBM: Logging into Repository gives error: "org.xml.sax.SAXParseException; Premature end of file."
SBM: Logging into Repository gives error: "org.xml.sax.SAXParseException; Premature end of file."
CMS-XML Get Internal Server Error (500) when logging into the Application Repository.
When you attempt to login to the Application Repository you see an error "Internal Server Error (500)" Look for the following errors in the followng two files on the SBM server. C:\Program Files\Serena\SBM\Common\jboss405\server\default\log\server.log
CMS-XML Invalid user name or password with SSO enabled, cannot log into Application Repository if SSO is disabled
One of the key elements for SSO and application repository to function correctly is the Gsoap virtual directory. It is always wise to test that this URL is accessible:
CMS-XML Confusing Error message in Application Repository Log
Confusing Error message in Application Repository Log
CMS-XML Invalid Setting Can Break Application Repository Log
Invalid Setting Can Break Application Repository Log
CMS-XML Status filter in Event manager log works incorrectly in Application Repository
Status filter in Event manager log works incorrectly in Application Repository
CMS-XML High CPU on database for Application Repository at midnight and also when selecting to purge the "Audit History log"
At midnight the SBM system runs SQL statements in the database against the TS_AUDITENTRY table to check how many records are in the "Audit History log ". If there are a large number of records in the Audit History log, this calculation can run for a long time and can affects the performance of the SBM database for the Application Repository. If the Repository database is stored on the same server as the AE database, the user front-end may also be affected.
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